This document serves as an introduction to Scrum, outlining its framework, practices, and roles. It emphasizes the importance of backlogs, both product and sprint, in managing tasks and setting project goals, and describes the self-organizing nature of Scrum teams. Key practices include daily scrum meetings, sprint planning, and sprint reviews, highlighting the need for management support and adaptability throughout the Scrum lifecycle.

1. Scrum An Introduction Srinivas Chillara

2. Agenda Introduction to Scrum Overview of Scrum Practices in Scrum The Roles in Scrum

3. It is Scrum not SCRUM! Scrum is a simple framework, powerful and rooted in common sense. What Scrum provides is focus

4. Source: From OOPSLA95

5. How Scrum looks Regular inspections and adaptations Projects make progress in a series of sprints Software is developed during these sprints Scrum has a project management emphasis

6. SCRUM Lifecycle brief … 30 days 24 hours Product Backlog As prioritized by Product Owner Sprint Backlog Backlog tasks expanded by team Potentially Shippable Product Increment Daily Scrum Meeting

7. Scrum Characteristic NO CHANGE DURING SPRINT Self organising teams No prescribed development processes Uses peer pressure and commitment

8. Scrum Practices Product Backlog Sprint Sprint Planning Meeting Sprint Backlog Daily Scrum Meeting Sprint Review Meeting

9. Backlogs? Backlogs Product backlog Release Backlog Sprint Backlog

10. Product Backlog Prioritized list of work to be performed on a product Anyone can contribute backlog items Product Owner responsible for prioritisation Indicates the anticipated grouping of work by sprints/releases

11. SPRINT BACKLOG Work remaining (Hrs) 8 8 8 15 In-Progress Srinivas Suhas Analyse CRM meta-data 7 7 15 30 In-Progress Shailesh Prepare performance testing infrastructure. 20 20 20 20 Not started Shailesh Srinivas Switch JDK to 1.4 0 0 0 10 Complete Suhas Shailesh Meet to review Data Design 4 3 2 1 STATUS Responsible Originator Task Description

12. Sprint backlog during the sprint Estimates are updated as and when there is new information. Changes Team adds new tasks whenever they need to, in order to meet the sprint goal Team can remove unnecessary tasks But: Sprint backlog can only be updated by the team

13. Sprint Planning Meeting to set the next Sprint goal Product Backlog Team Capabilities Business Conditions Technology Stability Executable Product Increment Review Consider Organize Next Sprint Goal Sprint Backlog

14. Burndown chart

15. SCRUM Lifecycle 30 days 24 hours Product Backlog As prioritized by Product Owner Sprint Backlog Backlog tasks expanded by team Potentially Shippable Product Increment Daily Scrum Meeting

16. Scrum The practices are mandatory You are either doing Scrum or not (a preposition) Management support essential Team needs protection

17. Scrum Discussion/ Questions !?!