1. SCRUM METHODOLOGY By Kimberly Stoler IS 553

2. Historical Background  Creator’s  Ken Schwaber  Jeff Sutherland  Named after the game of Rugby  Why was it created?

3. Dr. Jeff Sutherland’s Use  Easel Corporation-1993  First object-oriented D&A tool  VMARK in 1995  Used SCRUM with Internet  Individual in 1996  Reduced senior mgmt time  Used during Internet Boom  IDX in 1996  Large teams -> Concern of quality  SCRUM increased production rate of deliverables

4. Principles  Team empowerment  Adaptability  Defining Process  Empirical Process

5. Components & Phases  Phases  Planning Phase  Architecture/high level design Phase  Development Phase  Closure Phase  Components  Backlog  Sprint

6. Backlog  Necessary for Sprint to begin  Consists of features and/or requirements  Functionality  Technical architecture  Known Bugs  Sprint can begin, once created

7. Planning & Architecture/High Level Design Phases  Planning  Backlog  Delivery Date  Select release  Define Project team(s)  Asses risk & risk controls  Review & adjust backlog  Validate development tools  Estimate costs  Mgmt approval  Design Phase  Design review meetings  Identify problems/issues in Development  Refine architecture  Perform Domain analysis  Identify changes for backlog  Review assigned backlog

8. Sprint (Development Phase)  Sprint teams 5 to 9 team members  Last 30 days  Different stages of lifecycle done in Sprint or multiple sprints  Backlog turned into tasks – 4 to 16 hours  Teams develop, wrap, review & adjust  SCRUM meetings  Everyday  Accomplishments  Issues  Next Assignment

9. Sprint cont’d  Demo  End of each Sprint  Beneficial  Customers  Developers  QA  Progress  New Backlog

10. The SCRUM Process

11. Closure Phase “When management feels the variables of time, competition, requirements, cost and quality concur for a new release to occur, they declare the release “closed” and enter this phase.” –Ken Schwaber SCRUM Development Process  General Release  Integration  Test  Documentation  Training  Marketing

12. Advantages  Continuous Improvement  Chaos Leverage  Customers-Progress  Flexibility  Productivity

13. Guidelines  When to use  Customer involvement  Requirements/Delive rables Change  All types of projects  Avoid SCRUM  Structured Requirements  Impossible to meet deadlines  Micromanagement

14. Success Factors  Built-in instability  Self-organizing teams  Overlapping Development  Subtle control

15. Challenges  Control of development process  Detailed order of processes  Environmental requirements

16. Gurus and Products  Ken Schwaber  Jeff Sutherland  VisionOne  Release 1.2  SCRUM framework

17. The End