PMI-ACP Question #213: Real Exam Question with Answer & Explanation

Question

During iteration planning, the team is discussing the design for a user story. A team member states that a design document should be started since the system is complex in nature. Another team member responds that in Agile there is no documentation. How should the ScrumMaster respond?

Options

• AAgree that documentation should be avoided, since it slows the progress of the team.
• BExplain that interactions are valued over documentation, but documentation is not forbidden.
• CAsk the manager if the technical processes mandate that designs be documented.
• DAsk the Product Owner if it is acceptable for the resources to spend time on documentation.

Explanation

The Agile Manifesto states 'Working software over comprehensive documentation' — meaning documentation is less valued than direct collaboration, but it is not prohibited. The ScrumMaster's role is to coach the team on Agile values and correct misconceptions. Saying documentation should be avoided entirely (A) misrepresents Agile. Escalating to a manager (C) or Product Owner (D) is unnecessary and undermines team self-organization. The correct response is to clarify that Agile prefers face-to-face interaction over heavy documentation, but when documentation provides genuine value (as with a complex system design), it is absolutely allowed and sometimes encouraged.

No community discussion yet for this question.