I am trying to come up with a meaningful metric in order to track performance for our agile development teams. We utilize 30 day sprints and I want to use the following data that we collect to develop a meaningful metric that an executive can look at and understand the current performance and the true meaning of the numbers they see.
** Number of developers - this could range from 3 to 7 developers
** Work Committed To (total for all developers) - at the beginning of each sprint, each developer commits to a certain amount of work
** Work completed to date - how much has the team completed so far.
** Work remaining - how much work is remaining to complete
** Days left in sprint - How many more days are remaining until the end of the sprint
So if for example I have the following data:
** Number of developers: 5
** Work Committed To (total for all developers): 120 days
** Work completed to date: 30 days
** Work remaining : 90 days
** Days left in sprint: 20 days
I'm looking for the overall performance of the entire team, not by individual.
I wrote an article on using a method called Line of Balance to track the progress of trouble reports. I am working on extending the concept to features in FDD and user stories in SCRUM but I have a couple more iterations to go. Please let me know if you find the concept useful and if you want a draft of the other article. Saving Changes...
Wayne MackRetired| RetiredSouth Riding, Va, United States
Hi Susan, why not just try a simple burndown chart for a sprint and one for product backlog? I would avoid saying this chart represents the "performance of the team"; it merely reflects progress on the product. Also, invite the executive(s) to the sprint review - this will provide far more information on the status of the effort than any metric or report. Of course it is management's call, but I would encourage them to attend the review meetings or even daily stand up meetings in lieau of just reading a report in their offices. Saving Changes...
