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

In this video, PST Ryan Brook talks about the meaning of the Increment and how the Definition of Done comes into play in support the work of the Developers. (8:15 Minutes)

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.

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)

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)

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)

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)

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?

In this blog post we will give examples of Increments and why it is important to have Done Increments

3 Do-it-yourself workshops to create, use, and improve your Definition of Done

Forget all these Agile Maturity Scans which are often treated as management reports and too focussed on the mechanical side of "do these things and the maturity goes up". Change itself should be considered an empirical journey with no end state. It’s always on the move, so start with making your tra...

Scrum uses an iterative, incremental approach to deliver value to the business through the medium of the Sprint. The purpose of each Sprint is to deliver a Done, usable increment. It sounds straightforward, but it can be tricky to achieve. Here are the three steps to Done in Scrum.

A common question we get asked is how do we get started with creating a Definition of Done? Let's explore how we can obtain transparency of where you are, your destination should be, and what your possible first steps are to get there!

Even a well-set team with clear objectives may fail to finish each thing when the Sprint ends.

There is a lot going on when it comes to delivering complex products in an uncertain and constantly changing world. In this webinar, Scrum.org Professional Scrum Trainer Stephanie Ockerman breaks it down to 5 ways Scrum Teams can discover their opportunities to improve the many different aspects of ...

Leaders use the Scrum Artifacts as a window into the work of the Scrum Team. This transparency enables inspection and adaptation at the appropriate level while enabling the team to self-manage. 

In today's vlog I would like to come back to the fundamentals of Scrum ... Done Increment.

If I were to summarize the purpose of a Sprint, I would say that it’s to deliver a Done, usable increment that meets the Sprint Goal.

This blog post discusses how the Circles of Improvement from the book by Stephen R. Covey: The 7 Habits of Highly Effective People, work in Scrum.

In my live training, I often ask students why we estimate. The answer I usually hear is some version of...“So we know how big something is and how long it will take.”  

Join me and explore the reasons and the consequences of this Sprint anti-pattern in 109 seconds.

I've given the same advice to almost all of my clients -- "you need a clearer Product Backlog", "You're working really hard but you're not getting anything done", and "You need to cut scope, launch your product with a more focused scope, launch it, and then get feedback." ...

On today’s episode of YOUR DAILY SCRUM: When does a Scrum Team create a Definition of Done? Today's question asks when the Definition of Done (DoD is created by the Scrum Team.

On today’s episode of YOUR DAILY SCRUM: Do we still have a Sprint Review if nothing is done?

Many organisations wrestle with the seeming incompatibility between agile and release management, and they struggle with release planning and predictable delivery.

In my last post about Professional software teams creating working software David Corbin made a good point. How do you determining what “Free from fault or defect” means? Since that is different for each Product and may change over time you need to focus on Quality and reflecting that quality in a D...

At a recent class, a new Scrum Master asked me for a simple example of a Definition of Done. This post captures my answer to them and I hope it will help simplify this concept for you.

In the 2020 Version of the Scrum Guide, the commitments were introduced for each artifact. These then became an element of Scrum; in that they need to be used to gain the maximum value that the Scrum Framework offers. They were always part of a Professional Scrum approach, now there is a clear conne...

This blog post talks about the addition of Commitments to each Artifact in the updated Scrum Guide.

Scrum is defined completely in the Scrum Guide by Ken Schwaber and Jeff Sutherland, the originators of Scrum.  The Scrum Guide is maintained independently of any company or vendor and therefore lives on a brand neutral site.  The Scrum Guide is translated and available in over 30 languages.

As per Scrum Guide – The Sprint Goal is an objective that will be met within the sprint by implementing the Product Backlog, and it guides the Development Team on why it is building the Increment.

Regularly, we find articles from developers detailing why ‘Agile’ in general and Scrum’s nature, in particular, deserve our collective disdain.

“Can an R&D team of chemists, physicists, electrical engineers, mechanical engineers and embedded software developers optimize teamwork and value by using Scrum? And can live virtual Scrum training deliver a practical Scrum learning experience to everyone on such a functionally diverse team?”

Ein Produkt für Kunden verfügbar zu machen ist der einzige Weg für ein Unternehmen, mit diesem Produkt Wert zu generieren. Erst wenn ein Produkt am Markt verfügbar ist, sind Kunden bereit, Geld dafür zu bezahlen. Wer aber entscheidet, ob ein Produkt released wird?

A Sprint Review is perhaps one of the most difficult elements in the product development with Scrum.

How to make sure that the definition of Done is used properly at a sprint planning session? Continue reading ...

“Our problem is that we can’t plan Sprints accurately with velocity,” he said. “Some Sprints, our velocity is really high, in others, we barely achieve anything.”

Treacherous bottlenecks can nullify all your hard work, no matter how industrious you are.