Agile teams are constantly running toward goals, requiring constant planning, monitoring, and re-planning. Metrics can help support these efforts by providing useful information about the health and progress of the project.
There are a few common metrics we use in agile teams: sprint burndown charts, release burnup charts, team velocity. They’re common because they communicate practical information, but they’re not the only metrics we can employ.
In my recent articles for TestRail blog, I described 3 Uncommon metrics you can easily create that will be very useful for your agile team. I also wrote about 3 Metrics that are not useful and you must stop using now!
Here are the posts–>
Three Uncommon Metrics Your Agile Team Should Be Tracking
Here I described 3 most useful metrics –
Click here to read the complete article —>
Three Metrics Your Agile Team Should Stop Using
Metrics are supposed to help and support an agile team by providing useful information about the health and progress of their project. But not all metrics are always beneficial. Going overboard with them can sometimes cause more harm than good.
In this post I have described three metrics that can impede your agile team instead of motivating you.
- Defect Counts
- Lines of Code or Defect Fixes per Developer
Click here to read the complete article–>
Please share your experiences with metrics and how they helped or impeded your progress!
One thought on “Metrics your Agile team should & should not be tracking!”
[…] https://testwithnishi.com/2019/12/04/metrics-your-agile-team-should-should-not-be-tracking/ […]