Value Of Agile Metrics


Published on

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Not a DeveloperFrustration as a PMFrustration with Agile presentations
  • Use the Ignite Project as an example of the War Room keeping people out
  • Centrics offeringTailoring Agile to fit into larger organizationsSOX compliancePMOsDistributed Groups
  • Stories vs Use Cases
  • Start with ToolsRallyPivotal TrackedMingleAgile ZenIdeal Days vs hours
  • Difference between Iteration and Release vs. Backlog
  • Tie back to Ideal Hours
  • Explain why line starts in second week
  • Math not opinion
  • Real World – GoodQA, Dev, QA in later weeks is why the work
  • Value Of Agile Metrics

    1. 1. Technology Service LineAgile Metrics<br />June, 2010<br />
    2. 2. Overview<br /><ul><li>Introduction
    3. 3. The Value of Metrics
    4. 4. Terms
    5. 5. Iteration and Release Plan
    6. 6. Forecasting Velocity
    7. 7. Metrics
    8. 8. Examples
    9. 9. Questions</li></ul>1<br />7/8/2010<br /><br />
    10. 10. Introduction<br />7/8/2010<br /><br />2<br />Alec Finn<br />18 Years in Information Technology the last 6 in the Agile space: <br /><ul><li>Sales Representative
    11. 11. Program / Project Manager
    12. 12. Quality Assurance Manager
    13. 13. Agile Coach</li></ul>Notable Agile Clients:<br /><ul><li>Nationwide
    14. 14. Fidelity
    15. 15. Cintas
    16. 16. Northwestern University
    17. 17. Great American Insurance</li></li></ul><li>The Value of Metrics<br />7/8/2010<br /><br />3<br />The board tells a story to those who look at it.<br />What about those who don’t?<br /><ul><li>Distributed Teams
    18. 18. Senior Managers
    19. 19. Dotted Lined Business Units</li></ul>What about those who see the board but not the big picture?<br />While Agile is an extremely collaborative approach to software development the team still needs to be able to communicate outside their room<br />
    20. 20. Introduction<br />7/8/2010<br /><br />4<br />Agile for the Enterprise<br />
    21. 21. Terms<br />Backlog: A collection of identified work<br />Stories: A business request that can be developed and tested<br />Use Cases: A actor based scenario of how a user walks a system<br />Ideal Days: 8 hours of uninterrupted work <br />Resources: Any individual that delivers against your project scope<br />Status: The stage your Story or Task is in<br />Tasks: A unit of work<br />Iteration: A time boxed group of prioritized tasks that the team has committed to deliver<br />Release: A time boxed collection of prioritized Iterations<br />5<br />7/8/2010<br /><br />
    22. 22. 7/8/2010<br /><br />6<br />Iteration and Release Plan<br />The Iteration and Release plan is the backbone of all your metrics. It’s used to prioritize and track Iteration work within a Release.<br />Minimum of 4 Status<br />Date of Refactor<br />Responsible Individual<br />Skillset<br />High level feature or functionality<br />Map Back to a wall card our a Requirement<br />Executable Action<br />Estimated Output<br />Team Responsible for Delivery<br />Where did this Task Come From<br />
    23. 23. 7/8/2010<br /><br />7<br />Iteration and Release Plan<br />Scheduling a meeting: Original Estimate<br />
    24. 24. 7/8/2010<br /><br />8<br />Iteration and Release Plan<br />Scheduling a meeting: Status<br /><ul><li>Remaining – Work that is in scope but not currently being done
    25. 25. In Progress – Work that is being worked but is not complete
    26. 26. Complete – Work that the team has completed but the business as not confirmed
    27. 27. Verified Complete – Work accepted by the Business</li></li></ul><li>Iteration and Release Plan<br />7/8/2010<br /><br />9<br />
    28. 28. 7/8/2010<br /><br />10<br />Iteration and Release Plan<br />Scheduling a meeting: Task Type<br /><ul><li>New – Work identified after the release has begun
    29. 29. Defect – Error introduced by the development team
    30. 30. Clarification – Rework that is required because a requirement was miss understood</li></li></ul><li>Iteration and Release Plan<br />7/8/2010<br /><br />11<br />
    31. 31. Velocity<br />7/8/2010<br /><br />12<br />Velocity is the rate of speed with which something happens; rapidity of action or reaction.<br />(<br />Velocity measures output not effort.<br />Waiting for <br />Materials<br />Bad Weather<br />Blueprint<br />Review<br />Contractor<br />Availability<br />Waiting for Inspections<br />
    32. 32. Velocity<br />7/8/2010<br /><br />13<br />Resource<br />Project Weeks<br />Ideal Hours<br />Total Available Velocity<br />
    33. 33. Metrics<br />7/8/2010<br /><br />14<br />
    34. 34. Metrics<br />7/8/2010<br /><br />15<br />Remaining work is comprised of Remaining and In Progress Tasks<br />
    35. 35. Metrics<br />7/8/2010<br /><br />16<br />The Value Wheel includes all tasks in a Release regardless of Status<br />
    36. 36. Metrics<br />7/8/2010<br /><br />17<br />
    37. 37. Metrics<br />7/8/2010<br /><br />18<br />
    38. 38. Questions<br />7/8/2010<br /><br />19<br />? ? ?<br />
    39. 39. Contact Info<br />7/8/2010<br /><br />20<br />For Questions or to get a sample Agile Workbook please contact Alec Finn @<br /><br />