To ensure high code quality, especially for critical products, agile teams employ technical practices like pair programming and peer code reviews. The PMI Agile Practice Guide (Section 5.5: Technical Practices and Quality) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 5: Quality and Technical Excellence) support these practices as part of built-in quality-ensuring that issues are caught early in the development cycle.
* Option A is correct: pair programming and peer reviews increase code quality and reduce defects early.
* Option B is essential but a feedback tool-not a direct quality assurance practice.
* Option C implies waterfall-style handoffs.
* Option D is inefficient and risky without integrated testing or validation.

The correct answer is A - Teach the team the appropriate agile principle, obtain consensus, and drive adoption.
Agile values "working software over comprehensive documentation." However, this does not mean eliminating all documentation, but rather focusing on documentation that delivers value.
PMI Agile Practice Guide states:
"Agile teams should regularly question whether the work being done adds value, including documentation. If documentation does not serve a current need or stakeholder, it should be minimized or eliminated." (PMI Agile Practice Guide, Section 2.2 - Agile Manifesto) Mike Griffiths further supports this in his exam prep book:
"Agile team members are encouraged to surface inefficiencies and suggest improvements. This is an example of continuous improvement and shared responsibility." Option A aligns with both the Agile Manifesto and the principle of team empowerment. Options B, C, and D either avoid accountability or introduce hierarchy that agile teams seek to minimize.

To assess process efficiency, agile teams use value stream mapping to identify waste, delays, and non-value- adding steps. According to the PMI Agile Practice Guide (Section 5.5 Process Analysis and Value Stream Mapping), value stream analysis helps determine how efficiently a process converts inputs into valuable outputs, making it ideal for supporting customer inquiries on operational performance.
Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 7: Continuous Improvement) reinforces the value of using value stream mapping for both software development processes and operational workflows to increase transparency and drive improvements.
* Option B is correct: reviewing the value stream provides a structured way to evaluate efficiency.
* Option A and D are important for team improvement and performance but don't focus on process activity efficiency.
* Option C relates to value prioritization, not operational efficiency.

Understandingproduct vision and customer goalsis foundational to agile. According to thePMI Agile Practice Guide (Section 2.1 Agile Mindset and Values), early engagement helps teamsconnect their work to real customer outcomes, which increasesmotivation, alignment, and value delivery.
Mike Griffiths (PMI-ACP Exam Prep Book, Chapter 2: Agile Principles and Mindset) also notes thatclear understanding of business goalsensures that team members build the right thing-not just build things right.
* Option Ais correct: aligning the team with the product's purpose drivesvalue-oriented thinking.
* Option Bis secondary-understanding comes before acceptance.
* Option Cis unrealistic and not the goal of this meeting.
* Option Dmay occur, but the main benefit is deeper alignment with value.