How do you know if a software team is any good? How can you compare teams and the commercial value they are producing? And what are metrics good for anyway? We discuss these, especially the latter, concluding that metrics are triggers for questions not answers in themselves. We look at burn-up and burn-down charts and cycle time, though none of these are fully satisfying.
- Phases of team activity: https://image.slidesharecdn.com/2015-150507130312-lva1-app6891/95/agile-is-for-wimps-toplevel-software-development-in-the-21st-century-19-638.jpg?cb=1431003851
- Burn-up and burn-down charts: https://stayrelevant.globant.com/en/why-you-should-use-burn-up-chart-in-agile-instead/
- Cycle time: https://codeclimate.com/blog/software-engineering-cycle-time/
- Momentum vs urgency: http://testobsessed.com/2020/02/momentum-urgency/
Our new book, Agile Conversations, will be out in May 2020! See https://conversationaltransformation.com where you can pre-order and get a free video when you join our mailing list!
We'd love to hear any thoughts, ideas, or feedback you have about the show.
Email us: see link on conversationaltransformation.com
Tweet us: twitter.com/TShootingAgile
Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2