Which statements are true about the Sprint Goal?
(choose the best two answers)
Technical debt is the implied cost of rework caused by choosing an easy solution now instead of a better approach that would take longer1. Reducing the Definition of Done for the next three Sprints will create technical debt, which will have negative impacts on the product quality, value, and delivery. Two ways to explain these impacts to the Product Owner are:
Releasing the version creates false assumptions about the actual state of the system.This is likely to result in interruptions during future Sprints in order to react to unforeseen problems arising from not having met the Definition of Done2. This will reduce the transparency, predictability, and adaptability of the Scrum process, and compromise the trust and satisfaction of the customers and stakeholders.
As development progresses and functionality is added upon the reduced Definition of Done, unknown errors will creep in. The system becomes more difficult to stabilize.Work for the actual release as well as future releases will be slowed down in unpredictable ways3. This will increase the complexity, risk, and cost of the product development, and lower the value and quality of the product.
What is Technical Debt in Scrum? | StarAgile, section ''The technical debt is created when''.
Technical Debt & Scrum: Who Is Responsible? | Scrum.org, section ''What Is Technical Debt?''.
Managing Technical Debt in a Scrum Project | SCRUMstudy Blog, section ''Technical debt accrues''.
Limited Time Offer
25%
Off
Kenneth
1 months agoNan
1 months agoTy
26 days agoRupert
27 days agoReita
2 months agoThad
2 months agoAriel
26 days agoArmanda
27 days agoLajuana
2 months agoViki
2 months agoJules
13 days agoJeniffer
14 days agoMargret
1 months agoVivan
1 months agoJanae
2 months ago