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 Sprint Review? Check it out! Back to the foundations of the Scrum framework (69)

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)

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)

In this Scrum Tapas video, Professional Scrum Trainer Simon Reindl explores how to demonstrate the value of Scrum to your organization. (4:34 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 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...

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...

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! 🤝

The Definition of Done and Acceptance Criteria both describe facets of a finished backlog item, don’t they? So what’s the difference? Does it matter? YES!! While they may seem similar, there are some crucial distinctions between these two, and confusing them may cause serious problems. I hope this q...

How validating the value of the Scrum team’s work during the Sprint limits risk and increases predictability

The three Scrum artifacts represent work or value. They help us maximize transparency, making it easier to inspect and adapt our way toward better outcomes. Let’s look at the commitment for each artifact to uncover their critical role in enabling the business benefits of agility.

Back in 2012 when I was on the path to becoming a Scrum.org Professional Scrum Trainer, I travelled to Boston to attend a PSM course run by Ken Schwaber (the co-creator of Scrum and Chairman/Founder of Scrum.org). It was a large class and people had flown in from all over the world. Everyone was exc...

The “Definition of Done” (DoD) describes the quality standards for the Increment to be considered “done” and in a state that it can be effectively inspected. It provides to the Scrum Team and organization a common understanding of the completeness of the Increment. Without this crystal clarity, it’s...

In this video we discuss the Definition of Done, why it is important and give an example of how it is created. (4:29 Minutes)

In this vlog, PST Joshua Partogi digs deep into the concept of Definition of Done and Increment in Scrum.

The Definition of 'Done' probably is the most misunderstood concept of the Scrum framework. In this article, we will learn some common dysfunctions or antipatterns associated with the Definition of 'Done' and also certain tips or remedies to overcome these.

The Definition of Done describes the quality standards for the Increment. Learn why getting to Done is so important, what undone work is, if it’s okay to show work that isn’t done to stakeholders, can you present undone work at the Sprint Review and what’s the difference between the DoD and Definition of Ready or acceptance criteria.

The Definition of 'Done' is probably the most misunderstood concept of the Scrum framework. In this article we will discuss:  What Is the Definition of 'Done'  How it can be used in Scrum Events

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the Increment. If a Product Backlog Item does not meet the Definition of Done, it cannot be released yet. Think of the Definition of Done as the ...

Business agility is only possible with technical excellence. Learn more about the twelve success principles of employing a Definition of Done as a quality standard to support your organization’s path to agility.

A scenario showing how the scrum framework and metrics can help a team self manage for improvement.

10 simple principles of a critical scrum success factor to improve your team’s effectiveness, team spirit, and reputation.

According to the Scrum Guide, Scrum teams are typically 10 or fewer, with a preference to the smaller size.  When Scrum Teams become too large, they should consider re-organizing into multiple Scrum teams supporting a single product.  When this happens, the Scrum Teams should share a single Product ...

But when you have scrum, for example, you need to deliver an increment every single sprint and that increment needs to be done. So the team needs to have a thing called a Definition of Done and done does not mean met the acceptance criteria. Doesn’t just mean that, there should be other consideratio...

What is an Increment and how does it connect with the other elements of Scrum?