Correlation Between “Technical Debt” and “Not Done” Work

Technical debt and “Not Done” work are closely related concepts that significantly impact the quality and transparency of a Scrum Team’s output. Both terms refer to aspects of work that are incomplete or not fully aligned with the product’s requirements and quality standards. Understanding their correlation is essential for maintaining a sustainable pace of development and ensuring that the team consistently delivers valuable Increments.

Exam Question

Discuss the correlation between “Technical Debt” and Not “Done” work?
Discuss how “Technical Debt” and Not “Done” work relate to the Definition of “Done.” Is one better than the other?
What can be done to ensure the transparency of “Technical Debt” and Not “Done” work?

Explanation

Correlation Between “Technical Debt” and “Not Done” Work

• Definition:
  Technical Debt: Refers to the consequences of shortcuts or compromises made during the development process. This can include inadequate testing, poor code quality, or incomplete documentation. Technical debt represents work that needs to be revisited and improved to maintain the product’s overall quality.
  Not Done Work: Refers to Product Backlog items or parts of them that were planned for completion within a Sprint but were not finished by the end of the Sprint. This work has not met the Definition of Done and cannot be considered part of the Increment.
• Correlation:
  Both technical debt and “Not Done” work represent a gap between the current state of the product and its desired state. If “Not Done” work accumulates, it can contribute to technical debt, as incomplete features may lack essential elements such as thorough testing or proper integration. Similarly, accumulating technical debt can lead to more “Not Done” work in future Sprints as the team struggles to maintain the existing codebase.

Relationship to the Definition of “Done”

• Ensuring Quality:
  The Definition of Done is a shared understanding of what it means for a Product Backlog item to be completed. It includes criteria such as code quality, testing, and documentation. Both technical debt and “Not Done” work indicate that a Product Backlog item has not fully met the Definition of Done.
• Comparison:
  Is One Better than the Other?
  Neither technical debt nor “Not Done” work is preferable. Both are indicative of underlying issues that need to be addressed to ensure the product’s long-term success. However, “Not Done” work is more immediately visible since it is clearly identified as incomplete at the end of a Sprint. Technical debt can be more insidious, gradually accumulating until it becomes a significant obstacle to progress.

Ensuring Transparency

• Visibility:
  Technical Debt: The team should make technical debt visible by tracking it explicitly in the Product Backlog or as part of the team’s work management tools. This allows the team and stakeholders to prioritize and address technical debt systematically.
  Not Done Work: Any “Not Done” work should be returned to the Product Backlog for re-prioritization and refinement. This ensures that the work remains visible and is planned for completion in a future Sprint.
• Regular Inspection:
  The Scrum Team should regularly inspect both technical debt and “Not Done” work during Sprint Reviews and Retrospectives. This helps the team understand the impact of these issues on their ability to deliver value and make informed decisions about how to address them.
• Adaptation:
  The team can adapt their Definition of Done to include more stringent criteria that prevent the accumulation of technical debt and reduce the likelihood of “Not Done” work. For example, the team might include automated testing or peer code reviews as part of the Definition of Done.

Relevance to the PSM III Exam

Understanding the relationship between technical debt, “Not Done” work, and the Definition of Done is crucial for Scrum practitioners aiming to maintain a high standard of product quality. In the PSM III exam, demonstrating knowledge of how to manage these issues effectively is essential for showcasing advanced Scrum mastery.

Key Takeaways

• Technical Debt: Represents compromises in quality that need to be addressed to maintain the product’s long-term success.
• “Not Done” Work: Refers to work that has not met the Definition of Done and should be re-prioritized and completed in future Sprints.
• Transparency: Both technical debt and “Not Done” work should be made transparent through regular inspection, tracking, and adaptation.

Conclusion

Managing technical debt and “Not Done” work is essential for maintaining a sustainable pace of development and ensuring that the Scrum Team delivers high-quality Increments. By making these issues transparent and addressing them systematically, the team can improve their ability to deliver value consistently. For more insights into Scrum practices and to prepare for the PSM III exam, visit our Scrum Master PSM III™ Exam Prep.