Agile Overview


Published on

Overview of the Agile process

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

Agile Overview

  1. 1. Andy Scarr 10/25/11 Andy Scarr
  2. 2. High Level Process <ul><li>Sprint Zero </li></ul>Sprint 1 Sprint 2 Sprint 3 Sprint 4 <ul><li>Project Planning </li></ul><ul><li>Product Backlog </li></ul><ul><li>Test Planning </li></ul><ul><li>Environment Requirements Planning </li></ul><ul><li>Sprint Planning </li></ul><ul><li>Story Execution </li></ul><ul><li>Stand-ups/SCRUMS </li></ul><ul><li>Progress Monitoring/Burn down </li></ul><ul><li>Regression Testing </li></ul><ul><li>Customer Demo </li></ul><ul><li>Post Sprint Review </li></ul><ul><li>Go LIVE </li></ul>10/25/11 Andy Scarr
  3. 3. Product Backlog <ul><li>‘ An agile project Lives and Dies by how good the product backlog is and how well it is managed’ </li></ul><ul><li>‘ Everyone on the project should know what is on the backlog, actively update and enhance it, adding stories where required’ </li></ul><ul><li>‘ It is a LIVE document used for the project metrics, burn downs and progress reporting </li></ul>10/25/11 Andy Scarr
  4. 4. Creating a Product Backlog – Sprint Zero Inputs <ul><li>Business Requirements Document (BRS) </li></ul><ul><ul><li>Stories </li></ul></ul><ul><ul><li>Use Cases </li></ul></ul><ul><li>Testing Requirements </li></ul><ul><li>Environment Requirements </li></ul><ul><li>Development Requirements </li></ul><ul><li>Project Requirements </li></ul><ul><li>Support Requirements </li></ul><ul><li>Transition To LIVE / Support Requirements </li></ul>The most Important rule here is to break stories down as much as possible, you want to get to the component level, even if that means having 000’s of product Items. 10/25/11 Andy Scarr
  5. 5. Scoring a Product Backlog – Sprint Zero Fibonacci Numbers 1, 2, 3, 5, 8, 13, 21, 34, etc Estimate (Hrs) Each Story <ul><li>Complexity </li></ul><ul><li>Business Priority </li></ul><ul><li>Effort </li></ul>Reviewed as a group by all members of the team – inc the business rep, testers, Development, Env Mgt, Design, PM’s - anyone in the Team 10/25/11 Andy Scarr
  6. 6. Creating a Product Backlog – Sprint Zero Inputs <ul><li>Resource availability </li></ul><ul><li>Resource Designation </li></ul><ul><li>Calendar of Sprints </li></ul><ul><li>Creating a Capacity Plan </li></ul>10/25/11 Andy Scarr
  7. 7. Sprint 1 Sprint Planning Meeting Which Stories do we take in first ? Base on Scores Base on Need Base on Dependencies Sprint 1 is always difficult and usually delivers little in the way of code, but it is a useful activity to prepare the way for further sprints, get the processes embedded and build the team. Base on Capacity 10/25/11 Andy Scarr
  8. 8. Sprint 1 Board and Stand-ups <ul><li>Monitor Progress: (Start of Day Meeting) </li></ul><ul><li>Stories for Sprint Documented </li></ul><ul><li>Assigned </li></ul><ul><li>Effort estimated </li></ul><ul><li>Actual effort expended </li></ul><ul><li>Estimated time to Complete </li></ul><ul><li>Blockers </li></ul><ul><li>Update the Project Burn-down </li></ul>ETC Days Planned Burn-down Actual Burn-down De-scoping stories Off Track Weekend Working On Track Under Utilisation? 10/25/11 Andy Scarr
  9. 9. Sprint 1 Customer/Sponsor Demo <ul><li>What Stories have we completed ? </li></ul><ul><li>What Stories have we not completed or de-scoped ? </li></ul><ul><li>Demo the delivery </li></ul><ul><li>Go LIVE Discussion </li></ul>Post Sprint Review <ul><li>What Went Well ? </li></ul><ul><li>What Did Not ? </li></ul><ul><li>Learning points for Next Sprint </li></ul>10/25/11 Andy Scarr
  10. 10. Restart the Cycle Sprint Planning Monitor Manage Communicate Execute Stories Demo Post Sprint Review 10/25/11 Andy Scarr
  11. 11. Q&A’s 10/25/11 Andy Scarr