It’s not “Done” until it meets your Definition of Done
A “Definition of Done” is a commitment to deliver a working increment meeting defined quality criteria to ensure the increment is complete.
A “Definition of Done” is a commitment to deliver a working increment meeting defined quality criteria to ensure the increment is complete.
A Definition of Done can vary widely between organizations, departments, and even teams, but it’s crucial that you have one. Find out why.
The fifth episode of “More Agile Great Debates” covers conflict, leadership, technical P.O.s, who writes User Stories, and extending Sprints.
Each event of Scrum has a specific audience and purpose. While skipping some might be tempting, you might want to read this before doing so.
In the second part of my blog series on “Agile’s Great Debates,” learn about five more agile topics that people argue about and disagree on.
Nothing in The Scrum Guide says you can’t pick a specific purpose for a Sprint, but is it a good practice? Are there special types of Sprints?
Not delivering a “done” increment at the end of a Sprint can cause many negative consequences. It’s a bad habit and won’t make anyone happy.
So, you have a Scrum Team. But does your team have all the necessary cross-functional skills to get to a “done” increment each Sprint?
I have long advocated that Scrum Teams have a “Definition of Ready”; if you don’t have one, there are many potential negative consequences.
I can’t tell you how many organizations I have worked with that had employees who confused the Sprint Review with the Sprint Retrospective.