The Agile Definition of Done (DoD) is a set of criteria that must be met for a project to be considered complete. It serves as a checklist for Scrum teams, ensuring a shared understanding of the requirements needed to make a product releasable. The Definition of Done includes all of the characteristics and standards an Increment needs to meet in order to be released.

The Definition of Done is the commitment by the Developers for the Increment, much like the Sprint Goal is the commitment by the Developers for the Sprint Backlog and the Product Goal is the commitment by the Product Owner for the Product Backlog. The Definition of Done includes all of the characteristics and standards an Increment needs to meet in order to be released.

In Scrum, the Definition of Done is a clear list of conditions that must be satisfied to mark a product increment as complete.

Empiricism is the foundational philosophy behind Scrum and other Agile frameworks. It asserts that knowledge comes from experience, and decisions are based on observed results rather than theoretical plans and assumptions.

Teams inspect their work (e.g., product increments, process effectiveness) and adapt based on real-world evidence—including customer feedback, Sprint outcomes, and team performance.

This approach ensures continuous learning and improvement, grounded in transparency, inspection, and adaptation.

Best time to estimate the Product Backlog:

1. Ongoing: During Backlog Refinement (Ideal)
   • When: Dedicated refinement sessions (at least once per Sprint)
   • Why:
     • Prevents Sprint Planning bottlenecks
     • Allows for deeper analysis of complex items
     • Enables PO to adjust priorities before commitment
   • Output:
     • Metric (story points)
     • Clear acceptance criteria
2. Just-in-Time: During Sprint Planning (Final Check)
   • When: Final hours of Sprint Planning
   • Why:
     • Confirms estimates account for latest insights
     • Ensures selected items align with Sprint Goal
   • Output:
     • Committed Sprint Backlog
     • Task breakdowns
3. Ad-Hoc: When New Work Emerges
   • When: New high-priority items arrive mid-Sprint
   • Why:
     • Maintains backlog readiness
     • Avoids surprise capacity issues
   • Rule:

The Sprint Goal defines the intended outcome or objective of a Sprint.

During Sprint Planning, the Scrum Team collaboratively creates this goal after the Developers forecasts which Product Backlog items it can deliver in the upcoming Sprint.