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