Skip to main content

Scrum Team Metrics (necessary and sufficient)

What metrics would a great Scrum team want to generate and track the trend?

Is the necessary and sufficient set of metrics just velocity?  No - I don't think that is enough.  Can you help me define a short list of metrics, and the reasons for tracking them?

First let's lay out some ground rules.  Who is responsible for generating the metrics?  Are all metrics treated the same, e.g. should each metric have the same visibility?  I'll state the the team is responsible for generating the metrics.  This ensures that the metric has some minimun level of veracity.  When the team believes that the metric does not tell the truth, they should make that visible and change how it is generated.  This is process improvement.  However not all metrics need be treated the same.  Some should be published, some could stay internal to the team.  As the level of trust and autonomy of the team increases the visibility of metrics should naturally become more transparent.

Here's a rough draft list - to get the conversation started.  Add your comments and additional metrics.  We will see if we can crowd source a great list.

Metrics for the Team
  • Story point velocity per sprint
  • Projected capacity (in person-days) of next sprint
  • Projected capability (in story points range) of next sprint
  • Planned capability of the sprint (in story points)
  • Story points done and accepted by PO of the sprint
  • Story's started but not done (in story points and stories)
  • Discovered work added to the backlog (in story points and stories)
  • Scope increase/decrease during the sprint.
  • Technical debt incurred this sprint (in story points)
  • Cost of sprint
  • Impediments discovered/removed/escalated
  • Sprint - pass/fail

Metrics for the Program
  • Release burn up (in story points)
  • Scope increase/decrease (and reasons for change)
  • Projected completion date range (optimistic & pessimistic)
  • Impediments discovered/removed
  • Risk mitigated, (unknown) risk realized

Metrics for the Organization

See Also:  a follow up post Metrics for the Scrum Team

Visualizing Agility: Agile Metrics that Matter by Jay Packlick

ODIM - a metric selection tool; by Larry Maccherone


4 comments

Most Popular on Agile Complexification Inverter

Software Development terms applied to Home Construction

Let's Invert the typically wrong headed view of Software Development project management as a construction project.  We can map it the other way just to see if it works... to have some fun, to explore the meaning of phrases we toss around quite frequently.


Normally Project Management terms come from a construction domain.  We are going to apply the lexicon of modern software to the construction of a home.  We will follow the construction project and meet some of the people doing the work.

This is a very small (8 homes from $600,000 skyward) program in my 30-40 year old neighborhood.

About 6 months ago I saw the programs landing page go up.  It gives casual observers and some of the stakeholders a general idea of the intent of the program.  And most importantly who to contact for additional information if you happen to be interested in their products.

The Refuge program has 8 product projects and has them running independently.  Yet much of their DevOps infrastructure has already b…

Where is Shakespeare When We Need Him?

We are desperately searching for a term for people that connotes the best of human kind.  The creative, sensing, combinatorial synergistic, empathic solutioning persons that have yet to been labeled with a role name that works.

Some of the old terms:
Staff, Workforce, Human Resource, My Team, Army, Company

Shakespeare created 1700 words in his time.  He mutated verbs to nouns, and vice-a-versa, transformed verbs into adjectives, and formed words from whole cloth never before heard.  This skill is rare, but there is a poet that can create the term we need in the twenty-first century.

What should this term define?

21st Century Human Resource; the generalizing specialist.

Yes, but what more?  What less?

Suggest your poetry in the comments, let us see if we cannot do 1/1700 as well as The Bard.

By-the-way; who create the phrase "coin a word"?



A TED Play List - How do you create new words
6:52
Erin McKeanGo ahead, make up new words! In this fun, short talk from TEDYouth, lexicographer Er…

a little feedback please...

some feedback please...
How do you like the new look and feel of our site?
  ___)  nah (I like the old one better - bring it back)
  _X_)  yeah (much cleaner and easy to navigate)



powered by Typeform
See Also:

One Dark and Stormy during a Hurricane

I'm from the Carolina's where legend has it that our family commonly just hunkered down in the home on the coast and waterways than to head for inland shelter. Now that's from the old school days of barely improved (read paved) roads. They counted a storms severity by how high on the back porch steps (about 15 - top to ground) the water reached.  I don't recommend this action in todays world of long range forecast and transportation options.

I do recommend a drink or two in a hotel bar, far far away.

This is the week that Harvey came ashore in Texas.  I live on a hill in the little old town of Grapevine outside Dallas and Fort Worth.  And thank you all for letting me know that a storm is coming... I didn't get out and walk Malibu before the rain hit, so I grabbed a hat and we went anyway.  Much nicer walk with the drizzle, I'd say.

I'll raise a glass to you - if you were not smart enough to do the responsible thing, at the last responsible moment.

I do re…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…