The correct answer is D - Confirm managers and stakeholders are invited to product review meetings. Agile promotes early and continuous feedback from stakeholders through regular reviews (e.g., sprint reviews or demos). Their active engagement ensures alignment with evolving business needs.
From the PMI Agile Practice Guide:
"Demonstrating working product increments at iteration reviews allows stakeholders to inspect progress, provide feedback, and align expectations. Agile teams rely on these sessions to validate whether the product meets business requirements." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement and 5.2 - Reviews) Mike Griffiths emphasizes:
"Frequent stakeholder reviews reduce risk by capturing early feedback. Stakeholder participation in iteration reviews ensures alignment and continuous validation of business goals." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A includes only the team; stakeholders are critical to product validation.
* B is insufficient-product owner alignment alone doesn't ensure business alignment.
* C refers to documentation, not collaboration.

To ensure that the service will benefit the customer and meet their requirements, the product owner should build a prototype. Prototypes allow the team to create an early, low-fidelity version of the product that can be used to gather direct feedback from the targeted customer segment. This helps to validate whether the service aligns with the customer ' s needs and expectations before investing heavily in full development.

The most effective way to address and correct defects while maintaining predictability and capacity is by working with the team to establish clear coding and quality standards, as well as comprehensive testing policies. By setting these explicit rules, the team will have a shared understanding of the quality expectations and testing requirements, which will help prevent defects from escaping into production. This approach focuses on building quality into the process, rather than reacting to defects after they occur, and supports the long-term goal of improving software quality and predictability without overburdening the team.

The correct answer is C - The team should discuss their definition of done (DoD) and make changes to ensure there is common understanding of the acceptance criteria.
A shared understanding of what "done" means ensures consistent quality across team members. When this understanding is missing, defects and inconsistencies arise. The Definition of Done (DoD) should be reviewed and updated collaboratively to set a clear standard for completeness and quality.
From the PMI Agile Practice Guide:
"The Definition of Done provides a shared understanding of when work is complete. This includes quality criteria, testing, and documentation. It should be revisited regularly to maintain alignment." (PMI Agile Practice Guide, Section 5.2 - Definition of Done) Mike Griffiths emphasizes:
"Quality issues often result from unclear or inconsistent DoD. Revisiting and refining it ensures consistent expectations across the team." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Adaptive Planning) Why the other options are incorrect:
* A (TDD) may help, but won't solve the fundamental alignment issue.
* B accepts a problem without resolving it.
* D imposes a process without team collaboration, which is not agile.

When transitioning to an iterative development lifecycle, it's crucial to ensure that user stories are written with clear, testable acceptance criteria that define the desired outcomes. The agile lead should explain to the project sponsor that the subject matter expert (SME) needs to collaborate with the team, including developers, testers, and the product owner, to ensureeveryone has a shared understanding of the requirements and the solution. This collaboration is essential for defining and refining the user stories to ensure that they deliver value and meet the needs of the stakeholders.