To Fix or Not to Fix : That is the Question - Avangel

Avangel — Wed, 14 Jun 2006 12:08:16 +0200

I think such decision must be an agreement between customers and team, but with sufficient data to make the decision.

For example, team may says customers : "This bug is critical and may impact further functionnalities, but it will need quite a lot of time to fix". In such a cas, the product owner has the elements to take the decision.

Another case is "This bug makes this functionnality uncompleted, and it will cost an average time to fix". In this case, the product owner may consider this functionnality is not important and the bug may be fixed later.

I think like any blocking case in an Agile projet, the main idea is that the team gives its technical view, the product owner has its business view, and then he takes its decision. In this way, we consider both technical and business constraints.

To Fix or Not to Fix : That is the Question - Laurent B.

Laurent B. — Tue, 13 Jun 2006 14:22:59 +0200

Je me permet de proposer un lien en rapport à ce billet instructif:
http://www.codinghorror.com...

L'Agilitateur - To Fix or Not to Fix : That is the Question - Commentaires

To Fix or Not to Fix : That is the Question - Avangel

To Fix or Not to Fix : That is the Question - Laurent B.