Agile Metrics

56 %
44 %
Information about Agile Metrics
Technology

Published on March 16, 2010

Author: gmarwaha77

Source: slideshare.net

Description

A short presentation on numbers that can be measured for an Agile project

Metrics for Agile projets

Agile I deas / Concepts + Product Mgr Release Mgt Team Product Backlog Release Backlog Iteration – Story Backlog Release Release Iteration – Story Backlog Agile Team Product Owner Agile Coach Product Features Stories Iterations Portfolio Program Project Feature 1 Arch 1 Feature 2 Arch 2 Feature 3 Arch 3

The Agile Package Iterative development Common coding standards Continuous integration Test driven development Team ownership Collaborative modeling Co-located teams Retrospectives Sustainable pace of development Daily stand-ups

Iterative development

Common coding standards

Continuous integration

Test driven development

Team ownership

Collaborative modeling

Co-located teams

Retrospectives

Sustainable pace of development

Daily stand-ups

Feature v/s Story Feature Feature is something about the product which may be sold to the end user; it may have a license attached or sold as bundle with the entire product. Example: PDF generation in MS word Story Story is the smallest unit of value/ requirement/ work which is visible to both project team and product owner. A story may have a description, validation criteria, complexity and business value.

A metric is a standard for measuring or evaluating something. A measure is a quantity, a proportion, or a qualitative comparison of some kind. Quantity : There are five items remaining out of ten in this iteration Proportion : This release required 20% less effort than last one Qualitative comparison : The new version of the software is easier to use than the old version. A metric can: Provide information on trends (Leads) Provides information on outcomes (Lags) Metrics Copyright © 2007-2009 Dave Nicolette

A metric is a standard for measuring or evaluating something.

A measure is a quantity, a proportion, or a qualitative comparison of some kind.

Quantity :

There are five items remaining out of ten in this iteration

Proportion :

This release required 20% less effort than last one

Qualitative comparison :

The new version of the software is easier to use than the old version.

A metric can:

Provide information on trends (Leads)

Provides information on outcomes (Lags)

Selecting Metrics Future orientation How will changes to development processes affect the organization’s ability to deliver value and quality in the future? Business value How do application development projects contribute (directly or indirectly) to quantitative business benefits? User orientation How effective is the team in meeting the users’ needs? Operational excellence How does management measure development teams’ effectiveness? Velocity Features delivered vs. planned Post-iteration feedback/working demo Surveys, Customer-filed defects Earned business value Agile scorecard

Completed Features Objective : Goal of the project is to deliver a working software Measure : Easily measurable from the product backlog. Team can measure the running & tested features Trend: The number of features should increase with time When to measure: This is a continuous measure

Financial Value Objective : Attach a profitability value in monetary terms to every release/ iteration Measure : Profit = Income – Costs Trend: A steady or upward trend is desirable When to measure: Post release

Objective :

Attach a profitability value in monetary terms to every release/ iteration

Measure :

Profit = Income – Costs

Trend:

A steady or upward trend is desirable

When to measure:

Post release

Earned Business Value

Earned Business Value Objective : To measure the earned value to business with each delivery Measure : BV of Services  Issue  Book  Issue Book is calculated as: (1/1) * (4/10) * (8/13) * (5/5) * (2/10) ~= 5% BV (bucket) = BV (parent) * [Wt (bucket) / Wt (bucket) + ∑Wt (sibling) ] EBV is the summation of BV of all stories that have been coded and are up and running Trend: A steady or upward trend is desirable When to measure: Post release When the list of stories and features is finalized else BV may change

Objective :

To measure the earned value to business with each delivery

Measure :

BV of Services  Issue  Book  Issue Book is calculated as:

(1/1) * (4/10) * (8/13) * (5/5) * (2/10) ~= 5%

BV (bucket) = BV (parent) * [Wt (bucket) / Wt (bucket) + ∑Wt (sibling) ]

EBV is the summation of BV of all stories that have been coded and are up and running

Trend:

A steady or upward trend is desirable

When to measure:

Post release

When the list of stories and features is finalized else BV may change

Velocity Velocity is The sum of the estimates of the stories that were completed in an iteration. It is an empirical observation of the team’s capacity to complete work per iteration. It is based on the team’s own sizing of work items It is comparable across different iterations for a given team on a given project Not: an estimate a target to aim for based on estimated or actual time dictated or imposed by anyone other than team members It is not comparable across teams & projects

Velocity is

The sum of the estimates of the stories that were completed in an iteration.

It is an empirical observation of the team’s capacity to complete work per iteration.

It is based on the team’s own sizing of work items

It is comparable across different iterations for a given team on a given project

Not:

an estimate

a target to aim for

based on estimated or actual time

dictated or imposed by anyone other than team members

It is not comparable across teams & projects

Velocity Objective : Customer satisfaction Measure : Stories delivered/ Story points delivered or even ideal hours delivered; the key fact is that only completed items count Trend: Upward or stable trend is expected When to measure: This is a continuous measure

Burn Charts Burn Up chart How much work has been completed Burn Up chart How much work is left or still remains With each iteration remaining work should decrease and completed work should increase Normally iterations are plotted on X axis and Stories/ story points on the Y axis

Burn Up chart

How much work has been completed

Burn Up chart

How much work is left or still remains

With each iteration remaining work should decrease and completed work should increase

Normally iterations are plotted on X axis and Stories/ story points on the Y axis

Other Metrics Code Analysis : The use of tools to perform static code analysis can uncover many details like: Test coverage Primary areas of focus (eg JSPs or controllers) Method complexity Lines of code Documentation v/s code TDD : TDD compilation or execution of tests at build time can provide an inference on the current state of development Story Cycle Time: Number of iterations it takes to complete a story Cycle Time: Average time between delivery of completed work items

Code Analysis :

The use of tools to perform static code analysis can uncover many details like:

Test coverage

Primary areas of focus (eg JSPs or controllers)

Method complexity

Lines of code

Documentation v/s code

TDD :

TDD compilation or execution of tests at build time can provide an inference on the current state of development

Story Cycle Time:

Number of iterations it takes to complete a story

Cycle Time:

Average time between delivery of completed work items

Earned Value Management Measuring actual value of integrated cost, schedule and scope against a baseline plan using Earned Value Management (EVM) metrics It compares the earned value (EV) with the planned value (PV)

Measuring actual value of integrated cost, schedule and scope against a baseline plan using Earned Value Management (EVM) metrics

It compares the earned value (EV) with the planned value (PV)

EVM - Metrics

EVM - Agile Story points are seen as a measure of work planned v/s completed

Story points are seen as a measure of work planned v/s completed

Velocity Report Card

Thank You A lot of material is available over the Internet this presentation is a summarized view and probably presents a set of metrics which can be used in a project following the Agile principles; many thanks to all the people who have shared similar content

Add a comment

Related presentations

Related pages

Agile Metrics - scrum

Agile Metrics Let the Numbers tell the Tale Pro ware ness+ ... The collection of metrics an Agile team should use is context dependent, but it
Read more

Metrics – Scaled Agile Framework

People adjust their behavior based on the metrics used to measure their systems and evaluate their performance, so they will naturally flex their efforts ...
Read more

Agile Atlas | Metrics for a Scrum Team

What sprint metrics do you collect about the team's behaviors? Who does the analysis? We live in a world of data and information. Some people have a ...
Read more

Agile Metrics - Scrum.de

Der Whitepaper Agile Metrics gibt dem Leser Kennzahlen an die Hand, die wir aufgrund unserer Erfahrung im Coaching&Arbeiten mit Agile-Teams ausgewählt haben
Read more

Agile Metrics: Seven Categories - SEI Insights

Agile Metrics: Seven Categories. Posted on September 22, 2014 by Will Hayes in ...
Read more

Five Agile Metrics You Won't Hate | The Agile Coach

How to use agile metrics to optimize your delivery? Learn about sprint burndown, epic and release burndown, velocity, control charts & the cumulative flow ...
Read more

Towards Agile Metrics - ScrumSense

Introduction This document seeks to provide a small yet useful set of metrics that may easily be implemented within an organisation transitioning to Agile.
Read more

Actionable Agile Metrics for Predictability: An ...

Daniel S. - Actionable Agile Metrics for Predictability: An Introduction jetzt kaufen. ISBN: 9780986436338, Fremdsprachige Bücher - Management
Read more

Agile Metrics - Scrum Alliance

Metrics -- different things to different people, organizations, and cultures. However, the underlying focus of measurement is whether or not ...
Read more

agile-metrics.org - Keine Weiterleitung definiert!

Für die Domain "agile-metrics.org" ist keine Weiterleitung definiert! No forwarding is defined for the domain "agile-metrics.org"!
Read more