P. 1
Scrum Guidelines

Scrum Guidelines

|Views: 65|Likes:
Published by araichura

More info:

Published by: araichura on Mar 20, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

03/20/2011

pdf

text

original

Scrum Guidelines

Service Delivery Handbook

Page 1 of 12

.......2 SPRINT:................1 PRODUCT OWNER ..................................................4 8........................................1 SCRUM PLANNING MEETING:..3 6...............................11 10...............................................6 9...............................................................................................................................................................................................................................................................................................................................................4 THE PRODUCT INCREMENT.....................................................................3 2................................6 SPRINT RETROSPECTIVE......................... AMENDMENT HISTORY.....................................................................................................................10 10...............................................................................3 THE SPRINT BURNDOWN CHART...........7 9......................................................... SCRUM ROLES & REPONSIBILITIES.................................................................................................................................................7 9..........11 10.. CHARACTERISTICS OF A SCRUM METHODOLOGY........ OTHER REFERENCE ............................................................................................................3 TEAM...............3 SCRUM MEETINGS :................................................................................................................... INTRODUCTION..............................CONTENTS 1....................................................................................................3 3.....................................1 THE PRODUCT BACKLOG...............................................................................................2 SCRUM MASTER..................................................10 10....................................9 10................................................................................................................................11 Service Delivery Handbook Page 2 of 12 .............................................................................11 11.................... SCRUM PROCESS FLOW........................3 5.. SCRUM.............................................................................................................................2 THE SPRINT BACKLOG.....................4 7............................................. SCRUM PRACTICES.................................................................................................................................................................................. SCOPE....................5 9......................4 8.......................5 9.............................5 8.................................................................................................................................................................................................................................................................................................................3 4.......................9 9.....5 SPRINT REVIEW MEETING...................5 9.................................................................................................................................. SCRUM ARTEFACTS................................................................................. PURPOSE..................................................4 8.................4 SCRUM OF SCRUMS.......................................

it doesn’t describe what to do in every circumstance. The objective of this document is hence to provide a common guideline for Scrum process of software development projects in 2. Scrum’s simplicity can be deceptive. Scrum is used for complex work in which it is impossible to predict everything that will occur. Scrum simply offers a framework and set of practices that keep everything visible. PURPOSE customers are increasingly demanding the use of Agile techniques while developing software.agilealliance.org ITS-S-G007E Hot Housing Guidelines ITS-S-G007H Agile Guidelines 4. Service Delivery Handbook Page 3 of 12 .1. This allows Scrum’s practitioners to know exactly what’s going on and to make on-the-spot adjusents to keep the project moving towards the desired goals. The process. SCOPE The guidelines enumerate general points to be followed for effective implementation of Scrum methodology 3. INTRODUCTION “Scrum” name is derived from activity that occurs during rugby match i. its artifacts and its rules are few. In IT context it is Project Management Methodology for Agile development 5. to move the ball downfield. On the other hand. Scrum is very simple. sometimes violently.e a group of players forms around the ball and the team-mates work together. straightforward and easy to learn. OTHER REFERENCE • • • • • Agile Project Management with Scrum by Ken Schwaber Agile Project Management by Jim Highsmith published by Pearson Education http://www. its practices. Scrum is not a prescriptive process. Accordingly. SCRUM On one hand.

       It is a project management methodology It is a wrapper for existing engineering practices Scrum works with XP. SCRUM ROLES & REPONSIBILITIES There are three roles in this methodology viz. However this duration can vary from project to project and can range from 1 week onwards The sprint backlog is developed in the sprint and progress is tracked through daily scrum meetings At the end of the sprint. 8. RUP and any other engineering practice you have adopted Scrum believes in empowering the development team Scrum advocates working in small team (7-9) It consists of only three roles Scrum expects to track the progress on daily basis.1 • • • PRODUCT OWNER Product Owner is the person responsible for managing Product Backlog so as to maximize the value of the project. CHARACTERISTICS OF A SCRUM METHODOLOGY 7. The sprint backlog hence contains a list of requirements that can be delivered in that sprint A Sprint is ideally recommended to be of 30 calendar day duration. Product owner. 8. Scrum Master and the team. SCRUM PROCESS FLOW      Requirements are documented in a product backlog which is a prioritised list of requirements. a deliverable called as product increment is shipped out to the customer.6. He/ She represents all stakeholders in the project He/ She owns product log and prioritizes Service Delivery Handbook Page 4 of 12 . Requirements in a product backlog are broken down into multiple sprints or iterations.

then Scrum of Scrums is used. the entire project team members will constitute the Scrum Team. He/She manages ROI through prioritization and release plans Typically in . business analyst) will be the product owner. Has the full authority to do anything to meet the sprint goal Estimates deliveries Commits and deliver user stories Produces quality code In . If the project team is big. Typically.• • He/She directs the project.      SCRUM PRACTICES The Sprint Planning Meeting The Sprint The Daily Scrum The Sprint Review Meeting The Sprint Retrospective 9. a Scrum team has 7-9 members.3 • • • • • TEAM Is a cross functional group of people that is responsible for managing itself to develop software every sprint. Sprint by Sprint. 8. Customer. customer proxy (onsite person. 9. the Project Manager may act as the Scrum Master 8. its correct implementation.4. and the maximization of its benefits. Refer Sec 9. • He/She helps the team turn that backlog into functionality • He/ She is responsible for enacting Scrum values and practices • His/her main job is to remove impediments • He/She fosters team communications • He/She improves engineering practices and tools • He/ She is responsible for improving productivity of development team • He/She organizes and facilitates ‘scrum meetings’ In context .2 • SCRUM MASTER Scrum Master is the person responsible for the Scrum Process.1 SCRUM PLANNING MEETING: Service Delivery Handbook Page 5 of 12 .

In fact the team members themselves decide and sign up for the tasks individually. 9. The Scrum Master doesn’t allocate tasks to the team members. Segment Two: Four hours • The Team decides • on the sprint goal (a short theme for the sprint) • how much it can commit to delivering in the coming Sprint.2 • • • • • SPRINT: • Strictly time boxed to 30 consecutive calendar days: it’s more important to fall short than to slip the date Activities are visible through the Sprint Backlog and Sprint Burndown Charts The Product Owner refrains from tinkering with priorities Within the sprint.Sprint Planning Meeting is a one-day meeting time-boxed to 8 hours that initiates every Sprint.. This is based on “Accepted responsibility” principle of Agile. The Team devises its own tasks and figures out who will do them. • Team may ask questions. It consists of following activities: • Product Owner describes highest priority features to the Team. • The Product Owner answers questions but does not direct the team’s choices. • The outcome is the Sprint goal and the Sprint Backlog The Team decides how to turn the selected requirements into an increment of potentially shippable product functionality. there are many possible engineering practices! Changes • Team adds new tasks whenever they need to in order to meet the sprint goal • Team can move unnecessary tasks • But : sprint backlog can only be updated by the team Service Delivery Handbook Page 6 of 12 . Sprint Planning Meeting comprises of two segments of four hours each: • Segment One: Four hours • The Product Owner selects the ideal backlog for the coming Sprint and communicates its meaning and importance to the team. • Team decides what they can commit to delivering in the Sprint.

• Daily meetings lead to knowledge socialization and promotes self organizing team structure 9. it is referred to as a “scaled project”. For more information on estimates.3 SCRUM MEETINGS: Daily scrum meetings are held by the team to check the status on work being done as per following: • Parameters • Daily • 15-minutes • Stand up • Not for problem solving Three questions are answered by each team member • What did you do yesterday? • What will you do today? • What obstacles are in your way? Scrum master leads the meeting and assesses the responses from each person • • Purpose of Scrum meetings: • Help the team to uncover potential problems as early as possible. If teams are of larger size then. The process of defining and prioritizing the non-functional requirements for scaling is called staging. • • • Large teams are broken down into smaller teams Scrum meeting team happens daily for each team. After this. Following is discussed • What did my team do yesterday to advance the objectives of the Sprint • What will my team do today • What are the barriers that could keep my team from meeting its commient to the Sprint This meeting takes place after daily SCRUMs When more than one Scrum team works simultaneously on a project. 9. Section on Agile estimation.4 SCRUM OF SCRUMS Scrum advocates team size of 7-9 members.• Estimates are updated whenever there is new information. please refer ITS-S-G007H Agile Guidelines. • • • Service Delivery Handbook Page 7 of 12 . Scrum of Scrums is done as per following. and the mechanisms employed to coordinate the work of these teams are called scaling mechanisms. team leads of each team have a Scrum meeting among themselves daily.

Service Delivery Handbook Page 8 of 12 .

any desired changes and the priority of these changes. • Time boxed to one hour of preparation and four hours of meeting. It is time boxed to three hours. 9. • Functionality that isn’t done cannot be presented • At the end of the presentations.5 SPRINT REVIEW MEETING The purpose of the Sprint review is for the Team to present to Product Owner and stakeholders functionality that is done as per following: • Team presents what is accomplished during the sprint • Team demonstrates product increment to product owner’s satisfaction.6 • • • • SPRINT RETROSPECTIVE A retrospective is a ritual gathering of a community at the end of a project to review the events and learn from the experience It can be done at end of sprint/iteration/ release or any specific event/situation requiring a re-look. the Scrum Master announces the place and date of the next Sprint review to the Product Owner and all stakeholders. to get their impressions. one by one. • Informality is encouraged. • At the end of the Sprint review.9. Following are the activities: Service Delivery Handbook Page 9 of 12 . the stakeholders are polled.

reliability. It is a prioritized list of project requirements or features that provide business value for the customer Usually a combination of  Story based work  Task based work List is prioritized by the Product owner Items can be added to the backlog at any time (this is how changes are introduced) This activity is not intended to analyze the system.for the product to deliver the necessary value. The focus is on what we can learn from what happened Retrospectives are NOT a witch hunt Retrospectives are NOT about gathering specific information • They are a free-flowing brainstorm on opportunities and ways to resolve them Sprint retrospective details can be logged in Retrospective worksheet of ITS-E-T061E Iteration Metrics Template. such as performance. ITS-E-T036A User Story template and ITS-E-T061B Use case template are used for effective estimation. Product backlog is maintained as per ITS-E-T026C Product backlog template. Refer ITS-E-G036A User Story Guidelines.  Non-functional requirements . 10. security. and (optionally) Product Owner review the last Sprint Teams get together to discuss the following  What did we do well  What did we learn  What should we do differently the next time  What still puzzles us Actionable items are presented to the Product Owner for prioritization as nonfunctional requirements.1       THE PRODUCT BACKLOG Product backlog is a list of all desired work on the project.what capabilities and environments must be in place for the product to be developed and delivered In . merely to scope and list its requirements and not to how it would be done The product backlog consists of three types of items:  Product functionality .• • • • Team. and cost requirements  Environmental requirements . prioritizing requirements. what operational aspects must it demonstrate. What a Retrospective is NOT • • • Retrospectives are NOT about blame • Problems (opportunities) arise. Sprint retrospective template is used to capture information of the same. Scrum Master. SCRUM ARTEFACTS 10.what functions could the system perform to deliver the value anticipated in the product vision.   Service Delivery Handbook Page 10 of 12 .

documents or hand waving. prioritizing requirements. Delivers measurable value Product Increment should be “Potentially Shippable”. The process can be halted after every Sprint and there will be some value. some ROI It must be a product.3    THE SPRINT BACKLOG The Sprint Backlog is the list of tasks that the Scrum Team is committing that they will complete in the current Sprint.MK(QMG) Ananthan (CH. Sprint backlog is maintained as per ITS-E-T026D Sprint backlog template. THE SPRINT BURNDOWN CHART The estimated work remaining in the Sprint is calculated daily and graphed resulting in a Sprint Burndown chart The burn-down chart is emotionally powerful because there is a special feeling about hitting the number zero that helps people get excited about completing their work and pressing forward In . no matter how incomplete 10. Sprint Burndown chart is maintained as per ITS-E-T026D Sprint Burndown chart template THE PRODUCT INCREMENT At the end of every Sprint the team should have delivered a production quality increment of the system. QMG) Nature of Changes First Issue Service Delivery Handbook Page 11 of 12 . but progress must be reported in the backlog Managers don’t make decisions for the team Time estimates must be updated daily In . micro-iterations). The Product Increment is what is demonstrated to the users and stakeholders working software rather than mock-ups. AMENDMENT HISTORY Ver I1. Scrum team takes the sprint goal and decides what tasks are necessary Selected by team at outset of Sprint Scrum master maintains the sprint Backlog by updating it to reflect which tasks are completed and how long the team thinks it will take to complete those that are not yet done Changes during Sprint as information is discovered Okay to use other engineering practices (stories.2           10.0 Date 21 Jul 2006 Author(s)/ Approved by Function GA.4     11. ITS-E-T036A User Story template and ITS-E-T061B Use case template are used for effective estimation.10.

Service Delivery Handbook Page 12 of 12 .

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->