We hosted a popular webinar with XBOSoft last week on agile metrics. One of the questions that came up but due to time constraints we could not cover in depth was if it is useful to have different metrics for the different roles in an agile team. And specifically if project managers and their team members should have different metrics and what metrics agile project managers should use.


Agile Metrics Roles

Different Roles – Same Goals

Co-Founder of Grip and one of the speakers at the webinar, Kamiel Wanrooij, says, “On the highest level a company or team should have shared goals toward which everyone is working. However since different team members are responsible for different activities it is good to have different metrics to keep track of the outcome and impact of those activities.”


“Project management activities are mostly about prioritizing, scheduling, budgeting and managing expectations for all stakeholders,” says Kamiel. “Important metrics for people with a project management role are related to velocity, can we deliver timely. Scope changes, which would also impact the ability to deliver on time,” Kamiel continues. “Another Metric I always recommend for this role is defect removal effectiveness, which tell me something about the quality of delivery and the effectiveness of the team. When defect removal efficiency drops, the team might be under high stress to deliver each iteration. ”


“The team is working on implementation, they want to make sure they can deliver what they committed to. So they will also care for velocity but will look at it from a more technical perspective.  Maintainability for instance, is important to them, says Kamiel. “Good metrics for maintainability are, code complexity, code duplication and code independence, because they say something about technical debt and issues that may impact their ability to deliver.

 Guest Post from GripQA