Vital Signs Thoughtworks

629 views
596 views

Published on

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Eduardo,



    You downloaded from slideshare a presentation I produced(http://www.slideshare.net/spantazopoulos/project-vital-signs), stipped out any mention of me, and then reposted it under your name where it says 'Vital Signs ThoughtWorks' by Eduardo Fayh.



    I am not impressed.



    - Stelios
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
629
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
16
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Vital Signs Thoughtworks

  1. 1. Project Vital Signs
  2. 2. My fellow ITpractitioners… IT has lost trust and credibility with the business
  3. 3. How? Poor track record Poor visibilityROI hard to quantify
  4. 4. Restoring trust and credibility begins with the Project
  5. 5. Simply saying“the Project is ‘on track’” is not good enough
  6. 6. Need to show how and whyProject is on track
  7. 7. The NeedHolistic view into the State of the Project
  8. 8. Project as a Patient
  9. 9. Project as a Patient
  10. 10. In Medicine…Medical History x Tests x Vital Signs x Experience ê Diagnosis ê   Treatment
  11. 11. Vital Signs
  12. 12. Vital Signs
  13. 13. Vital SignsSimple, quantitative, near real-time metrics conveyed via a chart published to a location and easily referenced by all
  14. 14. PMBOK Project Levers
  15. 15. PMBOK Project Levers + 1
  16. 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. 17. Project Vital Signs1)  Scope Burn Up2)  Current State of Delivery3)  Budget Burn Down4)  Delivery Quality5)  Team Dynamics
  18. 18. Scope Burn Up
  19. 19. Scope Burn Up Schedule x Scope =Expected Delivery Date
  20. 20. Current State of Delivery
  21. 21. Current State of Delivery Scope x Team =Real-time state of delivery
  22. 22. BudgetBurnDown
  23. 23. Budget Burn DownSchedule x Budget = $$$tatus
  24. 24. Delivery Quality
  25. 25. Delivery Quality Schedule x Quality =How good is the end product
  26. 26. Alternative to Bugs as a Measure of Quality
  27. 27. Alternative to Bugs as a Measure of Quality
  28. 28. Team Dynamics
  29. 29. Team Dynamics Schedule x Team =State of the team at different stages of delivery
  30. 30. Performing NormingTuckman Model ofGroup Development Storminghttp://en.wikipedia.org/wiki/Forming-storming-norming-performing Forming
  31. 31. Project Dashboard
  32. 32. Example Scenario
  33. 33. Today is Aug 12Start of Iteration 5Production Release Sep 9, 4 weeks
  34. 34. What is the Current State of the Project? What is the Diagnosis? What (if any) Treatment is required?
  35. 35. Vital Signs
  36. 36. Scope Burn Up
  37. 37. Current State of Delivery
  38. 38. Budget Burn Down
  39. 39. Delivery Quality
  40. 40. Team Dynamics
  41. 41. What is the Current State of the Project? Not going to make it.
  42. 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. 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. 44. Current State of Delivery : Before
  45. 45. Current State of Delivery : After
  46. 46. Current State of Delivery : After
  47. 47. Scope Burn Up : Before Treatment
  48. 48. Scope Burn Up : After Treatment
  49. 49. Budget Burn Down : Before Treatment
  50. 50. Budget Burn Down : After Treatment
  51. 51. Delivery Quality : After Treatment
  52. 52. Team Dynamics : After Treatment
  53. 53. Key Messages
  54. 54. Transparencyis key
  55. 55. Shared teamresponsibility
  56. 56. Project Vital Signs Agile 2010, ThoughtWorks

×