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.

Struggling with long and unfocused Daily Scrums? In the second part of this two-part series, PSTs Robert Pieper and Greg Crown share five more strategies to cut down on wasted time, improve focus, and ensure your Scrum Event stays efficient and productive.

In diesem Artikel stellt PST Simon Flossmann 5 Methoden zum besseren Product-Backlog-Management vor.

If Product Owners fail to maximise the value produced by the team, the entire product development can be derailed. Failing to understand and validate value leads to the team missing the intended goals.

A common question for newcomers to Scrum: Can the Tasks of the Sprint Backlog Be Modified Mid-Sprint?

Agile teams often struggle with how to size and forecast upcoming work. Flow metrics offer a simple, effective way to solve that problem without the headaches that come from traditional estimation methods. In fact, flow metrics can provide more accurate planning and forecasting than using points or ...

Struggling with unclear priorities, technical debt, or stalled progress with your Scrum Teams? Adopting a product-focused approach can unlock your team's potential and drive continuous value. Discover how one team went from nine months of frustration to delivering game-changing solutions in just wee...

How to Make Retrospectives Lead to Real Change and Stop Spinning Wheels.

In diesem Artikel erklärt PST Simon Flossmann 3 Backlog-Management-Methoden, die helfen die wichtigsten Features zuerst zu priorisieren

What makes a good Product Goal? In this article, PST Simon Flossmann shares his approach on how to use the business model equation to define a Product Goal that aligns with the company’s goals.

In diesem Artikel erklärt PST Simon Flossmann, wie du ein gutes Produkt-Ziel definiert werden kann.

A common question for those new to the practice of #StoryPoints: Should we assign points to #bugs?

Don't spend months writing detailed proposals only to discover that things always worked out differently. Instead, sell Sprints and deliver more value to your customers sooner!

I am often asked, what’s the right amount of information for an item in the Product Backlog. First, there is no “right” amount of information. And second, less is more.

These criteria establish conditions for team or stakeholder acceptance, ensuring that the work meets the required standards and setting clear expectations for what needs to be delivered.

Backlog refinement is essential for Scrum teams to work effectively, yet many teams struggle to allocate enough time for this critical activity. In this video, PSTs Jason Malmstadt, Gregory Crown, and Robert Pieper discuss strategies to optimize backlog refinement sessions and share practical tips f...

In this Responsive Advisors Lightning Round, PSTs Robb Pieper, Greg Crown, and Jason Malmstadt go over common scenarios that lead to change while you’re in the middle of a Sprint and ways you can deal with unplanned work that’s thrown your way during the middle of the Sprint.

By dispelling common misconceptions and embracing the Sprint Backlog's true nature, teams can enhance responsiveness and work cohesively towards their goal. The Sprint Backlog is a powerful guide that, when used correctly, ensures that the team remains focused, adaptable, and aligned with the overal...

Understanding the true nature of the Product Backlog is essential for the success of Scrum and the delivery of value to stakeholders. By dispelling common misconceptions and embracing this knowledge, teams can enhance their responsiveness, prioritize effectively, and deliver maximum value to their c...

While there are various ways to write or format items on the Product Backlog, one of the most popular and effective methods is writing them in the user story format. This practice, though beneficial, is not mandatory. Scrum teams may choose to adopt the user story format when it suits their needs an...

Done is a fundamental part of bringing transparency. How does this relate to your Sprint Backlog? Check it out! Back to the foundations of the Scrum framework (73)

This webinar with PST Lavaneesh Gautam covers how Impact Mapping can help you optimize Product Backlog Management.

I really can’t let this incremental delivery topic go. According to the 2020 Scrum Guide, “Scrum employs an iterative, incremental approach to optimize predictability and to control risk.” This means that Scrum Teams deliver a done, usable increment of working product frequently. This approach ha...

Done is a fundamental part of bringing transparency. How does this relate to your Product Backlog? Check it out! Back to the foundations of the Scrum framework (71)

In this video, PSTs Greg Crown, Robert Pieper, and Jason Malmstadt break down the three Scrum artifacts: the Product Backlog, Sprint Backlog, and Increment. They provide clear explanations and practical tips to ensure you're using these artifacts effectively to deliver valuable Product Increments ev...

What is the difference between validation and verification?

In this blog post PST Mary Iqbal discusses the question - Who Writes Product Backlog items Scrum?

Product Owners: feeling overwhelmed by your Product Backlog? You're not alone! In this video, PSTs Robert Pieper, Greg Crown, and Jason Malmstadt address the typical challenges you face and provide you with effective strategies for managing your product backlogs.

We cover the perils of a lack of transparency, limited to non-existing leadership support, and why penny-pinching is the wrong approach.

The Product Owner is accountable for maximising the value by communicating the vision, Product Goals, and creating the right level of transparency of the Product Backlog to satisfy customer needs.

In diesem Artikel erklärt PST Simon Flossmann 4 kritische Fehler in Sprint Backlogs. Wenn du sie vermeidest, verbesserst du die Effektivität deines Scrum Teams.