PMI Agile Certified Practitioner (ACP) Practice Exam

How is Documentation perceived in Agile projects compared to traditional projects?

1. Highly valued in both approaches

2. Less valued in Agile, requiring only sufficient documentation

3. Only utilized for legal compliance

4. Considered a time-consuming necessity

The correct answer is: Less valued in Agile, requiring only sufficient documentation

In Agile projects, documentation is perceived as a tool that should provide value and support the objectives of the project rather than be an end in itself. The Agile Manifesto emphasizes "working software over comprehensive documentation," meaning that while documentation is still acknowledged as necessary, it should be kept to a level that is "just enough" to facilitate collaboration, communication, and understanding among team members and stakeholders. Agile practices advocate for documentation that is lightweight, flexible, and continuously updated rather than exhaustive or overly formal. This approach allows teams to focus on delivering functional and high-quality products, adapting their documentation practices to the shifting needs of the project and the team. Thus, the emphasis is on producing only the documentation that is essential for the project, which enhances efficiency and agility. In contrast, traditional project management often places a greater emphasis on comprehensive and formal documentation as a means to establish clarity and control throughout the project lifecycle. This difference in perspective highlights why documentation is considered less valued in Agile settings, where the priority is to promote communication and facilitate iterative progress over maintaining detailed records.