Definition of DONE helps communicate clearly, manage STAKEHOLDER expectations + creates Transparency

Описание: Take this online course about Scrum for free https://www.udemy.com/course/scrum-gu...

--------

3 Scrum’s commitments are
1. the Product Goal for the Product Backlog artifact,
2. the Sprint Goal for the Sprint Backlog artifact,
3. the Definition of Done – for the Increment.

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the Product. The moment a Product Backlog item meets the Definition of Done – an Increment is born.

During the Sprint:
– Scope may be clarified and re-negotiated with the Product Owner as more is learned. But NO changes are made that would endanger the Sprint Goal.
– Furthermore, the Quality canNOT decrease – the list of criteria that make up the Definition of Done canNOT be reduced during the Sprint.

The Sprint Goal and the Definition of Done – both are commitments by the Developers. The Developers are required to conform to the Definition of Done.

If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at The Sprint Review. Instead, it returns to the Product Backlog for future consideration.

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment.

May there be any standard or shared DefinitionS of Done? Yes, there may be.
– If the Definition of Done for an Increment is part of the standards of the organization, then ALL Scrum Teams must follow it as a minimum.
– If the Definition of Done is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for their Product.
– If there are multiple Scrum Teams working together on a Product, they must mutually define and comply with the same Definition of Done.

--------

In this online course, you will learn about the most popular Agile approach used by 87% of teams – Scrum! As an Agile coach and Scrum Master with years of experience, Dim Blinov will guide you through the essential elements of Scrum including roles, events, artifacts, values, and pillars.

The course covers various elements of Scrum, including:

1. The definition of Scrum. It is a lightweight framework that helps teams and organizations generate value through adaptive solutions for complex problems.

2. The key elements of Scrum, including the accountabilities (Product Owner, Developers, Scrum Master), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment) + the commitments associated with the Scrum artifacts (Product Goal, Sprint Goal, Definition of Done).

3. The five Scrum values (Focus, Openness, Respect, Commitment, and Courage) and the three empirical pillars (Transparency, Inspection, and Adaptation).

4. Additional elements of Scrum, such as Product Backlog Refinement, Empowerment and Self-management, Lean thinking, Cross-functionality, and Iterative-Incremental approach.