20060919-59_Minute_Scrum.pptVIP

59-Minute Scrum Pam Rostal prostal@ Topics Scrum Relevance 59-Minute Scrum Agenda Scrum Overview Scrum Work Products Scrum References Scrum Relevance Would you be interested in: An installment plan that delivers your highest priority software on a monthly basis? Visibility into what’s really going on at any time? Manageability of short time-boxes that produce production-quality code every time? Rapid feedback cycles that prevent bottlenecks? Adaptability that captures the best of what’s been delivered as input into the requirements for your next iteration? Well-informed decisions made by a responsible, accountable Product Owner, Scrum Master, and Team (including the customer)? 59- Minute Scrum Agenda Timetable: Introduce Scrum Concepts 30 minutes 59-Minute Exercise: Complete Sprint Planning Meeting 10 minutes Conduct a Sprint “Day 1” 10 minutes Conduct a Daily Scrum Meeting 05 minutes Conduct a Sprint “Day 2” 10 minutes Conduct a Sprint Review/Demo 06 minutes per team (x4) Debrief the exercise 15 minutes Questions 15 minutes This exercise is based on a simulation developed by Jean Tabaka and Hubert Smits and a presentation delivered by Rachel Davies. Scrum Practices Product Backlog Sprint Planning Meeting Roles Scrum Team Product Owner Scrum Master Sprint Sprint Backlog Daily Scrum Meeting Sprint Review Meeting Scrum Flow Sprint Planning Meeting 2-part meeting to define the next sprint Product Owner Scrum Team Selects and develops the highest priority items on the Product Backlog Self-organizing Cross-functional with undifferentiated roles Seven plus or minus two Responsible for committing to work Authority to do whatever is needed to meet commitment Scrum Master Sprint A fixed period of 30 days to develop a deliverable product The Sprint includes design, coding, testing, and documentation Once a Sprint has started only the Scrum Team can add or remove items in Sprint backlog Abnormal termination of Sprint is called for when