You are on page 1of 9

SCRUM - QUICK GUIDE FOR SCRUM IMPLEMENTATION FOR THE FIRST TIME

INTRODUCTION This is a quick guide where I tried to comment all the main aspects of Scrum Guide (2011 version) in a sequenced way and adding some another minor aspects not shown in the Scrum Guide but commonly present in our projects. Notation: The texts between [brackets] are the additional comments not included in the official version of scrum guide, which you can find at http://www.scrum.org/scrumguides/. You can find some texts in bold that are highlighted once they are important events, artifacts or roles within Scrum. I hope this guide can be useful as a quick reference guide your jobs or when studying. Any comments, corrections, suggestions, advices please feel free to contact me at scrum@glemiston.com. Cheers, Glemiston Figueiredo Professional Scrum Master I

USING SCRUM FOR A NEW PROJECT IMPLEMENTATION 1.0 [Define the Product scope] 2.0 [Define stakeholders and committee] 3.0 SCRUM ROLE: SCRUM MASTER 3.1 Choose 1 person to be the Scrum Master 3.2 Train this person on SCRUM 3.2.1 Main points: 3.2.1.1 Ensure Scrum Application 3.2.1.2 Servant-Leader for: 3.2.1.2.1 The Scrum Team (Product Owner and Development Team, as detailed later) 3.2.1.2.2 The Entire Organization

3.2.1.2.2.1 Leading and coaching the organization in its Scrum adoption; 3.2.1.2.2.2 Planning Scrum implementations within the organization; 3.2.1.2.2.3 Helping employees and stakeholders understand and enact Scrum and empirical product development; 3.2.1.2.2.4 Causing change that increases the productivity of the Scrum Team; and, 3.2.1.2.2.5 Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization 3.3 He or She can be or not a member of Development Team 4.0 SCRUM ROLE: PRODUCT OWNER 4.1 Choose 1 person to be the Product Owner 4.2 Train the Product Owner on SCRUM 4.3 Receives support from Scrum Master on: 4.3.1 Understanding long-term product planning in an empirical environment; 4.3.2 Understanding and practicing agility; and, 4.3.3 Facilitating Scrum events as requested or needed 4.3.4 Specific tasks detailed below 4.4 Concept 4.4.1 Maximizes the value of the Product and work done by the Development Team 4.5 He or She can be or not a member of Development Team 5.0 SCRUM ARTIFACT: PRODUCT BACKLOG 5.1 Product Owner analyzes the Product scope and delivers the first version of Product Backlog (named here as Initial Version) 5.2 One single product backlog for each product 5.2.1 ADDITIONAL SCRUM ARTIFACT: PRODUCT BACKLOG ITEMS 5.2.1.1 List with the description of all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases 5.2.1.2 Order the Product Backlog Items 5.2.1.2.1 Often ordered by value, risk, priority, and necessity 5.2.1.2.2 Top-ordered Product Backlog items drive immediate development activities 5.2.1.3 Product Backlog Items and ordering must toward the ROI (Return of Investment) and TCO (Total Cost of Ownership) Product Backlog duration: while the Product exists

5.2.2

6.0 SCRUM ROLE: DEVELOPMENT TEAM

6.1 Define the people to join the Development Team 6.1.1 Development Team composition should not change within each Sprint 6.1.2 Quality goals remain constant within each Sprint 6.2 Train the Development Team members on SCRUM 6.2.1 Main Points: 6.2.1.1 Self-managed and organized 6.2.1.2 Cross-functional 6.2.1.3 Can manage individual specialized skills 6.2.1.4 although the accountability in shared and not individual for each Developer 6.2.1.5 No sub-teams inside it 6.2.1.6 Size between 3 and 9 members 6.2.1.6.1 Product Owner and/or Scrum Master just are counted in this amount if they are also working as Developers 6.3 Receives support from Scrum Master on: 6.3.1 Coaching the Development Team in self-organization and cross-functionality; 6.3.2 Teaching and leading the Development Team to create high-value products; 6.3.3 Removing impediments to the Development Teams progress; 6.3.4 Facilitating Scrum events as requested or needed; and, 6.3.5 Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood. 6.4 7.0 SCRUM ROLE: SCRUM TEAM 7.1 Once the three people were assigned to the three Scrum roles (Scrum Master, Product Owner and Development Team), the Scrum Team was defined. 8.0 SCRUM ARTIFACT: THE SPRINT 8.1 1 month or less 8.1.1 8.2 ADDITIONAL EVENT: PRODUCT BACKLOG GROOMING 8.2.1 Occurs when Scrum Team decides to do it 8.2.2 Consumes no more than 10% of Development Team capacity 8.2.3 Participation of: 8.2.3.1 Development Team and Product Owner 8.2.3.2 Just Development Team 8.2.3.3 Scrum Master doesnt participate but he/she can aid Product Owner: 8.2.3.3.1 Delivering tools and techniques for Product Backlog management 8.2.3.3.2 Teaching the Development Team to create clear and concise Product Backlog items 8.2.3.3.3 Clearly communicating vision, goals, and Product Backlog items to the Development Team;

8.2.4

Input: 8.2.4.1 8.2.4.2 8.2.4.3 8.2.4.4

8.2.5

1st Version of Product Backlog (Initial Product Backlog Version) Revision of Product Backlog Items Detailing and grouping of Product Backlog Items Grouping Product Backlog Items 8.2.4.4.1 Especially when working with multiple Scrum Teams on the same Product 8.2.4.4.2 [Suggestion]: Group and Subgroup Product Backlog Items according to complete portions of processes, functionalities, tools or whatever will be developed, so, the Development Team can later easily choose subgroup items that can fit inside the sprint and delivers potentially usable product portions 8.2.4.5 Review ordering of Product Backlog Items 8.2.4.6 Estimation of Product Backlog Items 8.2.4.6.1 More precise estimates are made based on the greater clarity and increased detail Output: 8.2.5.1 2nd Version of Product Backlog (named here as Working Version) 8.2.5.1.1 Higher ordered Product Backlog items are clearer and more detailed 8.2.5.1.2 More detailed Product Backlog Items has more precise estimates 8.2.5.1.3 Product Backlog items selected to the upcoming Sprint are decomposed and fine-grained

8.3 SCRUM EVENT: SPRINT PLANNING MEETING: 8.3.1 All Scrum team participation (Development Team, Scrum Master, Product Owner) 8.3.2 Total of 8 hours (1 month Sprint) or proportionally less 8.3.3 SPRINT PLANNING MEETING - PART 1: Define what will be done 8.3.3.1 4 hours (1 month Sprint) 8.3.3.2 Inputs: 8.3.3.2.1 Product Backlog 8.3.3.2.2 Last Product Increment 8.3.3.2.3 Projected Capacity of Development Team 8.3.3.2.4 Past Performance of Development Team 8.3.3.3 Outputs:

8.3.3.3.1

8.3.3.3.2

Product Backlog Items selected to compose the Sprint Backlog 8.3.3.3.1.1.1 Selected from the Product Backlog 8.3.3.3.1.1.2 Defined by Development Team 8.3.3.3.1.1.3 The selected Items must to be a set of shippable and deliverable portions of Product according to the DEFINITION OF DONE 8.3.3.3.1.1.3.1 [Suggestion]: Try to deliver Product Backlog Item groups or subgroups that fit inside the Sprint and consist to complete portions of processes or functionalities Sprint Goal 8.3.3.3.2.1.1 Defined by all Scrum Team (Product Owner, Development Team and Scrum Master)

8.3.4

SPRINT PLANNING MEETING - PART 2: Define how to get the work done 8.3.4.1 Participation of invited people (besides of Scrum Team) to provide technical or domain advice 8.3.4.2 Inputs: 8.3.4.2.1 Select Items to compose the Sprint Backlog 8.3.4.2.2 Define a Plan about how to convert the selected Product Backlog Items into a Product Increment 8.3.4.2.2.1.1 Made by Development Team 8.3.4.2.2.1.2 Forecast the work that can be done 8.3.4.2.2.1.3 Work may be of varying size, or estimated effort 8.3.4.2.2.1.4 Work planned for the first days of the Sprint is decomposed to units of one day or less 8.3.4.2.3 Product Owner clarifications and negotiation 8.3.4.3 Outputs: 8.3.4.3.1 SCRUM ARTIFACT: SPRINT BACKLOG 8.3.4.3.1.1.1 Consists to Selected Product Backlog Items + Plan to deliver them

8.4 ADDITIONAL EVENT: DAILY DEVELOPMENT WORK 8.4.1 Daily 8.4.2 Attend Product Backlog Items toward the agreed definition of done

8.4.3

8.4.4

Check Sprint Goal against the increment implementation 8.4.3.1 If there is a sprint deviation, Development Team renegotiates the Sprint Backlog with the Product Owner Output: 8.4.4.1 SCRUM ARTIFACT: INCREMENT 8.4.4.1.1 Is the sum of all Product Backlog Items delivered since the first Sprint to the current or last one 8.4.4.1.2 The increment must to be DONE 8.4.4.1.2.1 It means that it must to be usable, regardless of the total completion of Product 8.4.4.1.2.2 The DEFINITION OF DONE MUST TO BE clear and agreed between everyone in the Scrum Team 8.4.4.1.2.2.1 The Increment delivered must to be a set of shippable and deliverable portions of Product according to the DEFINITION OF DONE

8.5 ADDITIONAL EVENT: MONITORING SPRINT PROGRESS 8.5.1 Made by the Development Team 8.5.2 At least once for every Daily Scrum 8.5.3 Only work remaining and date are important as parameters in Scrum 8.5.4 Input: 8.5.4.1 Tracking of total work remaining 8.5.5 Output: 8.5.5.1 Projection and reading of likelihood of achieving the Sprint Goal 8.5.6 [Suggestion]: 8.5.6.1 Check that the Increment that are being prepared its becoming a set of shippable and deliverable portions of Product according to the DEFINITION OF DONE 8.6 SCRUM EVENT: DAILY SCRUM 8.6.1 Functioning: 8.6.1.1 15 minutes meeting 8.6.1.2 Taken at the same time and place, daily 8.6.1.3 Granted by Scrum Master 8.6.1.4 Participation of: 8.6.1.4.1 Just Development Team; 8.6.1.4.2 Product Owner and Scrum Master participate just in case they are part of Development Team or if invited. 8.6.2 Consists to: 8.6.2.1 Inspect the work done since last meeting 8.6.2.1.1 What has been accomplished since last Daily Scrum

What will be done before till next Daily Scrum What obstacles were faced Check daily progress toward 8.6.2.1.4.1.1 The Sprint Goal 8.6.2.1.4.1.2 The Sprint Backlog Completion 8.6.2.2 Define a plan until the next Daily Scrum 8.7 ADDITIONAL EVENT: DEVELOPMENT TEAM MEETING POST-DAILY SCRUM 8.7.1 Participation of just Development Team 8.7.2 Re-plan the rest of the Sprints work

8.6.2.1.2 8.6.2.1.3 8.6.2.1.4

8.8 ADDITIONAL EVENT: MONITORING PROGRESS TOWARD A GOAL 8.8.1 Made by the Product Owner 8.8.2 Made at least once before each Sprint Review. 8.8.3 Compare this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. 8.8.4 Time spent working on Product Backlog Items are not considered 8.8.5 Considers just the work remaining and desired delivery date 8.9 ADDITIONAL EVENT: SPRINT CANCELLATION 8.9.1 Only made by the Product Owner 8.9.2 It should happen just when the Sprint no longer makes sense given the current circumstances 8.9.3 It should happens every time Sprint Goal becomes obsolete, usually when: 8.9.3.1 Company changes direction 8.9.3.2 Market conditions change 8.9.3.3 Technology conditions change 8.9.4 Cancellation Results: 8.9.4.1 Review all completed and DONE Product Backlog Items 8.9.4.2 Shippable parts of Product are usually accepted by the Product Owner 8.9.4.3 Incomplete Product Backlog Items are re-estimated and put back on the Product Backlog 8.10 SCRUM EVENT: SPRINT REVIEW 8.10.1 Functioning: 8.10.1.1 All Scrum Team and Stakeholders participation 8.10.1.2 Informal Meeting 8.10.1.3 4 hours (1 month Sprint) 8.10.2 Concept: 8.10.2.1 Technical point-of-view review 8.10.2.2 Inspect the work done

8.10.2.3 Define what to do in the next Sprint 8.10.2.4 Adapt the Product Backlog if needed 8.10.3 Key Topics: 8.10.3.1 For Product Owner: 8.10.3.1.1 Identifies what was DONE or NOT DONE 8.10.3.1.2 Discusses current Product Backlog status 8.10.3.1.3 Projects likely completion dates based on current progress 8.10.3.2 For Development Team: 8.10.3.2.1 Issues review: 8.10.3.2.1.1.1 Success points 8.10.3.2.1.1.2 Problems faced 8.10.3.2.1.1.3 Solutions taken 8.10.3.2.2 ADDITIONAL ARTIFACT: INCREMENT PRESENTATION (here called SPRINT DEMO) 8.10.3.2.2.1.1 Intended to elicit feedback and foster collaboration 8.10.3.2.2.1.2 Answers questions about the Increment 8.10.3.3 For the entire group: 8.10.3.3.1 Collaboration about what to do next 8.10.4 Results: 8.10.4.1 Revised Product Backlog 8.10.4.1.1 Probable part of next Sprint Product Backlog Items

8.11

SCRUM EVENT: SPRINT RETROSPECTIVE 8.11.1 Functioning: 8.11.1.1 After Sprint Review and before Next Sprint Planning Meeting 8.11.1.2 3 hours (1 month Sprint) 8.11.2 Purpose: 8.11.2.1 Environmental point-of-view Review of ending Sprint: 8.11.2.1.1 Checks aspects about people, relationships, process, and tools 8.11.2.2 Identify and order: 8.11.2.2.1 Success points 8.11.2.2.2 Improvements to be done 8.11.2.3 Create a plan for implementing improvements 8.11.3 Input: 8.11.3.1 From Scrum Master: 8.11.3.1.1 Encouragement of Scrum Team to improve the development processes and practices

8.11.3.2 From All Scrum Team 8.11.3.2.1 Plans ways to increase product quality through the adaptation of DONE definition 8.11.3.2.2 [SUGGESTION]: Brainstorming to get the suggestions, based to a prior list of ideas by role 8.11.4 Output: 8.11.4.1 List of Improvements to be implemented in the next Sprint 9.0 SCRUM ARTIFACT: SPRINT 2 SPRINT N 9.1 The Sprint process restart and ends: 9.1.1 Until the last agreed shippable part of product is delivered, according to the DEFINITION OF DONE 10.0 AFTER PRODUCT DELIVERY AND USING 10.1 Once the Product was delivered, the product lifecycle is still active so, we can repeat all the process in order to deliver maintenance shippable items 10.2 PRODUCT BACKLOG 10.2.1 After the product development be finished and the product delivered, it should be converted in a Maintenance Product Backlog 10.2.1.1 Becomes larger once the product is used and gains value, and the marketplace provides feedback 10.2.1.2 Can be changed because of changes in business requirements, market conditions, or technology