PMP · Question #1170
A project team is performing extremely well when it comes to delivering the value-added features to the customer in each sprint. However, they are missing the documentation portion and the project man
The correct answer is D. Make documentation a standard part of the definition of done (DoD).. To ensure documentation is kept current in an agile project, the project manager should integrate it directly into the Definition of Done (DoD) for each increment.
Question
Options
- AAssign a dedicated resource to work on the documentation during the project.
- BCreate a specific sprint to deliver the project documentation.
- CFocus on the documentation after the features are delivered.
- DMake documentation a standard part of the definition of done (DoD).
How the community answered
(25 responses)- A16% (4)
- B4% (1)
- C8% (2)
- D72% (18)
Why each option
To ensure documentation is kept current in an agile project, the project manager should integrate it directly into the Definition of Done (DoD) for each increment.
Assigning a dedicated resource might create a bottleneck or a separate silo for documentation, potentially leading to outdated or misaligned documentation, rather than integrating it continuously.
Creating a specific sprint for documentation goes against the agile principle of delivering integrated, potentially shippable increments, and risks delaying documentation until features are already 'done'.
Focusing on documentation after features are delivered leads to "documentation debt," where it's often rushed, inaccurate, or never completed, negating the agile value of incremental delivery.
Making documentation a standard part of the Definition of Done (DoD) ensures that features are not considered complete until their associated documentation is updated, fostering continuous integration of documentation into the development process.
Concept tested: Agile Definition of Done (DoD) and continuous integration
Topics
Community Discussion
4
Anjali D.Jun 23, 2026D is the right call here, and our group was pretty unified on this one. Adding documentation to the definition of done ensures it gets completed as part of each sprint rather than treated as an afterthought. A few people leaned toward B, but the consensus was that creating a dedicated documentation sprint goes against agile principles and would just delay the work. A and C got some votes too, but the group agreed those options either add unnecessary overhead or kick the can down the road. Anyone else see this one on their exam recently?
Yusuf A.Jun 23, 2026Our senior dev mentioned this exact trap: documentation sprints feel productive but they are basically waterfall in disguise, so D keeps it baked into the workflow where it belongs.
Yusuf A.Jun 26, 2026D is the answer here. The senior PM on my team always says if something keeps getting skipped, it probably is not in the DoD yet, so folding it in makes it non-negotiable. I am still a bit fuzzy though, does adding documentation to the DoD mean every single sprint must produce finalized docs, or just that the work needs to be tracked as incomplete until the docs catch up?
Dervla O.Jul 5, 2026D is the right call here because baking documentation into the DoD means it becomes a non-negotiable exit criterion for every sprint rather than an afterthought. One thing worth clarifying: does adding documentation to the DoD risk slowing velocity if the team has historically treated it as optional, and how do you coach them through that tension without it feeling like a process heavy mandate?