Definitely. I think I’ve expressed myself wrong — I have originally started gathering these data for myself to see if there are valuable trends and signs I may get of it. (e.g. the pitfall team had in velocity between Sprints 7 and 10 (42 > 31 > 27 > 42) may have looked bad if I didn’t have additional data to analyze like Throughput, # of bugs and unplanned work) When I understood that the data seem representative and useful, we’ve started using it as one of the things to provide input for our Retrospectives.
Measuring Throughput, WIA and watching how does it co-relate with Velocity was also one of the steps I took to make the team ready to try #NoEstimates approach.

--

Org Design consultant, Trainer & LeSS Coach @ Agile Expat | Head of Agile Practices @ PandaDoc | Professional Scrum Master | CMI Team Coach | Kanban Coach

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Agile Expat by Denis Salnikov

Agile Expat by Denis Salnikov

Org Design consultant, Trainer & LeSS Coach @ Agile Expat | Head of Agile Practices @ PandaDoc | Professional Scrum Master | CMI Team Coach | Kanban Coach