Value of metrics

Technology Service LineAgile Metrics
June, 2010

Overview
Introduction
The Value of Metrics
Terms
Iteration and Release Plan
Forecasting Velocity
Metrics
Examples
Questions
1
7/8/2010
www.centricconsulting.com

Introduction
7/8/2010
2
Alec Finn
18 Years in Information Technology the last 6 in the Agile space:
Sales Representative
Program / Project Manager
Quality Assurance Manager
Agile Coach
Notable Agile Clients:
Nationwide
Fidelity
Cintas
Northwestern University
Great American Insurance

The Value of Metrics
7/8/2010
3
The board tells a story to those who look at it.
What about those who don’t?
Distributed Teams
Senior Managers
Dotted Lined Business Units
What about those who see the board but not the big picture?
While Agile is an extremely collaborative approach to software development the team still needs to be able to communicate outside their room

Introduction
7/8/2010
4
Agile for the Enterprise

Terms
Backlog: A collection of identified work
Stories: A business request that can be developed and tested
Use Cases: A actor based scenario of how a user walks a system
Ideal Days: 8 hours of uninterrupted work
Resources: Any individual that delivers against your project scope
Status: The stage your Story or Task is in
Tasks: A unit of work
Iteration: A time boxed group of prioritized tasks that the team has committed to deliver
Release: A time boxed collection of prioritized Iterations
5
7/8/2010

7/8/2010
6
The Iteration and Release plan is the backbone of all your metrics. It’s used to prioritize and track Iteration work within a Release.
Minimum of 4 Status
Date of Refactor
Responsible Individual
Skillset
High level feature or functionality
Map Back to a wall card our a Requirement
Executable Action
Estimated Output
Team Responsible for Delivery
Where did this Task Come From

7/8/2010
7
Scheduling a meeting: Original Estimate

7/8/2010
8
Scheduling a meeting: Status
Remaining – Work that is in scope but not currently being done
In Progress – Work that is being worked but is not complete
Complete – Work that the team has completed but the business as not confirmed
Verified Complete – Work accepted by the Business

7/8/2010
9

7/8/2010
10
Scheduling a meeting: Task Type
New – Work identified after the release has begun
Defect – Error introduced by the development team
Clarification – Rework that is required because a requirement was miss understood

7/8/2010
11

Velocity
7/8/2010
12
Velocity is the rate of speed with which something happens; rapidity of action or reaction.
(Dictionary.com)
Velocity measures output not effort.
Waiting for
Materials
Bad Weather
Blueprint
Review
Contractor
Availability
Waiting for Inspections

Velocity
7/8/2010
13
Resource
Project Weeks
Ideal Hours
Total Available Velocity

Metrics
7/8/2010
14

Metrics
7/8/2010
15
Remaining work is comprised of Remaining and In Progress Tasks

Metrics
7/8/2010
16
The Value Wheel includes all tasks in a Release regardless of Status

Metrics
7/8/2010
17

Metrics
7/8/2010
18

Questions
7/8/2010
19
? ? ?

Contact Info
7/8/2010
20
For Questions or to get a sample Agile Workbook please contact Alec Finn @
Alec.Finn@CentricConsulting.com

Value of metrics

by Alex Yastrebenetsky on Jul 10, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 36

Statistics

Value of metrics — Presentation Transcript