This document provides an introduction to the Scrum framework, outlining its lifecycle, roles, and rules for effective implementation. Key roles include the Product Owner, who prioritizes the product backlog, and the Scrum Master, responsible for facilitating the process and removing impediments. It details the structure of sprint planning, daily scrums, and sprint reviews, emphasizing time-boxing and specific responsibilities to ensure team efficiency and communication.

1. Scrum An Introduction Srinivas Chillara

2. 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

3. Roles TEAM Typically six to ten Cross functional Responsible for implementing the sprint backlog Full-time Self organizing Membership can change only between sprints

4. Roles PRODUCT OWNER A very important Stakeholder Determines product backlog May represent a larger group Responsible for prioritizing BI Ensures business relevance Must be available to the team

5. Roles SCRUM MASTER Represents management to the project. Typically filled by a PL or PM. Responsible for Scrum values and practices. Removes impediments. Facilitates understanding between team and PO. Helps provide visibility into progress of Team.

6. Rules SPRINT PLANNING MEETING Time-boxed to 8 hrs (std) Attended by all roles The PO must prepare the PB prior to meeting The team can make suggestions Decision of product backlog lies with PO The team decides how much work to take up

7. Rules SPRINT PLANNING MEETING First part : discuss the relevant part of PB Second part: team discusses how to implement The PO must be available to the team PO may have to gather more information Team has complete freedom on approach to PB A sprint vision and a sprint backlog result

8. Rules DAILY SCRUM Same place same time every working day Stand in a circle All team members are required to attend. Team members must be prompt! Anyone who is late pays Rs 100 to the Scrum Master on the Spot. If Scrum Master is late, she pays each team member Rs 100.

9. Rules DAILY SCRUM Each team members, in turn, should respond to three questions only What have you done since the last Scrum? ( w.r.t this project) What will you do between now and the next scrum? What obstacles are in the way of your work? no digression beyond answers

10. Rules DAILY SCRUM One person talks at a time Chickens are not allowed to talk, make observations or faces Chickens are on the periphery on the team The Scrum Master can limit the chickens

11. Rules DAILY SCRUM Chickens are not allowed to talk to the team members after the meeting for clarification or instruction Pigs or chicken who cannot or will not conform to the above rules can be excluded from the meeting (chickens) or removed from the team (pigs). When a team member reports something of interest to another or needs the assistance of another, any team member can immediately arrange for a separate (offline) meeting to discuss this further

12. Rules SPRINT The team can seek outside help, support, information during the sprint No one else can provide directions, instruction etc. SM or PO in consultation can terminate sprint Team can consult PO, when unable to meet commitment.

13. Rules SPRINT If the team feels able to add to sprint backlog it can again consult PO The team must attend the Scrum The team must keep the sprint backlog updated.

14. Rules SPRINT REVIEW The sprint review meeting is time-boxed to 4 hrs. Team should not spend more than 4 hrs preparing for it. The purpose of this meeting is for the team to present to the product owner and stakeholders functionality that is “done”. Functionality that isn’t “done” cannot be presented.

15. Rules SPRINT REVIEW Functionality presented on which ever server is closest to production Starts with a presentation of the sprint goal Followed by the product backlog committed to and completed The team members can take turns presenting At end of the presentation the stakeholders are polled, in turn, to get their impressions

16. Rules SPRINT REVIEW The PO discusses with the stakeholders and the team, potential re-arrangements of product backlog based on feedback The stakeholders are free to voice any comments, observations, opinions regarding the increment. Stakeholders can identify any new functionality that occurs to them as they view the presentation. At the end the Scrum Master announces the date of the next sprint review to all

17. On to Role Play LEAVE MANAGEMENT SYSTEM We are the Product Owners Two Scrum Masters The timings (we’ll do one cycle + second sprint plan) Pre-sprint preparation 4 min SPRINT PLANNING MEETING: 8 min Each Day: 10 min (4 Days, Scrums) Sprint Review meeting: 8 min