If you are a Product Owner (PO), you are essentially the owner of the product and most POs I come across know what that entails. However, I also meet POs who determine during the Sprint which items from the Sprint Backlog the Development Team should work on, or what the solution should be, or even perform code reviews and evaluate work this way.

"How do you define Done when you’ve got dependencies outside the Scrum Team?” Dealing with Dependencies can throw a wrench into the process of even the most well-oiled Scrum Teams. It can be very challenging to get to a Done Increment when there’s something the team is depending on coming from outside the Scrum Team. How can a team best define Done in this scenario? PST'S Jason Malmstadt, Robert Pieper, and Gregory Crown have some surprising answers to this difficult question.

In this Scrum Lightning Round, our team tackles a very challenging question: “How does a Scrum Team work when they’re dependent on vendors or other business units that don’t use Scrum?” It’s a common scenario when applying Scrum in the real world and a question we get asked often. PST's Jason, Robb, and Greg all offer slightly differing perspectives on working through this tough situation.

The Scrum Guide is rather vague about how Product Backlog Items should be structured and how to make them transparent. That is by design because Scrum is intentionally incomplete. Understanding what attributes you are dealing with is helpful in creating a well-structured Product Backlog.

🚀 Dive into the world of empiricism in Agile development! 🌍 Discover how inspecting and adapting, deeply rooted in Agile practices like Scrum, ensures organisations stay ahead of the curve. 🔄 Join me on this journey through the Scottish Highlands of Agile development 🏞️, where change is the only constant, and success is all about reflection and adaptation. 💡 #AgileInsights #ScrumMastery 📊🔍.

One question that often arises in the context of Scrum is whether individuals can be part of more than one Scrum Team. While there is no explicit rule against this in Scrum, it's essential to explore the implications of such arrangements on productivity and adherence to Scrum values.

We have seen many Scrum teams attempt to resolve challenges by giving up and moving to Kanban. However, the decision to switch from Scrum to Kanban typically arises not from Scrum shortcomings, but rather from challenges in its implementation. In this episode, Jeff and Mike explore misguided reasons to move away from Scrum and things to consider before making that move.

The Product Backlog is crucial for Scrum to be effective. But for many teams, Product Backlogs are bloated, confusing, and hard to navigate. This blog discusses the challenges of building a great Product Backlog and what Scrum Teams can do to fight the bloat.

Great product ownership has the potential to transform companies, making them almost invincible, even when economic skies are dark. But how does this happen? And what exactly makes a great Product Owner in these times of adversity? The secret sauce, I propose, boils down to three Vs: Vision, Value, and Validation.

Ten Reasons and Five Approaches on How To Overcome Them

Wie kannst du das Daily Scrum verbessern? In diesem Beitrag erfährst du eine einfache Checkliste.

FAQs (Frequently Asked Questions) What is the role of a Scrum Product Owner? A Scrum Product Owner is responsible for defining and prioritizing the Product Backlog, ensuring the team delivers value to stakeholders, and maintaining alignment with the product vision. How can I improve my backlog prioritization skills? You can improve backlog prioritization skills by understanding user needs, estimating the value of features, and regularly reviewing and adjusting priorities. What certifications are available for Product Owners in Scrum? Certifications like Professional Scrum Product Owner (PSPO) are widely recognized for Scrum Product Owners. How can a Product Owner handle scope creep effectively? Managing scope creep involves clear communication with stakeholders, prioritizing based on value, and having a change control process in place. Why is continuous learning important for a Product Owner? Continuous learning keeps a Product Owner updated with the latest industry trends and best practices, enabling them to make informed decisions and adapt to change.

Los equipos ágiles pueden utilizar una variedad de métricas para medir su desempeño y el progreso de su trabajo. Pero no solo eso, un equipo agile también debe ser consciente de que valor entrega y de cómo evoluciona la organización.

In Scrum, it is the expectation that the Product Owner makes the Product Backlog transparent. Making the Product Backlog transparent doesn’t just mean making it visible; it means making it easy to understand, to convey meaning, and to have it illustrate the ‘why’ behind the Product Owner’s decisions. Introducing levels of decomposition is an optional practice that can be applied when a situation calls for it.

As the world evolves, so does the essence of leadership. Traditional management, apt for defined problems, finds its counterpart in agile leadership, tailored for our world's intricate maze. Agile leadership champions creativity, self-managing teams, and environment creation, moving away from mere oversight.

Scrum Values make the use of Scrum successful. How can you and your Team live these values during the Daily Scrum? Check it out!

Scrum has an accountability called “Product Owner”, but you’ll also come across people with the title of “Product Manager”. Are they the same thing? Related to each other? Is one better than the other? PST'S Gregory Crown, Jason Malmstadt, and Robert Pieper shed some light on this confusing topic in this Scrum Lightning Round.

When we talk about desired stances of a Scrum Master - Change Agent is one of them and we emphasize that a Professional Scrum Master should be an effective Agent of Change. However, in my subjective point of view, we rarely mention the domain of Change Management explicitly and we do not emphasize that Scrum Master should be an expert in Change Management. So, let's dive a bit deeper into the domain of Change Management and discover what Scrum Master can do to become and effective Agent of Change.

Superare il concetto di ritardo con Scrum è possibile! In un mondo in cui le scadenze sono spesso un pilastro cruciale, l’approccio di Scrum può inizialmente suscitare dubbi e scetticismo. La flessibilità apparente delle funzionalità da sviluppare può sembrare controintuitiva, ma è proprio questa caratteristica che rende Scrum un approccio ideale per affrontare problemi complessi in modo empirico. Questo articolo esplora come il concetto di “ritardo” si trasforma in un’opportunità di crescita, quando Scrum è applicato con competenza.

In the world of product development, the language we use can profoundly shape our approach to work. 🗣️ One term that I believe has been misused to the point of causing more harm than good is "User Stories". 📚 In my latest blog post, I argue for a shift away from this term towards a more flexible and transparent framework for describing our work: "Product Backlog Items". 🔄 This change can help us avoid the pitfalls of trying to force all our work into a user story format and ultimately lead to more effective product development. 💡 Join me as I delve into this topic and propose a new way of thinking about our work. 🚀 #ProductDevelopment #BacklogManagement

Die Scrum Master Gehaltsumfrage 2024: Werden Sie fair bezahlt? — Eine anonyme Umfrage von der Community für die Community!

Explore 8 red flags indicating incomplete Kanban adoption. Enhance your team's agility with Practicing Kanban

Do you ever struggle to help the leaders in your organization see the benefits of agile thinking or using the Scrum framework? I will address this challenge as I answer the Scrum Lightning Round Question: “How can we influence high leadership levels into better implementation of Agile & Scrum methodologies?” I will also discuss the benefits of Misk Ritigation. 🤔

Uma pergunta recorrente para quem está iniciando no Scrum: Por onde começar com o Scrum? Nesse artigo você verá sugestões de como começar com o Scrum - o que pode ser feito antes do primeiro Sprint, rodando o primeiro Sprint e o que fazer na sequência.

In a world marked by constant change and complexity, effective facilitation has become a critical skill for individuals and organizations alike. Whether you're leading a Sprint Planning event, a brainstorming session, or a strategic planning workshop, the ability to guide conversations, foster inclusivity, and elicit valuable insights is paramount. Facilitation is not just about orchestrating discussions; it's about creating an environment where everyone's voices are heard, ideas are explored, and decisions are made collaboratively. This is where Liberating Structures come into play, offering a toolkit of powerful facilitation techniques that can transform the way groups work together.

The Product Owner is the bridge between corporate strategy and the Scrum Team. The Product Owner must balance the demands of users against the need to ensure that the product remains up to date from a technical perspective. This often means that the Product Owner may need to choose between developing new features to satisfy customer requests and fixes for technical debt.

6 Advanced stances / perspectives a scrum product owner needs to understand in order to excel in Product Ownership & Management.

Le Daily Scrum est un event essentiel qui permet aux développeurs de rester synchronisés et d'identifier rapidement les obstacles à leur progression. Dans cette vidéo, découvrez l'essentiel de ce qu'est le Daily Scrum, comment il fonctionne et pourquoi il est important pour les équipes scrum ou les équipes agiles, le role qu'y joue le scrum master.

Ist aktives Zuhören nur für Jedi möglich?

Let Us Create Transparency: Are you fairly paid?

Existen varios mitos o ideas erróneas sobre la agilidad de negocio que no son verdad. Aquí te presento algunos de estos mitos.

By embracing experiential learning, quick application, and iterative growth, learners will gain the practical skills they need to affect positive change in their environments immediately.

In my opinion, the section on the definition of workflow in the Kanban Guide is probably the most important section. If you don’t understand your definition of workflow, many other things don’t work that well in the Kanban Guide as a result. If you don’t get that part, it’ll be difficult to really make progress.

Why I don’t care that much about the Scrum roles, events, and artifacts, and what I do care about instead.

Scrum Values make the use of Scrum successful. How can you and your Team live these values during the Sprint Planning? Check it out!

A brief explanation of why limiting Work in Progress gets more value delivered.

Agile is over 20 years old, and the Agile conference has been running since 2005. But are we seeing any changes? Has agile adoption stalled? This blog discusses enterprise adoption challenges and the environment necessary for Agile to succeed.

🎯📝 Master the delicate balance of crafting a #ProductBacklog! 🚀 Our latest blog post guides you through the path of keeping it lean💡, but not too lean, anticipating the future🔭 without overcrowding. 🔄 Embrace the power of regular reflection meetings to turn surprises into golden insights! 🤔💼 Be the sculptor of your backlog 🎨⚒️ - Trim it, shape it and make it ready for the future.

SAFe® ist heute das agile Framework der Wahl für viele große Organisationen. Wie kommt das? Erfahren Sie mehr über neun Gründe für diese Entwicklung.

In this vlog, join your hosts Andreanna Marshall, a professional Scrum Trainer at scrum.org, and the fantastic Scrum Master, Scott, as they dive deep into the Sprint Retrospective and provide several facilitation techniques to improve the event.

Someone asked us the question “How can we make Agile work with a long dependency chain?” With that as a somewhat-vague staring point, Jason Malmstadt and I explore ideas around Waterfall-Scrum Hybrid models, managing dependencies, and whether trying to combine these two ways of working even makes sense in the first place.

Scrum Masters are like great white sharks, if they stop swimming, they die. (Just metaphorically, thankfully.). Keep learning, Scrum Masters!

Most people familiar with Scrum know that teams need to break User Stories or other types of work into small pieces that can be done in a sprint. But this can be done in many ways. Are there ways that are better than others? Should you break it down by task? By area of expertise or specialization? PST's Jason Malmstadt and Robert Pieper discuss these ideas in this quick Q&A video.

Going beyond autonomy, mastery & purpose. 10 intrinsic motivators that can help your team.

Watermelon metrics - reported green but in reality totally red. We've all seen them. But can we prevent them?

This episode focuses on way to avoid robotic Scrum and make the Daily Scrum come to life!

In this article, we will explore some complimentary practices which the Product Owner might use to as an input when deciding how to order the Product Backlog.

“Administrative Overhead” is a phrase that strikes terror, anxiety, and boredom in the hearts of productive developers everywhere - including us at Responsive Advisors! In this Lightning Round Q&A session, PST'S Robert Pieper & Jason Malmstadt explore ways that Scrum can be used to lessen the amount of wasteful and unnecessary work in your daily routine.

Was sind Ideen-Sessions im Refinement, Sprint Reviews, Stakeholder-Meetings, Sprint Plannings und Sprint Retrospektiven wirklich? Es sind Entscheidungen. Mehr dazu in diesem Artikel!

How come? Learn more about nine reasons for this development.