Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum Methodology

2,297 views

Published on

Presentation on scrum methodology in March 2009 to train the team at Fifth Third to start using this agile methodology. Details have been blurred to protect confidentiality.

Published in: Technology, Economy & Finance
  • Be the first to comment

Scrum Methodology

  1. 1. Executing Project with SCRUM <ul><ul><li>Iterative / Incremental </li></ul></ul><ul><ul><li>Methodology </li></ul></ul>
  2. 2. Design Coding Coding Integration Testing … … etc Then Now Time Boxing Sprint 1 <ul><li>Database creation </li></ul><ul><li>5 larger stories </li></ul><ul><li>UI Design </li></ul><ul><li>Batch Design </li></ul>Sprint 2 <ul><li>2 larger stories </li></ul><ul><li>3 smaller stories </li></ul>Sprint 3 <ul><li>Bug fixing - Integration </li></ul><ul><li>5 smaller stories </li></ul>Sprint 4 <ul><li>Bug fixing - Integration </li></ul><ul><li>2 smaller stories </li></ul>Sprint Final <ul><li>Bug fixing - Integration </li></ul>
  3. 3. Coding 2 weeks Design Database Creation Sprint #1 Sprint daily meeting Sprint Planning Design Build & Deploy Demo / Integration Testing
  4. 4. Coding 2 weeks Bug fixing Design Design Sprint #2 Sprint daily meeting Sprint Planning Build & Deploy Demo / Integration Testing
  5. 5. Coding 2 weeks Bug fixing Sprint #3 to Sprint #(final – 1) Sprint daily meeting Sprint Planning Build & Deploy Demo / Integration Testing
  6. 6. 2 weeks Bug fixing Sprint #final Sprint daily meeting Sprint Planning Build & Deploy Demo / Integration Testing
  7. 7. Product Backlog
  8. 8. Sprint Planning <ul><li>15 min: Select items from Product Backlogs </li></ul><ul><li>60 min: Team time estimates, break down items as necessary, Product owners clarifies priorities, How-to Demo </li></ul><ul><li>15 min: break </li></ul><ul><li>15 min: Do velocity calculations </li></ul><ul><li>5 min: Select time for daily scrum </li></ul>Scope Estimate Importance
  9. 9. Sprint backlog
  10. 10. Sample Sprint Backlog
  11. 11. Communication <ul><li>Wiki </li></ul><ul><li>http://...../Scrum/SprintInfoPage </li></ul><ul><ul><li>Sprint Goal </li></ul></ul><ul><ul><li>Sprint Backlog </li></ul></ul><ul><ul><li>Schedule </li></ul></ul>
  12. 12. Chicken and Pig
  13. 13. Daily Sprint meeting <ul><li>What was done </li></ul><ul><li>What will be done </li></ul><ul><li>Any issues ? </li></ul>
  14. 14. Sprint Demo <ul><li>“ Oh do we really have to do a demo ? There really isn’t much fun to show!!” </li></ul><ul><li>“ We don’t have time to prepare a &%$* demo!” </li></ul><ul><li>“ I don’t have time to do demos!” </li></ul>
  15. 15. Sprint Demo <ul><li>Demo attracts feedback from stakeholders </li></ul><ul><ul><li>Watch out for nice-to-have feedback vs real bugs </li></ul></ul><ul><li>Time to discuss work </li></ul><ul><li>Force to actually finish stuff </li></ul><ul><li>No more screen mock up … </li></ul><ul><li>Real accomplishments </li></ul>
  16. 16. Integration Testing <ul><li>High impact Integration Testing </li></ul><ul><li>Very short time (half day) </li></ul><ul><li>QA involvement </li></ul><ul><li>No script </li></ul><ul><li>Benefit: easier to create the system test script later </li></ul>
  17. 17. Sprint Retrospectives Good Could have done better Improvements
  18. 18. Trade-off <ul><li>Regularly tested -> higher quality </li></ul><ul><li>Development mixes with bug fixing </li></ul><ul><li>Too many changes will jeopardize time for latter features </li></ul>
  19. 19. Q & A

×