Examples of How Agile Metrics can be Faked [#AgileMetrics #FakeAgile #AgileVelocity]

Examples of How Agile Metrics can be Faked [#AgileMetrics #FakeAgile #AgileVelocity]

Typical suggestions on how an increasing velocity is reported without working more:

  1. Accept “mostly” done Product Backlog items as done, and create new tasks to finish them at a later stage.

  2. Accept “buggy” items and create new Product Backlog items to fix the issues.

  3. Add points to bugs.

  4. Include tickets from other teams on your board.

  5. Open and then close fake tickets.

  6. Add tickets for Scrum events.

  7. Change the base value of points / the reference stories.

  8. Multiply the estimate of user stories by 2, use higher numbers during estimation.

  9. Reestimate stories by increasing their complexity after implementation.

  10. Add story points to each sub-task of an item.

  11. Add story points to epics additionally.

  12. Do it slow and steady to show steady growth. Ddo not over-deliver at any time.

  13. In the case of spillover, collect the story points partially and create a new user story with the full estimate for the new Sprint.

  14. Automate tasks and pretend they are still done manually.

  15. Slice an issue into several smaller issues that collectively have a higher estimate.

Overcoming familiar reporting patterns can be hard on the management. However, becoming Agile requires exactly this scraping of beloved habits and adapting to change.

To make the transition easier, start with a simple exercise by teaching managers how any reporting system can be gamed by Scrum Teams that is based on velocity.

Free your mind, and the rest will follow.

Faking Agile Metrics or Cooking the Agile Books:
Business 2 Community

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Don`t copy text!