SCRUM

SCRUM

1. Agile Methodology

2. Sprint Cycle

   • Product Backlog
     • Prioritised list of features required by the customer
     • Features are known as user stories
     • Wishlist
   • Sprint Backlog
     • Features to be done this sprint
     • Features are expanded into smaller tasks
   • Sprints are normally about one month long
   • Daily Scrum: 15 minute meeting held every day. SCRUM Master asks:
     • What have you accomplished since the last meeting?
     • Are there any obstacles in the way of meeting your goal?
     • What will you accomplish before the next meeting?
   • New functionality is demonstrated at the end of each sprint
   • Sprint Retrospective Meeting
     • Takes place at the end of each sprint
     • Team reflects on what went right and areas of improvement

3. Team

   • Product Owner
     • Makes sure the right features make it into the product backlog
     • Helps set the direction of the product
   • Scrum Master/Project Manager
     • Makes sure the project is progressing smoothly
     • Makes sure everyone has the tools they need to allow them to get the job done
     • Sets up meetings, monitors the work being done, and plans releases
     • Developers
     • Testers

4. Release Planning

   • Team decides which user stories are going to be put into release
   • Release Backlog
     • User stories included in a particular release
     • Team prioritises user stories and estimates how long each will take
     • Sprints used to get work done
       • 1 - 30 days
       • 2 - 12 sprints per release
       • Product in ship-ready state at the end of each sprint

5. Estimates

   • Hours, days, months

6. Burndown Chart

   • Day be day measure of remaining work in a given sprint or release
   • Burndown Velocity/Rate of Productivity
     • Work remaining decreases with every day
   • Estimated completion date can be calculated based on velocity
     • Work Remaining / Rate = Days to Completion