Agile Metrics – Part I
In the recent past we have wondering about what metrics to track. Our aim from the metrics study is to:
a. Improve the process by which things get done
b. Foster project collaboration practices and environment
c. Create an energized and informative workspace
Our current thinking is that we must track the following metrics:
a. Project Backlog – exists, when was it updated, reflects current realities, everyone has access to it, everyone contributes to it, are changes in different versions recorded?
b. Sprint Backlog – mostly the above but is it accompanied with sprint retrospectives for previous sprints and sprint plans for previous as well current sprints?
c. Sprint Plans – developer availability [hours] and total work output documented and communicated to the management and the client
d. Retrospectives – how often are they done, who attend the same and what actions are taken on identified items
e. Engineering Practices – how does the team actually build software, how much of it is automated workspace, how does information flow, what percentage of code is unit test code driven
f. Trainings – how often the team is trained in new soft and hard skills
g. Innovation – what did and how did the team innovate
h. Knowledge Management – how did the learning translate into knowledge, was this knowledge available and used
We have tried to keep it simple and not unnecessarily complicated. However, even the above seem like quite handful to measure. A team member also pointed out that “How to measure” is an interesting aspect of debate as well.
Part I is rarely a destination, its just a start of a journey. Here is hoping for an exciting and adventure filled journey.