Asynchrony recently teamed up with Doug Dockery and colleagues from Rally (www.rallydev.com) for a presentation on essential agile metrics to assess the impact of changes made to software development activities at the team level. The presentation affirmed that simple metrics that encompass all team activities can provide valuable insights to allow teams to self-assess the impact of changes they make. It was recommended that teams track a metric or two across each of the following categories:
- Productivity - How much work your team has completed within a period of time? For teams practicing scrum, this data is tracked as “Velocity” - the number of stories completed each sprint. Many teams at Asynchrony have shifted to use kanban (rather than scrum), so this metric could be a simple running tally of how many stories are completed each week - for teams using kanban, you can extract this data from the bottom line of your Cumulative Flow Diagram.