What makes a Sprint valuable? If at the end of the Sprint, the Scrum Team is able to meet the goal and stakeholders, users expectations. A Sprint is not just about delivering functionality, it is an opportunity to experiment and validate assumptions about what Value is being created or delivered. ...

in diesem Artikel teilt PST Simon Flossmann drei Fragen, die sich jedes Scrum Team stellen sollte, wenn ihr Product Backlog mehr als 100 Einträge hat.

"Technical Debt" is a big topic in the Professional Scrum. This article addresses a specific new pain point: AI generates code fast (increasing Velocity), but creates massive maintenance debt. This warns Scrum Teams against false velocity.

There’s an old expression, don’t gild the lily. It means to try not to over decorate something that’s already beautiful on its own. Sometimes I want to tell a Product Owner that I am working with not to gild the lily by overloading their requirements with solutions.

Eine User Story ist kein Mini-Pflichtenheft, sondern der Startpunkt für echte Zusammenarbeit. Ihr Wert entsteht nicht durch viele Worte, sondern durch Gespräche, Fragen und gemeinsames Verständnis. Warum weniger Schreiben oft zu besseren Ergebnissen führt, zeigt dieser Artikel.

In diesem Artikel erklärt PST Simon Flossmann die am häufigsten übersehene Aufgabe eines Product-Owners

In this episode of the Scrum.org Community Podcast, host Dave West sits down with authors Sander Dur and Ryan Brook to explore their new book, The Anatomy of a Product—a practical field guide that uses the human body as a metaphor to demystify modern product management. (30:22 Minutes)

Scrum balances three forces—strategy, tactics, and risk—through the Vision, Product Goal, and Sprint Goal. The Product Goal bridges the gap between long-term vision and short-term execution, ensuring focus, alignment, and manageable risk in complex environments.

What manufacturing taught us about knowledge work — and why Ackoff knew we were asking the wrong questions

Experienced Scrum practitioners often reach a plateau where the mechanics are mastered, but the outcomes still feel constrained and inefficient. If you are comfortable with Scrum and ready to evolve your practice, consider an approach that reframes the Product Backlog and Sprint Planning around valu...

In diesem Artikel stellt PST Simon Flossmann 3 Fragen vor, die sich Product Owner viel zu selten stellen.

Scrum Teams don’t exist in a vacuum. The Scrum team's success—or failure—is heavily influenced by the broader organization around them.

In diesem Webcast zeigen dir die PSTs Peter Götz und Simon Flossmann, wie du als Product Owner Schritt für Schritt von einer inspirierenden Produktvision zu einem priorisierten Product Backlog gelangst, ohne das Vertrauen der Stakeholder zu verspielen.

When your backlog isn’t prioritized, even great teams can lose focus. In this blog, PST Jason Malmstadt explains how effective prioritization helps teams deliver faster, stay aligned, and build trust with stakeholders.

Pricing is a hypothesis about value, willingness-to-pay, and customer behavior. In this blog, we explore TAP’s pricing formula and show how Scrum Teams can run lightweight experiments, fake doors, A/B tests, and packaging trials, to validate pricing early. Treating pricing like backlog items ensures...

Defining product in Scrum is a fundamental choice. A narrow scope gives focus but risks local optimization. A broad scope brings adaptability and customer-centricity but may blur priorities and vision. The right balance turns Scrum into a true driver of business transformation.

User stories are one way to describe Product Backlog items, but too often they’re misused or forced into every situation. The original intent, from Extreme Programming, was about sparking collaboration through the 3 Cs: Card, Conversation, Confirmation, not filling in a rigid template. Scrum doesn’t...

El refinamiento es una práctica saludable en Scrum para mejorar la transparencia del Product Backlog y la entrega de valor. Hay muchas prácticas, técnicas y herramientas para llevarlas a cabo, sin embargo, su ejecución debe llevarse a cabo teniendo en consideración algunos aspectos que se muestran a...

This post unpacks what story point estimates really show -variance. A simple scatter plot reveals why chasing better estimates misses the point. Smaller, consistent work wins. Estimation isn’t the problem. The way we size work is.

In this article, we'll break down two of the most misunderstood yet powerful tools in the product toolbox: User Personas and User Role Modeling. These tools will help you create value-driven backlogs that reflect real user needs, not just business assumptions.

This blog covers the two techniques - Slicing and Splitting. Are they same? Are they different? When to use which?

In this episode of the Scrum.org Community Podcast, host Dave West and Brendan Mcsheffrey, Managing Partner at Kendall AI explore the Kendall Framework—a method for training AI using principles from lean, agile, and design thinking. (33:42 Minutes)

In this blog, author Ryan Brook shares a practical approach to launching new products by treating go-to-market as a learning process. He explains how using real customer insights, short Sprints, and Strategyzer’s Test and Learning Cards helps teams validate assumptions, reduce waste, and make smarte...

Ryan Brook explores how Scrum and the Double Diamond model complement each other in fostering innovation. By combining structured discovery with iterative delivery, teams can better frame problems, experiment safely, and deliver meaningful outcomes in complex environments.

In diesem Artikel erklärt PST Simon Flossmann wie Undercover Scrum funktioniert.

Our Professional Scrum Trainers have worked to gather many of the questions that are asked by their students, the Scrum.org Forum and other places to provide answers to your Frequently Asked Questions about Scrum. How do we handle spill-over between Sprints?There is no spill-over (or carry-over) of ...

AI is transforming product management across the entire Planning Onion, from vision to validation. Learn how AI enhances market analysis, backlog prioritization, and customization while rethinking technical debt. Discover how the Model Context Protocol and AI code generation are revolutionizing how ...

It may be tempting to push the team to deliver more by overloading the Sprint with extra work. But don’t do it! One of Scrum’s core values is focus, and that value exists for a reason. A team that focuses on delivering a reasonable amount of work will accomplish more than one that tries to take on e...

En este artículo, el PST Alex Ballarín explica como escribir buenos criterios de aceptación para entender y validar las historia de usuario.

Some teams are obsessed with documenting everything. They create tickets for tracking time, logging meetings, or even planning how to plan. They think they’re being transparent. In reality, they’re just adding layers of clerical work that don’t actually help deliver value.

In diesem Artikel erklärt PST Simon Flossmann die 3 größten Refinement-Probleme

Learn more about how to embrace the alignment-to-value pipeline and create your product operating model.

In this blog, PST Joshua Partogi shares his insights on the mechanisms in Scrum for handling urgent requests from stakeholders.

Product Backlog Management is challenging. Imagine you’re a Product Owner with a backlog of 300+ items. Stakeholders keep adding requests, developers feel lost in prioritisation, and every refinement session is a painful, drawn-out discussion. If this sounds familiar, you’re not alone. If you have e...

Rigid, long-term forecasts stifle agility and increase risk, but figuring out how to do shift to agile forecasting is challenging. We'll explore for core practices that enable agility through adaptable investment decisions: re-forecasting, decreasing precision, bracketing, and aligning forecasts wit...

Find ways of understanding and increasing value by imagining you are about to pitch your product to a demanding investor

The only reason for a Product Owner to exist is to maximize the value of the Product. One of the ways a Product Owner can accomplish this is by ensuring that most valuable items remain at the top of the Product Backlog and the Product Goal underscores their importance. So, how does the Product Owner...

PSTs Simon Flossmann and Stas Pavlov tackle listener questions about the challenges they are facing with their Product Backlog in this (recorded) live and interactive session. (1:00:56 hour)

So bringen Sie Ihr Produkt-Backlog zur Maximierung der Wertschöpfung für Kunden und Organisation in Ordnung.

Ordering a Product Backlog ensures that every step taken, every backlog item worked, is a step towards delivering value, satisfying stakeholders, and making the best use of the team's capabilities.

How to Align Teams with Stakeholders, and Finally Fix Your Product Backlog.

Die forensische Produkt-Backlog-Analyse ist eine 60-minütige Teamübung um Ihr Produkt-Backlog in Ordnung zu bringen. Identifizieren Sie, was kaputt ist, finden Sie heraus, warum, und einigen Sie sich auf praktische Lösungen – alles in fünf schnellen Schritten. Ohne Schnickschnack, nur Ergebnisse.

In vielen Organisationen bleibt echte Zusammenarbeit oft eine Wunschvorstellung. Einzelne Teammitglieder arbeiten isoliert, Missverständnisse häufen sich, und die Synergie bleibt aus. Doch wie schafft man es, dass ein Team wirklich zusammenarbeitet und Verantwortung teilt? Die Antwort beginnt beim B...

A 60-minute team exercise to fix your Backlog. Identify what’s broken, find out why, and agree on practical fixes—all in five quick steps. There is no fluff, just results.

A common question for newcomers to Scrum: What Do You Think About Story Points?

Ordering the Product Backlog in Scrum isn’t just about deciding what’s important—it’s about creating a clear sequence of work for maximum value. Discover the key differences between ordering and prioritizing, and the criteria Product Owners use to arrange backlog items effectively

The Scrum Guide says a Product Owner ‘orders the work’ into a Product Backlog. But what does ordering really mean in Scrum? It’s not about commands—it’s about creating clarity and alignment. Explore the collaborative nature of ordering and its impact on the Scrum Team.

The Kano Model* is a way to classify customer preferences by exploring how customers react to certain product capabilities or features. It can help Scrum Teams priortize experiments and features based on how likely they are to satisfy customers.The Kano Model uses a questionnaire to analyze how cust...

Opportunity Scoring* is designed to help identify areas for innovation by focusing on the outcomes customers want to achieve with a product or service. By scoring these outcomes based on their importance and the degree to which they are currently satisfied, the Opportunity Score highlights areas whe...

In this webinar, PSTs Sander Dur and Ryan Brook offer remedies to common dysfunctions product-focused organizations face and offer insights from their new book - Solving for Value - A Journey of Ambition and Stupidity.