In a demonstration meeting with a customer, the project team presented deliverables that were considered...

In Agile and Scrum frameworks, as outlined in the Agile Practice Guide and the Scrum Guide, a clear understanding of completion is required to ensure transparency and quality.

Why Choice D is correct:

The Definition of Done (DoD): This is a formal, shared understanding of the state an increment must be in to be considered complete and releasable. It serves as a comprehensive checklist of quality criteria, such as coding standards, testing (unit, integration, and regression), documentation, and peer reviews.

Application in Demos: During a Sprint Review (demonstration meeting), the team presents work that has met the DoD. By checking the deliverables against these criteria before the meeting, the team ensures that what they show the customer is actually " ready for use " and meets the project ' s quality standards.

Quality Gate: The DoD acts as a primary quality gate, preventing " half-done " work from being counted as progress or being pushed to the customer.

Analysis of other options:

A (Definition of Ready - DoR): This is a checklist used to determine if a user story is sufficiently defined (e.g., has clear acceptance criteria, dependencies resolved) to be brought into a sprint. It focuses on the " start " of work, not the " completion " for customer use.

B (Burndown chart): This is a graphical tool used to track the work remaining in a sprint over time. While it shows progress, it does not provide the criteria or checklists used to verify if a deliverable is complete.

C (Backlog refinement): This is an ongoing process where the Product Owner and the team add detail, estimates, and order to items in the Product Backlog. It is a planning activity, not a verification tool used during a customer demonstration.

Key Concept: The Project Management Institute (PMI) emphasizes that the Definition of Done (Choice D) is essential for maintaining a consistent level of quality across all increments. It ensures that when a team says something is " ready, " there is no ambiguity about the technical or functional state of that deliverable, providing the customer with confidence in the project ' s output.