In this blog post PST Joshua Partogi shares how to map Agile Leaders maturity to the metrics they emphasise.

Scrum isn’t about busywork—it’s about making outcomes more predictable. But many teams confuse predictability with fake certainty. In this post, we explore how Scrum really optimizes predictability, where teams go wrong, and what you can inspect today.

In Scrum, one of the most common misunderstandings is the difference between the Definition of Done and Acceptance Criteria. In this blog, PST Robert Pieper explains the key differences and how your team can avoid confusion.

Scrum’s lean thinking isn’t about doing *everything* faster—it’s about focusing only on what truly matters. Learn how to cut through backlog bloat, process clutter, and competing priorities so your team’s energy fuels real outcomes, not busywork.

One of the key aspects of Scrum is that each Sprint should result in a Done, usable increment of product. But what happens if your team struggles to achieve this? Here are ten practical ideas that your team may consider adopting to help improve your ability to get to Done.

If you’ve ever been a Developer on a Scrum Team, you’ve probably experienced this moment: you’ve completed all of the work you originally planned for the Sprint, and there are still a few days left. What now? It might seem like a good idea to just pull more work into the Sprint, but that sometimes c...

Explains the difference between subjective goals and the objective Definition of Done in Scrum, highlighting how clear, measurable criteria ensure consistent product quality.

In Scrum, “Done” means done. Not halfway done, not “almost there,” and certainly not “we’ll get to it next Sprint.” Yet, many teams find themselves with a growing burden of unfinished work. Over time, that burden starts to feel like a monkey on the team’s back—heavy, distracting, and hard to shake o...

Master one of Scrum’s most critical (and misunderstood) concepts with PST Jason Malmstadt in this micro-training video. Alongside PST'S Robb Pieper and Greg Crown, Jason explains what the Definition of Done really means, how it differs from acceptance criteria, and why it’s key to delivering high-qu...

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.

The only purpose of doing Scrum is to create a DONE Increment. To get to a DONE Increment, quality is key. In Scrum Teams Definition of Done enables transparency around quality and releasability of the Increment. However, more often than not the Definition of Done stops at meeting acceptance criteri...

Warum „Done“ das Herzstück von Scrum ist In Scrum ist „Done“ weit mehr als nur ein Begriff—es ist das zentrale Konzept, das sicherstellt, dass ein Produktinkrement tatsächlich einsatzbereit ist. Ohne eine klare Definition of Done (DoD) ist empirisches Arbeiten in Scrum unmöglich, da Transparenz, I...

In Scrum, the Definition of Done (DoD) is a shared understanding of what it means for a Product Backlog item to be considered complete. For example, for a Scrum team that is developing software, a Definition of Done might include things such as 'Complete code review' or 'all standard Regression scri...

This article was tough to write, not because I don’t have enough mistakes to share, but because there are so many! Mistakes are where we learn, and that’s exactly what I’ve done. I hope sharing mine will help you avoid making the same ones.

Working Software. Done Increments. Two related concepts in the agile world that people trying to leverage Agile/Scrum’s empiricism outside of the software/technology space struggle with.

In Scrum, the Definition of Done (DoD) plays a critical role in ensuring quality and transparency. But who defines this important concept? And what does it even mean? Let’s break it down.

In this blog, we dispel a series of myths associated with product discovery in Scrum. Myths such as “it's a phase in the process and can not be done in a Sprint,” “It's only for greenfield projects,” to “ The DoD stops us from doing Discovery”.

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

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

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

In this video, PSTs Robert Pieper, Jason Malmstadt, and Greg Crown discuss the importance of quality standards and how Scrum can help ensure high-quality results.

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

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)

In diesem Artikel erklärt PST Simon Flossmann die fünf Irrtümer über die Rolle des Entwicklers in Scrum.

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)

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

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

The Definition of Done is a commitment that guides teams toward their goals. It's about ensuring that each product backlog item delivers value to the end user while maintaining quality standards.

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

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

In this Scrum Tapas video, Professional Scrum Trainer Simon Reindl explores how to demonstrate the value of Scrum to your organization. (4:34 minutes)

In this Scrum Tapas video, Professional Scrum Trainer Simon Reindl discusses engaging middle and senior management with Scrum or Agile by emphasizing the importance of delivering tangible results in a short amount of time. (2:35 minutes)

I was recently asked, "Do you think it's necessary to start every Sprint with each story fully specified?" The short answer: No, I don't. Join me as I discuss the topic.

There are numerous benefits to a Definition of Done, but consider this: The entire purpose of Sprint is to deliver a done, usable increment at least once per Sprint. Shouldn’t we be clear about what done means to us in our context? In this article, we'll discuss 10 benefits of the Definition of D...

What's the difference between Acceptance Criteria and Definition of Done? Teams that use Acceptance Criteria without a Definition of Done are skipping a crucial element of Professional Scrum!

Dive into the Scrum framework's approach to ingrained quality through the Definition of Done.

Applying the Definition of Done wrong will be detrimental to your agility.

Enabling constraints are an often misunderstood but powerful tool when coping with complexity.

Is Your Team Misinterpreting 'Done' in Scrum? Then Don't miss out on this video! Professional Scrum Trainers Robb Pieper, Greg Crown, and Jason Malmstadt dissect the Definition of Done and the "Done" Increment, shedding light on common misinterpretations.

The DoD and the acceptance criteria are two fundamental concepts in product development. While DoD is part of Scrum, Acceptance Criteria is an additional practice.

While only DoD is part of Scrum, some teams may choose to use DoR to help with Product Backlog transparency. The DoD provides a commitment for what the team must do to have a Done Increment.

During this article, we’ll look at some basics about the Definition of Done (DoD). We’ll explore misunderstandings such as the application of the DoD, ways to use a fully achievable DoD and avoid creating a waterfall approach, when to inspect and adapt the DoD, and an example starting point for you...

A short introduction about how you can make working with value more practical as a Product Owner.

By Simon Reindl and Stephanie Ockerman - This book is for anyone who wants to deliver increased value by using Scrum more effectively. Leading Scrum practitioners Stephanie Ockerman and Simon Reindl draw on years of Scrum training and coaching to help you return to first principles and apply Scrum w...

There are several reasons why Scrum Teams are left with un-done work at the end of the Sprint, including:They don’t understand the importance of time-boxes or Sprint Goals. If Sprints are just periodic check-ins on progress and if Sprint Planning merely involves updating an existing overall project...

There are reasons why Scrum Teams may have un-done work at the end of the Sprint, but these occurrences should be infrequent as they are detrimental to the team’s ability to deliver value. There are various techniques that they can try to minimize having un-done work, including:Ensuring that everyon...

The phrase “un-done work” refers to work that is not finished by the end of the Sprint, according to the Scrum Team’s Definition of Done. Un-done work is, simply put, waste. It adds no value to the product Increment and may even reduce its value. Ultimately, un-done work represents time that the Sc...

Un-done work is work that does not conform to the Definition of Done and is therefore unfinished. It represents time the Scrum Team spent creating something that delivered no value. Learn what un-done work is, what causes it and techniques for eliminating it.

If you or your team are new to Scrum, you can use this as a starting point to answer, “what should we be doing and why?” for each Scrum Event. If your team is more experienced but you feel like you’re drifting away from healthy behaviors and patterns and you’re not sure how to course correct - you c...

🚀 Navigating the nuances between the Definition of Done and Acceptance Criteria? 🤔 Dive into our latest article that explores the sanctity of a working, usable product without compromising value. 💡 Let's ensure quality and value go hand in hand! 🤝