1. SCRUM Software Development Process

2. Background “Scrum” A rugby term “describes a play in rugby in which the two sets of forwards mass together around the ball and, with their heads down, struggle to gain possession of the ball.” First Mentioned by Takeuchi and Nakata in 1986 as a holistic approach to a new product development

3. Background Jeff Sutherland and Ken Schwaber started in 1996 Also with the influences Complexity Theory, software development practices from Borland and Microsoft and Process Control Theory.

4. What is Scrum? Scrum is an agile process to manage and control development work. Scrum is a wrapper for existing engineering practices. Scrum is a team-based approach to iteratively, incrementally develop systems and products when requirements are rapidly changing Scrum is a process that controls the chaos of conflicting interests and needs. Scrum is a way to improve communications and maximize co-operation. Scrum is a way to detect and cause the removal of anything that gets in the way of developing and delivering products. Scrum is a way to maximize productivity. Scrum is scalable from single projects to entire organizations. Scrum has controlled and organized development and implementation for multiple interrelated products and projects with over a thousand developers and implementers.

5. Scrum Phases Planning (Defined) Sprint (Empirical) Closure (Defined)

6. Planning Set basic requirements  Time schedule  Cost and risk  Backlog (Functional requirement)  Prioritize backlog (Done by one person) Based on most important functions to less important functions.

7. Sprint Phase Empirical process  Develop, test, and document No external interference  Black box  Provide info to during the meeting New work and risk can be uncovered

8. Sprint process

10. Sprint Team Less than 6 people  Includes Developer, QA and Documentation member  Too many people then make other sprints Focus only on their work during the sprint

11. Scrum Meeting Appoint Scrum master  Must be able to make immediate decisions  Must be able to immediately resolve work issues 15 minutes meeting Scrum master ask 3 questions  What did you do since last Scrum?  What issues have been found?  What will the team complete today?

12. Sprint Cycle

13. Closure Phase Sprint backlogs are created and satisfied Regression testing Develop training materials Complete final documentation

14. Scrum productivity

15. When to use Scrum Any size of project Recommended on object oriented software  Use project domain approach

16. Gurus Jeff Sutherland  Initial Scrums at Easel Corp in 1993  IDX and nearly 600 people doing Scrum Ken Schwaber  ADM (Advanced Development Methods)  Initial definitions of Scrum at OOPSLA 96 with Sutherland Mike Beedle  Scrum patterns in PLOPD4