1.

On what metrics would you base the assessment of the value of a user story and which are the metrics that are not acceptable?

Answer»

The focus of the TEAM should be on delivering VALUE to the customer. It is not only the responsibility of the team but also it is important from the organization perspective. Each story is built on the concept of priority and value added to the customer. If the team is able to bring value through frequent deliveries and product increment, then the client will be HAPPY. The client satisfaction can also be one of the metrics to measure, if the client is able to realize value, it will be worth their money.

Another one can be, focus on minimizing the technical debt, once the product development starts, it is important to do the maintenance work from time to time to ensure the performance of the product, no one wants a dead code in the system. Bugs, refactoring, and research also requires regular attention to avoid building-up technical debt. Any metrics which cannot relate to the value delivered should be avoided in such scenarios as they portray a different picture, e.g, though velocity variance is a good metric to track if I relate to value DELIVERY it won’t work well.

Hence, the focus should always be on value delivery, and it should be the prime goal.



Discussion

No Comment Found