Value Of Agile Metrics

  • 1,114 views
Uploaded on

 

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,114
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
37
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    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

Transcript

  • 1. Technology Service LineAgile Metrics
    June, 2010
  • 2. Overview
    1
    7/8/2010
    www.centricconsulting.com
  • 10. Introduction
    7/8/2010
    www.centricconsulting.com
    2
    Alec Finn
    18 Years in Information Technology the last 6 in the Agile space:
    • Sales Representative
    • 11. Program / Project Manager
    • 12. Quality Assurance Manager
    • 13. Agile Coach
    Notable Agile Clients:
  • The Value of Metrics
    7/8/2010
    www.centricconsulting.com
    3
    The board tells a story to those who look at it.
    What about those who don’t?
    • Distributed Teams
    • 18. Senior Managers
    • 19. 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
  • 20. Introduction
    7/8/2010
    www.centricconsulting.com
    4
    Agile for the Enterprise
  • 21. 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
    www.centricconsulting.com
  • 22. 7/8/2010
    www.centricconsulting.com
    6
    Iteration and Release Plan
    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
  • 23. 7/8/2010
    www.centricconsulting.com
    7
    Iteration and Release Plan
    Scheduling a meeting: Original Estimate
  • 24. 7/8/2010
    www.centricconsulting.com
    8
    Iteration and Release Plan
    Scheduling a meeting: Status
    • Remaining – Work that is in scope but not currently being done
    • 25. In Progress – Work that is being worked but is not complete
    • 26. Complete – Work that the team has completed but the business as not confirmed
    • 27. Verified Complete – Work accepted by the Business
  • Iteration and Release Plan
    7/8/2010
    www.centricconsulting.com
    9
  • 28. 7/8/2010
    www.centricconsulting.com
    10
    Iteration and Release Plan
    Scheduling a meeting: Task Type
    • New – Work identified after the release has begun
    • 29. Defect – Error introduced by the development team
    • 30. Clarification – Rework that is required because a requirement was miss understood
  • Iteration and Release Plan
    7/8/2010
    www.centricconsulting.com
    11
  • 31. Velocity
    7/8/2010
    www.centricconsulting.com
    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
  • 32. Velocity
    7/8/2010
    www.centricconsulting.com
    13
    Resource
    Project Weeks
    Ideal Hours
    Total Available Velocity
  • 33. Metrics
    7/8/2010
    www.centricconsulting.com
    14
  • 34. Metrics
    7/8/2010
    www.centricconsulting.com
    15
    Remaining work is comprised of Remaining and In Progress Tasks
  • 35. Metrics
    7/8/2010
    www.centricconsulting.com
    16
    The Value Wheel includes all tasks in a Release regardless of Status
  • 36. Metrics
    7/8/2010
    www.centricconsulting.com
    17
  • 37. Metrics
    7/8/2010
    www.centricconsulting.com
    18
  • 38. Questions
    7/8/2010
    www.centricconsulting.com
    19
    ? ? ?
  • 39. Contact Info
    7/8/2010
    www.centricconsulting.com
    20
    For Questions or to get a sample Agile Workbook please contact Alec Finn @
    Alec.Finn@CentricConsulting.com