Technical debt

Front Page Forums Agilité Technical debt

2 sujets de 1 à 2 (sur un total de 2)
  • Auteur
    Messages
  • #2897
    contact@crossthink.fr
    Maître des clés

    Is it a good practice to have from time to time a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality?

    #2898
    contact@crossthink.fr
    Maître des clés

    Hello!

    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.