Big visible charts for the business

1,611 views

Published on

Many business and IT management stakeholders see the benefit of Agile, but don't know how to integrate the practices in to their organization.

How do you get status, monitor progress, and evaluate risk? Learn how business stakeholders and IT management engage with an Agile team.

A core tenant of Agile is to make things big and visible. This slide deck is from our webinar where we reviewed the typical questions leadership has of a team, and compares the traditional way of answering those questions to an agile perspective. Examples from 10 years of Big Visible Charts will include:

•Will I hit my target date?
•Will I stay under budget?
•How does this align to my IT strategy?

The analyst and IT advisory firm Gartner has identified that "Increasing the use of information / analytics" is the #3 priority of CIO's globally this year. Review this deck to gain practical insights which will directly support both your business stakeholders and IT executives. We also invite you to download the replay of the event with full audio at http://pillartechnology.com/events.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,611
On SlideShare
0
From Embeds
0
Number of Embeds
61
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Big visible charts for the business

  1. 1. Big Visible Charts for the Business Attend The Path To Agility Conference May 27 – Columbus Ohio thePathToAgility.org
  2. 2. Agenda • What is a Big Visible Chart • How do they help the Business and IT communicate • What are the Rules for creating Big Visible Charts • Examples
  3. 3. SURVEY WHO ARE YOU?
  4. 4. SURVEY WILL THIS PROJECT BE DONE ON TIME?
  5. 5. SURVEY WILL THIS PROJECT BE DONE ON TIME?
  6. 6. Concept 1: Make it Big and Visible • If you make a problem visible many times it will take care of it self – This is true at work, home, society, etc. • A picture is worth a 1000 words – Should Create Action – Should Set Mood
  7. 7. Component Test Coverage Address Service 85% Customer Service 87% Contract Service 22% … 92% … 77%
  8. 8. Component Test Coverage Address Service 85% Customer Service 87% Contract Service 22% 55% 84% … 92% … 77%
  9. 9. Concept 2: Manage based on Data not opinion • If you are getting status by asking the people doing the work you are just guessing.
  10. 10. SURVEY WITCH PROJECT IS FURTHER ALONG?
  11. 11. HOW THEY HELP
  12. 12. What Can they measure? • Any question you care about – When will development be complete? – Am I going to stay on budget? – When will we be in production? – Is the business happy?
  13. 13. Are there rules? • Keep them as simple as possible • Collaborate • Keep them up to date • Resist automation (initially) • Rarely are emails big and visible
  14. 14. Common Mistakes • Using a Chart that answers a different than you are asking? • Forgetting that different people have different questions? • Forgetting that people’s concerns can change over time? • Loosing the fact that the chart is for the user not the producer. • Keep It Simple – reader should not need training to read • Bad Data = Lost Confidence / Credibility
  15. 15. Types of Big Visible Charts • Trend Based – Usually something over time – Reader interprets – Easy to create • Status – Usually red / Green type items • Is the Build working • Are we on time – Builder/Metric Interprets • Be sure it is right • Inspect under the covers
  16. 16. gantt chart 22 29 April 2010
  17. 17. Practice Quality Spider Chart PO 100% 63% 75% CV RP 66% 50% 44% 25% 0% 65% 48% DP IP 55% 63% TP TE
  18. 18. Examples • Will I hit my target date? – Work Burn Down Chart • Will I stay under budget? – Budget Burn Down • How does this align to my IT strategy? – nnn • Is my project adding value? – Value Story Delivery
  19. 19. Tracking Delivery Date
  20. 20. Gantt vs. Burn Down • Gantt Chart • Burn Down Chart – Sequence of Tasks – Scope – Task Length – Velocity – Time Spent – Value Delivered Time Spent Value Delivered Task Length Velocity Sequence Scope of Tasks 26 Key Difference: 29 April 2010 Burn Down measures output
  21. 21. How does it work? - Estimating Work Verified By Business Complete This is the Project Effort Remaining Work 27
  22. 22. reading and interpreting a BVC – what is the end date? 120 100 0 10 11 10 20. 5 15 15 40 80 55 18 14 60 14 15 90 13 12 40 80 65 13 51 20 37 25 0 38353 38360 38367 38374 38381 38388 38395 38402 V er i f i ed Compl et e 11 20. 5 40 55 Compl et ed Day s 0 10 15 18 15 13 A c t i v e Day s 10 15 14 14 12 13 Remai ni ng Day s 90 80 65 51 37 25 28 29 April 2010
  23. 23. You read the chart? 29 29 April 2010
  24. 24. SURVEY WHAT IS HAPPENING TO PROJECT SCOPE?
  25. 25. Tracking Budget
  26. 26. 1200000 1000000 800000 600000 Remaining budget Projected Remaining Spend 400000 200000 0 1 2 3 4 5 6 7 8 9 10 11 12
  27. 27. 1200000 1000000 800000 600000 Remaining budget Projected Remaining Spend 400000 200000 0 1 2 3 4 5 6 7 8 9 10 11 12
  28. 28. 1200000 1000000 800000 600000 Remaining budget Projected Remaining Spend 400000 200000 0 1 2 3 4 5 6 7 8 9 10 11 12
  29. 29. Tracking Value Delivered
  30. 30. Release 1 Value Delivered 300,000 250,000 200,000 150,000 100,000 50,000 Release 1 Value Delivered 0 1 2 3 4 5 6 7 8 9 10 11 12 -50,000 -100,000 -150,000 -200,000
  31. 31. Release 2 Value Delivered 150000 100000 50000 0 Release 2 Value Delivered 1 2 3 4 5 6 7 8 9 10 11 12 -50000 -100000 -150000
  32. 32. Release 3 Value Delivered 60000 40000 20000 0 1 2 3 4 5 6 7 8 9 10 11 12 -20000 -40000 Release 3 Value Delivered -60000 -80000 -100000 -120000 -140000
  33. 33. Release 4 Value Delivered 0 1 2 3 4 5 6 7 8 9 10 11 12 -20000 -40000 -60000 Release 4 Value Delivered -80000 -100000 -120000 -140000
  34. 34. Multiple Consecutive Releases 300,000 250,000 200,000 150,000 100,000 Release 1 Value Delivered Release 2 Value Delivered 50,000 Release 3 Value Delivered Release 4 Value Delivered 0 1 2 3 4 5 6 7 8 9 10 11 12 -50,000 -100,000 -150,000 -200,000
  35. 35. Total Value Delivered 500,000 400,000 300,000 200,000 100,000 Total Value Delivered 0 1 2 3 4 5 6 7 8 9 10 11 12 -100,000 -200,000 -300,000
  36. 36. Incremental Release vs. Single Release 600,000 400,000 200,000 0 1 2 3 4 5 6 7 8 9 10 11 12 One Release (all 4 Value Stories) Value Story Based Releases -200,000 W h -400,000 e r -600,000 e -800,000 w o u l d
  37. 37. Additional Resources •Upcoming Webinars: Please visit http://pillartechnology.com/events. •All of the webinar content is available to your business in a 1-2 day on-site workshop or as a “lunch and learn” format. Please contact us for details. •Visit www.pillartechnology.com/events to access presentation slides and full archived broadcasts of past webinars. •Twitter.com/agilesoftware •Blog: www.pillartechnology.com/blog •LinkedIn: Join the Agile Enthusiast Group on LinkedIn: http://bit.ly/agilegroup •YouTube: http://www.youtube.com/user/PillarTechnology •Phone: (888) 3-pillar •Web: pillartechnology.com •Email: info@pillartechnology.com act differently.

×