Actually not. In all Sprints the main goal of the team is to deliver value for the client, and technical debt are not necessarily that. Technical debt is a tricky point, as the team must always pay attention to it, if it is increasing, what is the impact, and so on.
The best choice is to alwys take care of technical debt, in every Sprint. For PO might be hard to know the importance and urgency of a technical debt, even more to understand its priority compared to a functional item (user story). That is why dev team should always help PO on that, raising high risk technical debts that need to be taken care of.
When a team does not pay attention to technical debts, it arrives in a Sprint committing more to non-functional stories (debts) than functional stories that bring value to the product.
2 sujets de 1 à 2 (sur un total de 2)
Vous devez être connecté pour répondre à ce sujet.
Nous utilisons des cookies sur notre site Web pour vous offrir l'expérience la plus pertinente en mémorisant vos préférences et les visites répétées. En cliquant sur «Accepter», vous consentez à l'utilisation de TOUS les cookies.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.