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?
A. Agree that documentation should be avoided, since it slows the progress of the team.
B. Explain that interactions are valued over documentation, but documentation is not forbidden.
C. Ask the manager if the technical processes mandate that designs be documented.
D. Ask the Product Owner if it is acceptable for the resources to spend time on documentation.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
The Agile Manifesto supports “B” as the correct answer. Documentation is not prohibited. The Definition of Done that is written by the team should provide guidance on what documentation is required, how it is structured, where it resides, and to what extent. But none of this prevents a customer from requesting specific documentation that could be represented as a story.