1.
Project Vital Signs

2.
My fellow IT
practitioners… IT has lost
trust and
credibility
with the
business

3.
How?
Poor track record
Poor visibility
ROI hard to quantify

4.
Restoring trust and credibility
begins with the Project

5.
Simply saying
“the Project is ‘on track’”
is not good enough

6.
Need to show
how and why
Project is on track

7.
The Need
Holistic view into the
State of the Project

8.
Project as a Patient

9.
Project as a Patient

10.
In Medicine…
Medical History x Tests x Vital Signs x Experience
ê
Diagnosis
ê
Treatment

11.
Vital Signs

12.
Vital Signs

13.
Vital Signs
Simple, quantitative, near real-time metrics
conveyed via a chart
published to a location
and easily referenced by all

14.
PMBOK Project Levers

15.
PMBOK Project Levers + 1

16.
Objectives with Vital Signs
• Bring
visibility
into
all
5
project
levers
• Simple,
quan9ta9ve,
near-­‐real
9me
metrics
• Publish
to
charts
in
full
public
display
• Where
possible
include
history
and
trends

17.
Project Vital Signs
1) Scope Burn Up
2) Current State of Delivery
3) Budget Burn Down
4) Delivery Quality
5) Team Dynamics

18.
Scope Burn Up

19.
Scope Burn Up
Schedule x Scope
=
Expected Delivery Date

20.
Current State of Delivery

21.
Current State of Delivery
Scope x Team
=
Real-time state of delivery

22.
Budget
Burn
Down

23.
Budget Burn Down
Schedule x Budget
=
$$$tatus

24.
Delivery Quality

25.
Delivery Quality
Schedule x Quality
=
How good is the end product

26.
Alternative to Bugs as a
Measure of Quality

27.
Alternative to Bugs as a
Measure of Quality

28.
Team Dynamics

29.
Team Dynamics
Schedule x Team
=
State of the team at different
stages of delivery

30.
Performing
Norming
Tuckman Model of
Group Development
Storming
http://en.wikipedia.org/wiki/
Forming-storming-norming-performing
Forming

31.
Project Dashboard

32.
Example Scenario

33.
Today is Aug 12
Start of Iteration 5
Production Release
Sep 9, 4 weeks

34.
What is the Current State
of the Project?
What is the Diagnosis?
What (if any)
Treatment
is required?

35.
Vital Signs

36.
Scope Burn Up

37.
Current State of Delivery

38.
Budget Burn Down

39.
Delivery Quality

40.
Team Dynamics

41.
What is the Current State
of the Project?
Not going to make it.

42.
What is the Diagnosis?
The team is firing on all cylinders.
Quality is good.
Not enough time to deliver the full
backlog for the September 9th release.
Not enough money to carry us through
the warranty period ending September
23rd.

43.
What is the Treatment?
Release on Aug 26th instead of Sep 9th.
Includes 35 stories that are ready for,
currently in or have passed QA.
Remaining 20 stories to be included
in a future release, budgeted for
at a later time.

44.
Current State of Delivery : Before

45.
Current State of Delivery : After

46.
Current State of Delivery : After

47.
Scope Burn Up : Before Treatment

48.
Scope Burn Up : After Treatment

49.
Budget Burn Down : Before Treatment

50.
Budget Burn Down : After Treatment

51.
Delivery Quality : After Treatment

52.
Team Dynamics : After Treatment

53.
Key Messages

54.
Transparency
is key

55.
Shared team
responsibility

56.
Project Vital Signs
Agile 2010, ThoughtWorks