Deciding What Should Be Documented Every Sprint

Documentation is an important aspect of software development, but not everything needs to be documented. Deciding what should be documented every Sprint involves considering its value and necessity in maintaining and enhancing the software.

Exam Question

Which two criteria are useful in deciding if something should be documented every Sprint?
(choose the best two answers)
A. It has always been documented in the past.
B. The documentation is used to enhance and maintain the software.
C. It is required by the Definition of Done.
D. The Scrum Master requires it.
E. The software tool being used requires it.

Correct Answers

B. The documentation is used to enhance and maintain the software.
C. It is required by the Definition of Done.

Explanation

Correct Answers

B. The documentation is used to enhance and maintain the software:
Documentation that contributes to the enhancement and maintenance of the software is essential. If the documentation provides value in understanding the software, making future changes, or ensuring its reliability, it should be documented every Sprint. This type of documentation is crucial for long-term sustainability and quality.

C. It is required by the Definition of Done:
The Definition of Done is a shared understanding of what it means for work to be complete. If the Definition of Done requires certain documentation, it must be created every Sprint to ensure that the work is truly complete. This might include user manuals, technical documentation, or other artifacts that are necessary to consider the Increment “done.”

Why the Other Options Are Less Appropriate

A. It has always been documented in the past:
Just because something has been documented in the past doesn’t mean it should continue to be documented every Sprint. The decision to document should be based on its current value and necessity, not tradition.

D. The Scrum Master requires it:
While the Scrum Master can guide the team, the decision to document should be based on the value it adds to the product and its alignment with the Definition of Done, not solely on the Scrum Master’s requirements.

E. The software tool being used requires it:
The requirement by a software tool does not necessarily justify documentation every Sprint. The decision should be based on whether the documentation adds value to the product and aligns with the team’s goals.

Relevance to the PSD Exam

Understanding the criteria for deciding what should be documented every Sprint is crucial for the PSD exam. It ensures that you can prioritize meaningful documentation that supports software quality and maintainability.

Key Takeaways

• Documentation that enhances and maintains the software should be prioritized.
• If the Definition of Done requires certain documentation, it must be created every Sprint.
• The decision to document should be based on value and necessity, not tradition or external requirements that do not add value.

Conclusion

When deciding what to document every Sprint, focus on documentation that adds value by enhancing and maintaining the software and aligning with the Definition of Done. This approach ensures that the documentation is meaningful and supports the overall quality of the product. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSD™ Exam Prep.