- Finding bottlenecks from the wall or a CFD and taking actions to fix the problems.
- Looking critically at retrospective action items and seeing that all those issues are fixed (especially if they are issues outside the teams control, like infrastructure).
- Making sure that the right capabilities exist in the team at the right time. If not, get people from outside, arrange training, etc.
They want to organise the whole world into neat boxes and label them and track anything and everything possible. The walls soon fill up with useless charts with graphs and numbers that the team can’t use in any way. The worst part is, there is no analysis done around the data even by the people who gather it. Having people in a 15 member team draw emotional seismographs every iteration and sticking them on the wall is of no use if you are not going to make any decisions based on them.
So guys, here’s a humble request. Figure out with your client what kind of data he would like to see. Figure out as a team what you would like to improve and what data needs to be gathered to help you get there. Don’t burden your team with things that obstruct OR slow down the flow. Keep it simple and keep it lean.
Our job is to provide quality software not elaborate reports.
Sometimes some managers become paranoid and try to take refuge in metrics when clients ask questions related to quality or productivity. I had a painful time in a past project where a simple label change was estimated at about 5 hours of effort! And why so much time? Cuz there were a few excel sheets across different files that need to filled up, things that needed to be signed (yes on physical paper and then scanned to b stored as an electronic proof that something was adhered to!) .. so much for software development … needless to say I got out of that project the earliest I could.