1. The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours 1 - 4 weeks

2. Discussion today Presents an alternative way of developing products Provides insight into Scrum values Demonstrates Scrum as a simple framework

3. Scrum Overview

4. What is Scrum? The most unique aspect of rugby is the scrum, pictured below, which is used to restart play following minor infractions during the match. Scrum -- a group responsible for picking up the ball and moving it forward.

5. 3 pillars of Scrum

6. Scrum Values 6 CommitmentOpenness Courage Focus Respect

7. The Traditional Way orem ipsum dolor sit amet, co nse ctetur Milestones and Tasks 7

8. The Traditional Way 8

9. The SCRUM Way orem ipsum dolor sit amet, co nse ctetur Product Backlog 9

10. Involved vs. Committed 10

11. Involved vs. Committed 11

12. The Scrum Way orem ipsum dolor sit amet, co nse ctetur Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint N Sprint is 1 – 4 Weeks 12

13. Traditional SDLC vs Scrum

14. Source: www.VersionOne.com

15. Scrum Overview Self Organize and Deliver as a Team 24 hours 1 - 4 weeks Product Backlog Sprint Backlog Incremental Solution Delivery Daily Standup Meeting Team Retrospective

16. The Scrum Framework Events Sprint Planning What are we doing next? Daily Scrum How are we doing today? Sprint Review How did we do? Sprint Retrospective How do we get better? Artifacts Product Backlog What are we doing and in what order? Sprint Backlog What are we doing right now? How will we do it? Burndown Chart How are we doing in this sprint? How we are doing in this release? Roles Product Owner What should we work on and Why? (Vision) Development Team Who will do it and how? ScrumMaster Who will help us do it (Process Facilitator)?

17. The Core Scrum Team Product Owner Development Team Scrum Master Small enough to remain nimble and Large enough to complete significant work within a Sprint Self-organizing and cross-functional Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback

18. Product Owner Define the feature of the product Makes scope vs. schedule decisions Responsible for achieving financial goals of the project Prioritize and ranks the product backlog Adjust features and priority every sprint, as needed Accept or reject work results

19. Development Team Typically 5-9 people Cross-functional QA, Programmers, UI Designers, etc. Members should be full-time May be exceptions (e.g., System Admin, etc.) Teams are self-organizing Membership can change only between sprints

20. The Scrum Master Responsible for enacting Scrum values and practices Main job is to remove impediments

21. Product Backlog A list of all desired work for the project Ideally expressed such that each item has value to the users or customers of the product Prioritized by the product owner Team estimates items in Backlog relative to each other using predetermined scale (story points) Product Owner, with the help of the team, will continuously ‘groom’ or ‘review’ the backlog.

22. Sprints Scrum projects make progress in a series of “sprints” Target duration is 1-4 weeks A constant duration leads to a better rhythm Product is designed, coded, and tested during the sprint 3 5 8 3 2 8 2 13 3 1 Product Backlog

23. Sprint Planning InputTeam WorkOutput

24. Burndown charts Primary method of tracking progress A Burndown chart shows how much work is left as of various dates Two types Release burndown Sprint burndown

26. Release burndown

27. Daily Scrum meetings Parameters Daily 15-minutes Stand-up Not for problem solving

28. Daily Scrum Daily, 15 minutes, Commitments in front of peers Everyone Answers 3 Questions What did you do yesterday? 1 1 What will you do today? 2 2 Is anything in your way? 3 3

29. Sprint Review Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Participants Customers Management Product Owner Other engineers

30. Team Retrospective Key mechanism for examining and improving methods and teamwork at the close of every sprint and demo Team Answers 3 Questions What did we do well? 1 1 What didn’t go well? 2 2 What could be improved in the next sprint? What could be improved in the next sprint? 3 3

31. Inspect and Adapt

32. Thank You Somnath Ghosh somghosh@yahoo.com www.CorporateITSolutionsInc.com 720 217 8513 (mobile)

33. 24 hours 1 - 4 weeks