Scrum Body of Knowledge (SBOK® Guide) 4th Edition PDF

A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK® GUIDE) Fourth Edition A Comprehensive Guide to Deliver Projects using Scrum (Includes two chapters about Scaling Scrum for Large Projects and the Enterprise) A Guide to the SCRUM BODY OF KNOWLEDGE (SBOK® Guide) Fourth Edition Includes two chapters about Scaling Scrum for Large Projects and the Enterprise A Comprehensive Guide to Deliver Projects using Scrum © 2022 SCRUMstudy™, a brand of VMEdu, Inc. All rights reserved. Library of Congress Cataloging-in-Publication Data A Guide to the Scrum Body of Knowledge (SBOK® Guide) – Fourth edition Includes bibliographical references and index. ISBN: 978-098992520-4 1. Scrum Framework. I. SCRUMstudy™. II. SBOK® Guide 2013950625 ISBN: 978-0-9899252-0-4 Published by: SCRUMstudy™, a brand of VMEdu, Inc. 12725 W. Indian School Road, Suite F-112 Avondale, Arizona 85392 USA Email: [email protected], [email protected] Website: www.scrumstudy.com “SBOK”, the SCRUMstudy logo, “SFC”, “SDC”, “SMC”, “SAMC”, “SPOC”, “SSMC”, “SSPOC”, and “ESMC” are trademarks of SCRUMstudy™ (a brand of VMEdu, Inc.) For a comprehensive list of SCRUMstudy™ marks, contact the SCRUMstudy™ Legal Department. A Guide to the Scrum Body of Knowledge (SBOK® Guide) is provided for educational purposes. SCRUMstudy™ or VMEdu, Inc. does not warrant that it is suitable for any other purpose and makes no expressed or implied warranty of any kind and assumes no responsibility for errors and omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information contained herein. SCRUMstudy™ welcomes corrections and comments on its books. Please feel free to send comments on typographical, formatting, or other errors. You can make a copy of the relevant page of the book, mark the error, and send it to the above address or send an email to [email protected]. No part of this work may be reproduced or transmitted in any form or by any means, electronic, manual, photocopying, recording, or by any information storage and retrieval system, without prior written permission of the publisher. 10 9 8 7 6 5 4 3 2 PREFACE A Guide to the Scrum Body of Knowledge (SBOK® Guide) provides guidelines for the successful implementation of Scrum—the most popular Agile product development and project delivery approach. Scrum, as defined in the SBOK® Guide, is a framework which is applicable to portfolios, programs, or projects of any size or complexity; and may be applied effectively in any industry to create a product, service, or any other result. The SBOK® Guide is intended for use as a reference and knowledge guide by both experienced Scrum and other product or service development practitioners, as well as by persons with no prior experience or knowledge of Scrum or any other project delivery method. This new edition of the SBOK® Guide provides additional insight into Scrum best practices, particularly in the areas of scaling Scrum. As the popularity and application of the Scrum framework grows and evolves globally, our goal is to share the lessons learned and best practices as part of the SBOK® Guide. The SBOK® Guide draws from the combined knowledge and insight gained from thousands of projects across a variety of organizations and industries. This Fourth Edition adds to the collective contributions of experts in Scrum and project delivery. In particular, feedback from the global Scrum community played a large role in identifying improvements and additions to the SBOK® Guide. Its development has truly been a collaborative effort from a large number of experts and practitioners in a variety of disciplines. Wide adoption of the SBOK® Guide framework standardizes how Scrum is applied to projects across organizations globally, as well as significantly helps to improve their Return on Investment. Additionally, it promotes greater thought and deliberation regarding the application of Scrum to many types of projects, which will in turn contribute towards expanding and enriching the body of knowledge and consequently future updates to this guide. Although the SBOK® Guide is a comprehensive guide and framework for delivering projects using Scrum, its contents are organized for easy reference, regardless of the reader’s prior knowledge on the subject. I hope each reader will learn from and enjoy it as much as the many authors and reviewers learned from and enjoyed the process of collating the collective knowledge and wisdom contained within it. Tridibesh Satpathy, Lead Author, SBOK® Guide TABLE OF CONTENTS TABLE OF CONTENTS 1. INTRODUCTION............................................................................................................................................. 1 1.1 Overview of Scrum................................................................................................................................. 2 1.1.1 Brief History of Scrum.................................................................................................................... 3 1.2 Why Use Scrum?.................................................................................................................................... 4 1.2.1 Scalability of Scrum....................................................................................................................... 5 1.3 Purpose of the SBOK® Guide................................................................................................................. 6 1.4 Framework of the SBOK® Guide............................................................................................................. 7 1.4.1 How to Use the SBOK® Guide?..................................................................................................... 8 1.4.2 Scrum Principles............................................................................................................................ 9 1.4.3 Scrum Aspects............................................................................................................................. 11 1.4.4 Scrum Processes......................................................................................................................... 15 1.4.5 Scrum for Large Projects............................................................................................................. 19 1.4.6 Scrum for the Enterprise.............................................................................................................. 19 1.5 Scrum vs. Traditional Project Management.......................................................................................... 20 2. PRINCIPLES................................................................................................................................................. 21 2.1 Introduction........................................................................................................................................... 21 2.2 Roles Guide.......................................................................................................................................... 22 2.3 Empirical Process Control.................................................................................................................... 22 2.3.1 Transparency............................................................................................................................... 22 2.3.2 Inspection..................................................................................................................................... 24 2.3.3 Adaptation.................................................................................................................................... 24 2.4 Self-organization................................................................................................................................... 27 2.4.1 Benefits of Self-organization........................................................................................................ 27 2.5 Collaboration........................................................................................................................................ 29 2.5.1 Benefits of Collaboration in Scrum Projects................................................................................. 29 2.5.2 Importance of Colocation in Collaboration................................................................................... 31 2.5.3 Collaboration in Distributed Teams.............................................................................................. 31 2.6 Value-based Prioritization..................................................................................................................... 33 2.7 Time-boxing.......................................................................................................................................... 35 2.7.1 Scrum Time-boxes....................................................................................................................... 35 2.8 Iterative Development........................................................................................................................... 38 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) I TABLE OF CONTENTS 2.9 Scrum vs. Traditional Project Management.......................................................................................... 40 3. ORGANIZATION........................................................................................................................................... 41 3.1 Introduction........................................................................................................................................... 41 3.2 Roles Guide.......................................................................................................................................... 42 3.3 Scrum Project Roles............................................................................................................................. 42 3.3.1 Core Roles................................................................................................................................... 42 3.3.2 Non-core Roles............................................................................................................................ 43 3.4 Product Owner...................................................................................................................................... 45 3.4.1 Voice of the Customer (VOC)...................................................................................................... 47 3.5 Scrum Master....................................................................................................................................... 47 3.6 Scrum Team......................................................................................................................................... 49 3.6.1 Personnel Selection..................................................................................................................... 50 3.6.2 Scrum Team Size........................................................................................................................ 50 3.7 Scrum in Large Projects, Programs, and Portfolios.............................................................................. 51 3.7.1 Making Scrum Work in a Large Project........................................................................................ 51 3.7.2 Additional Core Roles in a Large Project..................................................................................... 52 3.7.3 Making Scrum Work in an Enterprise Environment..................................................................... 54 3.7.4 Additional Core Roles in an Enterprise Environment................................................................... 55 3.7.5 Examples of Projects, Programs, and Portfolios.......................................................................... 57 3.8 Summary of Responsibilities................................................................................................................ 59 3.9 Scrum vs. Traditional Project Management.......................................................................................... 60 3.10 Popular HR Theories and their Relevance to Scrum............................................................................ 61 3.10.1 Tuckman’s Model of Group Dynamics......................................................................................... 61 3.10.2 Conflict Management................................................................................................................... 62 3.10.3 Conflict Management Techniques............................................................................................... 62 3.10.4 Leadership Styles........................................................................................................................ 63 3.10.5 Maslow’s Hierarchy of Needs Theory.......................................................................................... 65 3.10.6 Theory X, Theory Y, and Theory Z............................................................................................... 66 4. BUSINESS JUSTIFICATION......................................................................................................................... 67 4.1 Introduction........................................................................................................................................... 67 4.2 Roles Guide.......................................................................................................................................... 68 4.3 Value-driven Delivery............................................................................................................................ 68 4.3.1 Responsibilities of the Product Owner in Business Justification.................................................. 70 II © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) TABLE OF CONTENTS 4.3.2 Responsibilities of Other Scrum Roles in Business Justification.................................................. 70 4.4 Importance of Business Justification.................................................................................................... 71 4.4.1 Factors Used to Determine Business Justification....................................................................... 71 4.4.2 Business Justification and the Project Lifecycle........................................................................... 72 4.5 Business Justification Techniques........................................................................................................ 74 4.5.1 Estimation of Project Value.......................................................................................................... 74 4.5.2 Planning for Value........................................................................................................................ 76 4.5.3 Relative Prioritization Ranking..................................................................................................... 78 4.5.4 Story Mapping.............................................................................................................................. 79 4.6 Continuous Value Justification.............................................................................................................. 80 4.6.1 Earned Value Analysis (EVA)...................................................................................................... 80 4.6.2 Cumulative Flow Diagram (CFD)................................................................................................. 83 4.7 Confirm Benefits Realization................................................................................................................ 84 4.7.1 Prototypes, Simulations, and Demonstrations............................................................................. 84 4.8 Summary of Responsibilities................................................................................................................ 85 4.9 Scrum vs. Traditional Project Management.......................................................................................... 86 5. QUALITY....................................................................................................................................................... 87 5.1 Introduction........................................................................................................................................... 87 5.2 Roles Guide.......................................................................................................................................... 88 5.3 Quality Defined..................................................................................................................................... 88 5.3.1 Quality and Scope........................................................................................................................ 88 5.3.2 Quality and Business Value......................................................................................................... 89 5.4 Acceptance Criteria and the Prioritized Product Backlog..................................................................... 90 5.4.1 Writing Acceptance Criteria......................................................................................................... 91 5.4.2 Definition of Ready....................................................................................................................... 92 5.4.3 Definition of Done (or Done Criteria)............................................................................................ 92 5.4.4 Minimum Done Criteria................................................................................................................ 93 5.4.5 Acceptance or Rejection of Prioritized Product Backlog Items.................................................... 94 5.5 Quality Management in Scrum............................................................................................................. 95 5.5.1 Quality Planning........................................................................................................................... 95 5.5.2 Quality Assurance and Quality Control........................................................................................ 97 5.5.3 Plan-Do-Check-Act (PDCA) Cycle............................................................................................... 97 5.6 Summary of Responsibilities................................................................................................................ 99 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) III TABLE OF CONTENTS 5.7 Scrum vs. Traditional Project Management........................................................................................ 100 6. CHANGE..................................................................................................................................................... 101 6.1 Introduction......................................................................................................................................... 101 6.2 Roles Guide........................................................................................................................................ 102 6.3 Overview............................................................................................................................................. 102 6.3.1 Unapproved and Approved Change Requests.......................................................................... 103 6.4 Understanding Change in Scrum........................................................................................................ 104 6.4.1 Balancing Flexibility and Stability............................................................................................... 104 6.4.2 Incorporating Flexibility.............................................................................................................. 105 6.5 Integrating Change............................................................................................................................. 110 6.5.1 Changes to a Sprint................................................................................................................... 110 6.6 Change in Programs and Portfolios.................................................................................................... 115 6.6.1 In Programs............................................................................................................................... 115 6.6.2 In Portfolios................................................................................................................................ 115 6.7 Summary of Responsibilities.............................................................................................................. 117 6.8 Scrum vs. Traditional Project Management........................................................................................ 118 7. RISK............................................................................................................................................................ 119 7.1 Introduction......................................................................................................................................... 119 7.2 Roles Guide........................................................................................................................................ 120 7.3 What is Risk?...................................................................................................................................... 120 7.3.1 Difference between Risks and Issues........................................................................................ 120 7.3.2 Risk Attitude............................................................................................................................... 121 7.4 Risk Management Procedure............................................................................................................. 122 7.4.1 Risk Identification....................................................................................................................... 122 7.4.2 Risk Assessment....................................................................................................................... 123 7.4.3 Risk Prioritization....................................................................................................................... 126 7.4.4 Risk Mitigation............................................................................................................................ 127 7.4.5 Risk Communication.................................................................................................................. 128 7.5 Minimizing Risks through Scrum........................................................................................................ 130 7.6 Risks in Portfolios and Programs........................................................................................................ 131 7.6.1 In Portfolios................................................................................................................................ 131 7.6.2 In Programs............................................................................................................................... 131 7.7 Summary of Responsibilities.............................................................................................................. 133 IV © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) TABLE OF CONTENTS 7.8 Scrum vs. Traditional Project Management........................................................................................ 134 8. INITIATE...................................................................................................................................................... 135 8.1 Create Project Vision.......................................................................................................................... 139 8.1.1 Inputs......................................................................................................................................... 141 8.1.2 Tools.......................................................................................................................................... 142 8.1.3 Outputs...................................................................................................................................... 144 8.2 Identify Scrum Master and Business Stakeholder(s).......................................................................... 145 8.2.1 Inputs......................................................................................................................................... 147 8.2.2 Tools.......................................................................................................................................... 148 8.2.3 Outputs...................................................................................................................................... 150 8.3 Form Scrum Team.............................................................................................................................. 151 8.3.1 Inputs......................................................................................................................................... 153 8.3.2 Tools.......................................................................................................................................... 154 8.3.3 Outputs...................................................................................................................................... 156 8.4 Develop Epic(s).................................................................................................................................. 158 8.4.1 Inputs......................................................................................................................................... 159 8.4.2 Tools.......................................................................................................................................... 162 8.4.3 Outputs...................................................................................................................................... 164 8.5 Create Prioritized Product Backlog..................................................................................................... 166 8.5.1 Inputs......................................................................................................................................... 167 8.5.2 Tools.......................................................................................................................................... 169 8.5.3 Outputs...................................................................................................................................... 172 8.6 Conduct Release Planning................................................................................................................. 174 8.6.1 Inputs......................................................................................................................................... 175 8.6.2 Tools.......................................................................................................................................... 177 8.6.3 Outputs...................................................................................................................................... 178 8.7 Initiate Phase Data Flow Diagram...................................................................................................... 180 9. PLAN AND ESTIMATE............................................................................................................................... 181 9.1 Create User Stories............................................................................................................................ 185 9.1.1 Inputs......................................................................................................................................... 186 9.1.2 Tools.......................................................................................................................................... 188 9.1.3 Outputs...................................................................................................................................... 189 9.2 Estimate User Stories......................................................................................................................... 191 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) V TABLE OF CONTENTS 9.2.1 Inputs......................................................................................................................................... 192 9.2.2 Tools.......................................................................................................................................... 193 9.2.3 Outputs...................................................................................................................................... 195 9.3 Commit User Stories........................................................................................................................... 196 9.3.1 Inputs......................................................................................................................................... 197 9.3.2 Tools.......................................................................................................................................... 198 9.3.3 Outputs...................................................................................................................................... 199 9.4 Identify Tasks..................................................................................................................................... 201 9.4.1 Inputs......................................................................................................................................... 202 9.4.2 Tools.......................................................................................................................................... 203 9.4.3 Outputs...................................................................................................................................... 204 9.5 Estimate Tasks................................................................................................................................... 206 9.5.1 Inputs......................................................................................................................................... 207 9.5.2 Tools.......................................................................................................................................... 208 9.5.3 Outputs...................................................................................................................................... 209 9.6 Update Sprint Backlog........................................................................................................................ 210 9.6.1 Inputs......................................................................................................................................... 212 9.6.2 Tools.......................................................................................................................................... 213 9.6.3 Outputs...................................................................................................................................... 214 9.7 Plan and Estimate Phase Data Flow Diagram.................................................................................... 216 10. IMPLEMENT............................................................................................................................................... 217 10.1 Create Deliverables............................................................................................................................ 221 10.1.1 Inputs......................................................................................................................................... 223 10.1.2 Tools.......................................................................................................................................... 226 10.1.3 Outputs...................................................................................................................................... 227 10.2 Conduct Daily Standup....................................................................................................................... 229 10.2.1 Inputs......................................................................................................................................... 231 10.2.2 Tools.......................................................................................................................................... 232 10.2.3 Outputs...................................................................................................................................... 233 10.3 Refine Prioritized Product Backlog..................................................................................................... 235 10.3.1 Inputs......................................................................................................................................... 236 10.3.2 Tools.......................................................................................................................................... 238 10.3.3 Outputs...................................................................................................................................... 239 VI © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) TABLE OF CONTENTS 10.4 Implement Phase Data Flow Diagram................................................................................................ 240 11. REVIEW AND RETROSPECT.................................................................................................................... 241 11.1 Demonstrate and Validate Sprint........................................................................................................ 244 11.1.1 Inputs......................................................................................................................................... 246 11.1.2 Tools.......................................................................................................................................... 247 11.1.3 Outputs...................................................................................................................................... 248 11.2 Retrospect Sprint................................................................................................................................ 250 11.2.1 Inputs......................................................................................................................................... 251 11.2.2 Tools.......................................................................................................................................... 252 11.2.3 Outputs...................................................................................................................................... 254 11.3 Review and Retrospect Phase Data Flow Diagram............................................................................ 256 12. RELEASE.................................................................................................................................................... 257 12.1 Ship Deliverables................................................................................................................................ 260 12.1.1 Inputs......................................................................................................................................... 261 12.1.2 Tools.......................................................................................................................................... 263 12.1.3 Outputs...................................................................................................................................... 263 12.2 Retrospect Release............................................................................................................................ 265 12.2.1 Inputs......................................................................................................................................... 267 12.2.2 Tools.......................................................................................................................................... 268 12.2.3 Outputs...................................................................................................................................... 269 12.3 Release Phase Data Flow Diagram.................................................................................................... 270 13. SCALING SCRUM FOR LARGE PROJECTS............................................................................................. 271 13.1 Impact of Large Projects to Fundamental Scrum Processes.............................................................. 273 13.1.1 Initiate........................................................................................................................................ 273 13.1.2 Plan and Estimate...................................................................................................................... 278 13.1.3 Implement.................................................................................................................................. 281 13.1.4 Review and Retrospect.............................................................................................................. 283 13.1.5 Release...................................................................................................................................... 285 13.2 Additional Inputs and Outputs for Large Projects............................................................................... 286 13.2.1 Large Project Scrum Organization*............................................................................................ 286 13.2.2 Product Owners Collaboration Plan*.......................................................................................... 286 13.2.3 Scrum Masters/Scrum Teams Collaboration Plan*.................................................................... 286 13.2.4 Shared Resources*.................................................................................................................... 287 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) VII TABLE OF CONTENTS 13.2.5 Team Specialization*................................................................................................................. 287 13.2.6 Environment and Environment Schedule*................................................................................. 288 13.2.7 Release Readiness Plan*.......................................................................................................... 288 13.3 Additional Tools for Large Projects..................................................................................................... 290 13.3.1 Large Project Communications Plan.......................................................................................... 290 13.3.2 Large Project Resource Planning*............................................................................................. 290 13.3.3 Environment Identification*........................................................................................................ 291 13.3.4 Prioritized Product Backlog Assignment*................................................................................... 291 13.3.5 Scrum of Scrums (SoS) Meeting*.............................................................................................. 292 13.3.6 Release Preparation Methods*.................................................................................................. 293 13.3.7 Release Readiness Sprint......................................................................................................... 293 13.3.8 Scrum Project Tool.................................................................................................................... 293 14. SCALING SCRUM FOR THE ENTERPRISE.............................................................................................. 295 14.1 Impact of Programs or Portfolios to Fundamental Scrum Processes................................................. 298 14.1.1 Initiate........................................................................................................................................ 298 14.1.2 Plan and Estimate...................................................................................................................... 301 14.1.3 Implement.................................................................................................................................. 301 14.1.4 Review and Retrospect.............................................................................................................. 302 14.1.5 Release...................................................................................................................................... 302 14.2 Additional Processes to Scale Scrum for the Enterprise (Program/Portfolio)..................................... 304 14.3 Create/Update Program or Portfolio Teams....................................................................................... 307 14.3.1 Inputs......................................................................................................................................... 308 14.3.2 Tools.......................................................................................................................................... 309 14.3.3 Outputs...................................................................................................................................... 309 14.4 Create/Update Program or Portfolio Components.............................................................................. 311 14.4.1 Inputs......................................................................................................................................... 312 14.4.2 Tools.......................................................................................................................................... 313 14.4.3 Outputs...................................................................................................................................... 315 14.5 Review and Update Scrum Guidance Body........................................................................................ 317 14.5.1 Inputs......................................................................................................................................... 318 14.5.2 Tools.......................................................................................................................................... 318 14.5.3 Outputs...................................................................................................................................... 319 14.6 Create/Refine Prioritized Program or Portfolio Backlog...................................................................... 320 VIII © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) TABLE OF CONTENTS 14.6.1 Inputs......................................................................................................................................... 321 14.6.2 Tools.......................................................................................................................................... 323 14.6.3 Outputs...................................................................................................................................... 325 14.7 Create/Update Program or Portfolio Releases................................................................................... 326 14.7.1 Inputs......................................................................................................................................... 327 14.7.2 Tools.......................................................................................................................................... 328 14.7.3 Outputs...................................................................................................................................... 329 14.8 Retrospect Program or Portfolio Releases......................................................................................... 330 14.8.1 Inputs......................................................................................................................................... 330 14.8.2 Tools.......................................................................................................................................... 332 14.8.3 Outputs...................................................................................................................................... 332 APPENDIX A. OVERVIEW OF AGILE................................................................................................................. 333 APPENDIX B. SBOK® GUIDE AUTHORS AND CONTRIBUTORS..................................................................... 343 APPENDIX C. FOURTH EDITION UPDATES..................................................................................................... 347 REFERENCES..................................................................................................................................................... 353 GLOSSARY......................................................................................................................................................... 355 INDEX.................................................................................................................................................................. 393 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) IX LIST OF FIGURES LIST OF FIGURES Figure 1-1: Scrum Flow for One Sprint..................................................................................................................... 2 Figure 1-2: SBOK® Guide Framework..................................................................................................................... 7 Figure 1-3: Scrum Principles.................................................................................................................................... 9 Figure 1-4: Organization in Scrum......................................................................................................................... 12 Figure 2-1: Transparency in Scrum........................................................................................................................ 23 Figure 2-2: Inspection in Scrum............................................................................................................................. 24 Figure 2-3: Adaptation in Scrum............................................................................................................................ 25 Figure 2-4: Challenges in Traditional Project Management................................................................................... 26 Figure 2-5: Goals of a Self-organizing Team......................................................................................................... 28 Figure 2-6: Benefits of Collaboration in Scrum Projects......................................................................................... 30 Figure 2-7: Value-based Prioritization.................................................................................................................... 34 Figure 2-8: Time-Box Durations for Scrum Meetings............................................................................................. 37 Figure 2-9: Scrum vs. Traditional Waterfall............................................................................................................ 39 Figure 3-1: Scrum Roles—Overview...................................................................................................................... 43 Figure 3-2: Desirable Traits for the Core Scrum Roles.......................................................................................... 50 Figure 3-3: Questions Asked during a Scrum of Scrums Meeting.......................................................................... 53 Figure 3-4: Scrum across the Organization for Projects, Programs, and Portfolios............................................... 58 Figure 3-5: Tuckman’s Stages of Group Development.......................................................................................... 61 Figure 3-6: Maslow’s Hierarchy of Needs Theory.................................................................................................. 65 Figure 4-1: Delivering Value in Scrum vs. Traditional Projects.............................................................................. 69 Figure 4-2: Hierarchy for Business Justification Responsibilities........................................................................... 70 Figure 4-3: Business Justification and the Project Lifecycle.................................................................................. 73 Figure 4-4: Value Stream Mapping........................................................................................................................ 76 Figure 4-5: Kano Analysis...................................................................................................................................... 78 Figure 4-6: Story Mapping...................................................................................................................................... 79 Figure 4-7: Sample Cumulative Flow Diagram (CFD)............................................................................................ 83 Figure 5-1: Project Increment Flow Diagram.......................................................................................................... 91 Figure 5-2: PDCA Cycle in Scrum.......................................................................................................................... 98 Figure 6-1: Sample Change Approval Process.................................................................................................... 103 Figure 6-2: Updating Prioritized Product Backlog with Approved Changes......................................................... 104 Figure 6-3: Scrum Characteristics for Achieving Flexibility.................................................................................. 105 Figure 6-4: Motivation of Business Stakeholders for Requesting Changes......................................................... 106 Figure 6-5: Motivation of Scrum Core Team for Requesting Changes................................................................. 107 Figure 6-6: Incorporating a Change during a Sprint............................................................................................. 111 Figure 6-7: Impact of the Probability of Change on the Length of Sprint.............................................................. 112 Figure 6-8: Incorporating Changes in Programs and Portfolios........................................................................... 116 Figure 7-1: Sample Probability Tree..................................................................................................................... 124 Figure 7-2: Sample Pareto Chart......................................................................................................................... 124 Figure 7-3: Sample Probability and Impact Matrix............................................................................................... 125 Figure 7-4: Process for Risk Prioritization............................................................................................................ 127 Figure 7-5: Sample Risk Burndown Chart............................................................................................................ 129 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) XI LIST OF FIGURES Figure 7-6: Handling Risks in Portfolios and Programs........................................................................................ 132 Figure 8-1: Initiate Overview................................................................................................................................ 137 Figure 8-2: Initiate Overview (Essentials)............................................................................................................. 138 Figure 8-3: Create Project Vision—Inputs, Tools, and Outputs............................................................................ 139 Figure 8-4: Create Project Vision—Data Flow Diagram....................................................................................... 140 Figure 8-5: The Gap Analysis Process................................................................................................................. 143 Figure 8-6: Identify Scrum Master and Business Stakeholder(s)—Inputs, Tools, and Outputs............................ 145 Figure 8-7: Identify Scrum Master and Business Stakeholder(s)—Data Flow Diagram....................................... 146 Figure 8-8: Form Scrum Team—Inputs, Tools, and Outputs............................................................................... 151 Figure 8-9: Form Scrum Team—Data Flow Diagram........................................................................................... 152 Figure 8-10: Develop Epic(s)—Inputs, Tools, and Outputs.................................................................................. 158 Figure 8-11: Develop Epic(s)—Data Flow Diagram............................................................................................. 159 Figure 8-12: Create Prioritized Product Backlog—Inputs, Tools, and Outputs.................................................... 166 Figure 8-13: Create Prioritized Product Backlog—Data Flow Diagram................................................................ 167 Figure 8-14: Conduct Release Planning—Inputs, Tools, and Outputs................................................................. 174 Figure 8-15: Conduct Release Planning—Data Flow Diagram............................................................................ 175 Figure 8-16: Initiate Phase—Data Flow Diagram................................................................................................. 180 Figure 9-1: Plan and Estimate Overview.............................................................................................................. 183 Figure 9-2: Plan and Estimate Overview (Essentials).......................................................................................... 184 Figure 9-3: Create User Stories—Inputs, Tools, and Outputs.............................................................................. 185 Figure 9-4: Create User Stories—Data Flow Diagram......................................................................................... 186 Figure 9-5: Estimate User Stories—Inputs, Tools, and Outputs........................................................................... 191 Figure 9-6: Estimate User Stories—Data Flow Diagram...................................................................................... 192 Figure 9-7: Commit User Stories—Inputs, Tools, and Outputs............................................................................ 196 Figure 9-8: Commit User Stories—Data Flow Diagram....................................................................................... 197 Figure 9-9: Typical Scrumboard........................................................................................................................... 200 Figure 9-10: Scrumboard with Four Sections....................................................................................................... 200 Figure 9-11: Identify Tasks—Inputs, Tools, and Outputs..................................................................................... 201 Figure 9-12: Identify Tasks—Data Flow Diagram................................................................................................ 202 Figure 9-13: Scrumboard with Identified Tasks.................................................................................................... 205 Figure 9-14: Estimate Tasks—Inputs, Tools, and Outputs................................................................................... 206 Figure 9-15: Estimate Tasks—Data Flow Diagram.............................................................................................. 207 Figure 9-16: Update Sprint Backlog—Inputs, Tools, and Outputs........................................................................ 210 Figure 9-17: Update Sprint Backlog—Data Flow Diagram................................................................................... 211 Figure 9-18: Sprint Burndown Chart..................................................................................................................... 215 Figure 9-19: Sprint Burnup Chart......................................................................................................................... 215 Figure 9-20: Plan and Estimate Phase—Data Flow Diagram.............................................................................. 216 Figure 10-1: Implement Overview........................................................................................................................ 219 Figure 10-2: Implement Overview (Essentials).................................................................................................... 220 Figure 10-3: Create Deliverables—Inputs, Tools, and Outputs............................................................................ 221 Figure 10-4: Create Deliverables—Data Flow Diagram....................................................................................... 222 Figure 10-5: Scrumboard with Tasks To Do, In Progress, and Complete............................................................ 224 Figure 10-6: Conduct Daily Standup—Inputs, Tools, and Outputs....................................................................... 229 Figure 10-7: Conduct Daily Standup—Data Flow Diagram.................................................................................. 230 XII © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) LIST OF FIGURES Figure 10-8: Refine Prioritized Product Backlog—Inputs, Tools, and Outputs..................................................... 235 Figure 10-9: Refine Prioritized Product Backlog—Data Flow Diagram................................................................ 236 Figure 10-10: Implement Phase—Data Flow Diagram......................................................................................... 240 Figure 11-1: Review and Retrospect Overview.................................................................................................... 242 Figure 11-2: Review and Retrospect Overview (Essentials)................................................................................ 243 Figure 11-3: Demonstrate and Validate Sprint—Inputs, Tools, and Outputs....................................................... 244 Figure 11-4: Demonstrate and Validate Sprint—Data Flow Diagram................................................................... 245 Figure 11-5: Retrospect Sprint—Inputs, Tools, and Outputs............................................................................... 250 Figure 11-6: Retrospect Sprint—Data Flow Diagram........................................................................................... 251 Figure 11-7: Review and Retrospect Phase—Data Flow Diagram...................................................................... 256 Figure 12-1: Release Overview............................................................................................................................ 258 Figure 12-2: Release Overview (Essentials)........................................................................................................ 259 Figure 12-3: Ship Deliverables—Inputs, Tools, and Outputs............................................................................... 260 Figure 12-4: Ship Deliverables—Data Flow Diagram........................................................................................... 261 Figure 12-5: Retrospect Release—Inputs, Tools, and Outputs............................................................................ 265 Figure 12-6: Retrospect Release—Data Flow Diagram....................................................................................... 266 Figure 12-7: Release Phase—Data Flow Diagram.............................................................................................. 270 Figure 14-1: Scaling Scrum for the Enterprise..................................................................................................... 306 Figure 14-2: Create/Update Program or Portfolio Teams—Inputs, Tools, and Outputs....................................... 307 Figure 14-3: Create/Update Program or Portfolio Components—Inputs, Tools, and Outputs.............................. 311 Figure 14-4: Scrum of Scrums of Scrums (SoSoS) Meeting................................................................................ 314 Figure 14-5: Review and Update Scrum Guidance Body—Inputs, Tools, and Outputs....................................... 317 Figure 14-6: Create/Refine Prioritized Program or Portfolio Backlog—Inputs, Tools, and Outputs..................... 320 Figure 14-7: Create/Update Program or Portfolio Releases—Inputs, Tools, and Outputs................................... 326 Figure 14-8: Retrospect Program or Portfolio Releases—Inputs, Tools, and Outputs......................................... 330 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) XIII LIST OF TABLES LIST OF TABLES Table 1-1: Summary of Fundamental Scrum Processes........................................................................................ 15 Table 1-2: Scrum Meetings and Processes........................................................................................................... 18 Table 1-3: Scrum vs. Traditional Project Management.......................................................................................... 20 Table 3-1: Responsibilities of the Product Owner in Scrum Processes................................................................. 46 Table 3-2: Responsibilities of the Scrum Master in Scrum Processes................................................................... 48 Table 3-3: Responsibilities of the Scrum Team in Scrum Processes..................................................................... 49 Table 3-4: Summary of Responsibilities Relevant to Organization........................................................................ 59 Table 4-1: Earned Value Formulas........................................................................................................................ 81 Table 4-2: Summary of Responsibilities Relevant to Business Justification.......................................................... 85 Table 5-1: Cascading Done Criteria....................................................................................................................... 93 Table 5-2: Summary of Responsibilities Relevant to Quality................................................................................. 99 Table 6-1: Summary of Responsibilities Relevant to Change.............................................................................. 117 Table 7-1: Summary of Responsibilities Relevant to Risk.................................................................................... 133 Table 13-1: Impact of Large Projects to Fundamental Scrum Processes—Initiate Phase................................... 277 Table 13-2: Impact of Large Projects to Fundamental Scrum Processes—Plan and Estimate Phase................ 280 Table 13-3: Impact of Large Projects to Fundamental Scrum Processes—Implement Phase............................. 282 Table 13-4: Impact of Large Projects to Fundamental Scrum Processes—Review and Retrospect Phase........ 284 Table 13-5: Impact of Large Projects to Fundamental Scrum Processes—Release Phase................................ 285 Table 14-1: Impact of a Program or Portfolio to Fundamental Scrum Processes—Initiate Phase....................... 300 Table 14-2: Impact of a Program or Portfolio to Fundamental Scrum Processes—Implement Phase................. 301 Table 14-3: Impact of a Program or Portfolio to Fundamental Scrum Processes—Review & Retrospect Phase 302 Table 14-4: Impact of a Program or Portfolio to Fundamental Scrum Processes—Release Phase.................... 303 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) XV 1 – INTRODUCTION 1 1. INTRODUCTION A Guide to the Scrum Body of Knowledge (SBOK® Guide) provides guidelines for the successful implementation of Scrum—the most popular Agile project delivery and product development approach. It provides a comprehensive framework that includes the principles, aspects, and processes of Scrum. Scrum, as defined in the SBOK® Guide, is applicable to the following: Portfolios, programs, and/or projects in any industry Products, services, or any other results to be delivered to business stakeholders Projects of any size or complexity The term “product” in the SBOK® Guide may refer to a product, service, or other deliverable. Scrum can be applied effectively to any project in any industry—from small projects or teams with as few as six team members to large, complex projects with up to several hundred members in several teams. This first chapter describes the purpose and framework of the SBOK® Guide and provides an introduction to the key concepts of Scrum. It contains a summary of Scrum principles, Scrum aspects and Scrum processes. Chapter 2 expands on the six Scrum principles which are the foundation on which the Scrum framework is based. Chapters 3 through 7 elaborate on the five Scrum aspects that must be addressed throughout any project: organization, business justification, quality, change, and risk. Chapters 8 through 12 cover the 19 Scrum processes involved in carrying out a Scrum project. These processes are part of the five Scrum phases: Initiate; Plan and Estimate; Implement; Review and Retrospect; and Release. These phases describe in detail the associated inputs and outputs of each process, as well as the various tools that may be used in each process. Some inputs, tools, and outputs are mandatory and are indicated as such; others are optional and can be used depending on the specific project, organizational requirements, and/or guidelines set forth by the organization’s Scrum Guidance Body (SGB). Chapters 13 and 14 provide guidance on scaling Scrum for large projects and at the enterprise level (which involves programs and portfolios). This chapter is divided into the following sections: 1.1 Overview of Scrum 1.2 Why Use Scrum? 1.3 Purpose of the SBOK® Guide 1.4 Framework of the SBOK® Guide 1.5 Scrum vs. Traditional Project Management © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 1 1 – INTRODUCTION 1.1 Overview of Scrum A Scrum project involves a collaborative effort to create a new product, service, or other result as defined in the Project Vision Statement. Projects are impacted by constraints of time, cost, scope, quality, resources, organizational capabilities, and other limitations that make them difficult to plan, execute, manage, and ultimately succeed. However, successful implementation of the results of a finished project provides significant business benefits to an organization. It is therefore important for organizations to select and practice an appropriate project management approach. Scrum is one of the most popular Agile frameworks. It is an adaptive, iterative, fast, flexible, and effective framework designed to deliver significant value quickly and throughout a project. Although, the Scrum framework as defined in the SBOK® Guide is primarily used to deliver projects and create products, Scrum may also be used to manage the continuous maintenance of products and services, to track issues, and to manage changes. Scrum ensures transparency in communication and creates an environment of collective accountability and continuous progress. The Scrum framework, as defined in the SBOK® Guide, is structured in such a way that it supports product and service development in all types of industries and in any type of project, irrespective of its complexity. A key strength of Scrum lies in its use of cross-functional, self-organized, and empowered teams who divide their work into short, concentrated work cycles called Sprints. Figure 1-1 provides an overview of a Scrum project’s flow. Figure 1-1: Scrum Flow for One Sprint The Scrum cycle begins with a Stakeholder Meeting, during which the Project Vision is created. The Product Owner then develops a Prioritized Product Backlog which contains a prioritized list of business and project requirements written in the form of User Stories. Each Sprint begins with a Sprint Planning Meeting during which high priority User Stories are considered for inclusion in the Sprint. A Sprint generally lasts between one and four weeks and involves the Scrum Team 2 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 1 – INTRODUCTION 1 working to create potentially shippable deliverables or product increments. During the Sprint, short, highly focused Daily Standup Meetings are conducted where team members discuss daily progress. The Product Owner can assess completed deliverables during the Sprint and can accept the deliverables that meet the predefined Acceptance Criteria. Toward the end of the Sprint, a Sprint Review Meeting is held during which the Product Owner and relevant business stakeholders are provided a demonstration of the deliverables. The Sprint cycle ends with a Retrospect Sprint Meeting where the team members discuss ways they can improve the way they work and their performance as they move forward into the subsequent Sprint. 1.1.1 Brief History of Scrum In the mid 80’s, Hirotaka Takeuchi and Ikujiro Nonaka defined a flexible and all-inclusive product development strategy where the development team works as a unit to reach a common goal. They described an innovative approach to product development that they called a holistic or “rugby” approach, “where a team tries to go the distance as a unit, passing the ball back and forth.” The authors based their approach on manufacturing case studies from various industries. Takeuchi and Nonaka proposed that product development should not be like a sequential relay race, but rather should be analogous to the game of rugby where the team works together, passing the ball back and forth as they move as a unit down the field. The rugby concept of a “Scrum” (where a group of players form together to restart the game) was introduced in this article to describe the authors’ proposal that product development should involve “moving the Scrum downfield.” Since then, several Scrum practitioners, experts, and authors have continued to refine the Scrum conceptualization and framework based on best practices. A major milestone in the Scrum journey was the creation of the original version of the SBOK® Guide in 2013. Over time, the SBOK® Guide has been continuously improved based on reviews and feedback provided by several thousand Scrum and Agile practitioners, including 5000+ faculty in 110+ countries who teach Scrum and Agile practices using the SBOK® Guide framework. This fourth edition is the product of further refinements that ensure the SBOK® Guide continues to remain valid and relevant in an ever-changing world. The SBOK® Guide is now the industry standard for companies and practitioners interested in implementing Scrum or Agile practices. In recent years, Scrum has increased in popularity and is now the preferred project development approach for many organizations globally. To facilitate its application across multinational settings, the SBOK® Guide has been translated into multiple languages including Spanish, Portuguese, French, Italian, Arabic, Chinese, and Japanese. For more information about accessing translated versions, please visit www.scrumstudy.com. © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 3 1 – INTRODUCTION 1.2 Why Use Scrum? Some of the key benefits of using Scrum in any project are: 1. Adaptability—Empirical process control and iterative delivery make projects adaptable and open to incorporating change. 2. Transparency—All information radiators like a Scrumboard and Sprint Burndown Chart are shared, leading to an open work environment. 3. Continuous Feedback—Continuous feedback is provided through the Conduct Daily Standup and Demonstrate and Validate Sprint processes. 4. Continuous Improvement—The deliverables are improved progressively Sprint by Sprint, through the Refine Prioritized Product Backlog process. 5. Continuous Delivery of Value—Iterative processes enable the continuous delivery of value through the Ship Deliverables process as frequently as the customer requires. 6. Sustainable Pace—Scrum processes are designed such that the people involved can work at a sustainable pace that they can, in theory, continue indefinitely. 7. Early Delivery of High Value—The Create Prioritized Product Backlog process ensures that the highest value requirements of the customer are satisfied first. 8. Efficient Development Process—Time-boxing and minimizing non-essential work leads to higher efficiency levels. 9. Motivation—The Conduct Daily Standup and Retrospect Sprint processes lead to greater levels of motivation among employees. 10. Faster Problem Resolution—Collaboration and colocation of cross-functional teams lead to faster problem solving. 11. Effective Deliverables—The Create Prioritized Product Backlog process and regular reviews after creating deliverables ensures effective deliverables to the customer. 12. Customer Centric—Emphasis on business value and having a collaborative approach to engage business stakeholders ensures a customer-oriented framework. 13. High Trust Environment—Conduct Daily Standup and Retrospect Sprint processes promote transparency and collaboration, leading to a high-trust work environment ensuring low friction among employees. 14. Collective Ownership—The Commit User Stories process allows team members to take ownership of the project and their work, leading to better quality. 15. High Velocity—A collaborative framework enables highly skilled cross-functional teams to achieve their full potential and high velocity. 16. Innovative Environment—The Retrospect Sprint and Retrospect Release processes create an environment of introspection, learning, and adaptability leading to an innovative and creative work environment. 4 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 1 – INTRODUCTION 1 1.2.1 Scalability of Scrum To be effective, Scrum Teams should ideally have six to ten members. This practice may be the reason for the misconception that the Scrum framework can only be applied to small projects. However, the framework can easily be scaled for effective use in large projects, programs, and portfolios. In situations where the Scrum Team size exceeds ten people, multiple Scrum Teams can be formed to work on the project. The logical approach of the guidelines and principles in this framework can be used to manage projects of any size, spanning geographies and organizations. Large projects may have multiple Scrum Teams working in parallel making it necessary to synchronize and facilitate the flow of information and enhance communication. Large or complex projects are often implemented as part of a program or portfolio. Details on Scaling Scrum for Large Projects are provided in chapter 13. Guidance on Scaling Scrum for the Enterprise is covered in chapter 14. © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 5 1 – INTRODUCTION 1.3 Purpose of the SBOK® Guide The Scrum framework has proven to be the preferred project delivery framework to consistently deliver high business value and improve Returns on Investment. Scrum’s focus on value-driven delivery helps Scrum Teams deliver results as early in the project as possible. The SBOK® Guide was developed as a means to create a necessary guide for organizations and project management practitioners who want to implement Scrum, as well as those already doing so who want to make needed improvements to their processes. It is based on experience drawn from thousands of projects across a variety of organizations and industries. The contributions of many Scrum experts and project management practitioners have been considered in its development. The SBOK® Guide is especially valuable: to Scrum Core Team members including: ◦ Product Owners who want to fully understand the Scrum framework and particularly the customer or stakeholder-related concerns involving business justification, quality, change, and risk aspects associated with Scrum projects; ◦ Scrum Masters who want to learn their specific role in overseeing the application of the Scrum framework to Scrum projects; ◦ Scrum Team members who want to better understand Scrum processes and the associated tools that may be used to create the project’s product or service; as a comprehensive guide for all Scrum practitioners working on Scrum projects in any organization or industry; as a reference source for anyone interacting with the Scrum Core Team, including but not limited to the Portfolio Product Owner, Portfolio Scrum Master, Program Product Owner, Program Scrum Master, Scrum Guidance Body, and business stakeholders (i.e., sponsors, customers, and users); as a handbook for any person who has no prior experience or knowledge of Scrum framework but wants to learn more about the subject. The content of the SBOK® Guide is also helpful for individuals preparing to write the following SCRUMstudy™ certification exams: Scrum Developer Certified (SDC®) Scrum Master Certified (SMC®) Scaled Scrum Master Certified (SSMC™) SCRUMstudy Agile Master Certified (SAMC™) Scrum Product Owner Certified (SPOC®) Scaled Scrum Product Owner Certified (SSPOC™) Expert Scrum Master Certified (ESMC™) 6 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 1 – INTRODUCTION 1 1.4 Framework of the SBOK® Guide The SBOK® Guide is broadly divided into the following three areas: 1. Principles covered in chapter 2, expand on the six principles which form the foundation on which Scrum is based—Empirical Process Control, Self-organization, Collaboration, Value-based Prioritization, Time- boxing, and Iterative Development. 2. Aspects covered in chapters 3 through 7, describe the five aspects that are important considerations for all Scrum projects—Organization, Business Justification, Quality, Change, and Risk. 3. Processes covered in chapters 8 through 12, include the nineteen fundamental Scrum processes and their associated inputs, tools, and outputs. Chapter 13 covers the additional inputs, tools, and outputs needed for scaling Scrum for large projects, whereas chapter 14 covers the additional processes needed for scaling Scrum for the enterprise. Figure 1-2 illustrates the SBOK® Guide framework and how principles, aspects, and processes interact with each other—all three are equally important in the understanding and application of the Scrum framework. Figure 1-2: SBOK® Guide Framework © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 7 1 – INTRODUCTION 1.4.1 How to Use the SBOK® Guide? The SBOK® Guide can be used as a reference and knowledge guide by both experienced Scrum and other product and service development practitioners, as well as by persons with no prior experience or knowledge of Scrum or project management approach. The contents are organized for easy reference by the three Scrum Core Team roles: Product Owner, Scrum Master, and Scrum Team. The chapters covering the six Scrum principles (chapter 2) and five Scrum aspects (chapter 3 through 7) include a Roles Guide. This guide provides direction regarding the relevance of each section in the chapter to the Scrum Core Team roles. In order to facilitate the best application of the Scrum framework, the SBOK® Guide has clearly differentiated mandatory inputs, tools, and outputs, from non-mandatory or optional ones. Inputs, tools, and outputs denoted by asterisks (*) are mandatory, or considered critical for project success, while others with no asterisks are optional. It is recommended that those being introduced to Scrum focus primarily on the mandatory inputs, tools, and outputs; while more experienced practitioners should read the entire process chapters to benefit from the optional best practice inputs, tools, and outputs suggested. Scrum is a framework that is not meant to be prescriptive, which means there is room for flexibility in its application. All the fundamental Scrum processes detailed in the SBOK® Guide (chapters 8 through 12) are required for every Scrum project but should be applied based on the specific needs of the organization, project, product, and/or team. Additional inputs, tools, and outputs would apply when Scaling Scrum for Large Projects (chapter 13) and additional processes would apply when Scaling Scrum for the Enterprise (chapter 14). 8 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 1 – INTRODUCTION 1 1.4.2 Scrum Principles Scrum principles are the core guidelines for applying the Scrum framework and should mandatorily be used in all Scrum projects. The six Scrum principles presented in chapter 2 are: 1. Empirical Process Control 2. Self-organization 3. Collaboration 4. Value-based Prioritization 5. Time-boxing 6. Iterative Development Figure 1-3 illustrates the six Scrum principles. Figure 1-3: Scrum Principles © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 9 1 – INTRODUCTION Scrum principles can be applied to any type of project in any organization and must be adhered to in order to ensure effective implementation of the Scrum framework. Scrum Principles are non-negotiable and must be applied as specified in the SBOK® Guide. Keeping the principles intact and using them appropriately instills confidence in the Scrum framework with regard to attaining the objectives of the project. The Scrum aspects and processes, however, can be modified to meet the requirements of the project or the organization. 1. Empirical Process Control—This principle emphasizes the core philosophy of Scrum based on the three main ideas of transparency, inspection, and adaptation. Empirical process control aids learning through experimentation, especially when the problem is not well defined or when there are no clear solutions. 2. Self-organization—This principle focuses on today’s workers, who deliver significantly greater value when self-organized, and this results in better team buy-in and shared ownership; and an innovative and creative environment which is more conducive for growth. 3. Collaboration—This principle focuses on the three core dimensions related to collaborative work: awareness, articulation, and appropriation. It also advocates project delivery as a shared value-creation process with teams working and interacting together, as well as with the customer and other business stakeholders, to deliver the greatest value. 4. Value-based Prioritization—This principle highlights the focus of Scrum to deliver maximum business value, from early in the project and continuing throughout. 5. Time-boxing—This principle describes how time is considered a limiting constraint in Scrum and used to help effectively manage project planning and execution. Time-boxed elements in Scrum include Sprints, Daily Standup Meetings, Sprint Planning Meetings, Sprint Review Meetings, and Retrospect Sprint Meetings. 6. Iterative Development—This principle defines iterative development and emphasizes how to better manage changes and build products that satisfy customer needs. It also delineates the Product Owner’s and organization’s responsibilities related to iterative development. 10 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 1 – INTRODUCTION 1 1.4.3 Scrum Aspects The Scrum aspects must be addressed and managed throughout a Scrum project. The five Scrum aspects presented in chapter 3 through 7 are: 1.4.3.1 Organization Understanding defined roles and responsibilities in a Scrum project is very important for ensuring the successful implementation of Scrum. Scrum roles fall into two broad categories: 1. Core Roles—Core roles are those roles which are mandatorily required for producing the project’s product or service. Individuals who are assigned core roles are fully committed to the project and are ultimately responsible for the success of each sprint and that of the project as a whole. Core roles comprise the Scrum Core Team members, which include: The Product Owner is the person responsible for achieving maximum business value for the project. He or she is also responsible for articulating customer requirements and maintaining business justification for the project. The Product Owner represents the Voice of the Customer. The Scrum Master is a facilitator who ensures that the Scrum Team is provided with an environment conducive to completing the project successfully. The Scrum Master guides, facilitates, and teaches Scrum practices to everyone involved in the project; clears impediments for the team; and ensures that Scrum processes are being followed. The Scrum Team is the group or team of people who are responsible for understanding the requirements specified by the Product Owner and creating the deliverables of the project. 2. Non-core Roles—Non-core roles are those roles that are not mandatorily required for the Scrum project. They may include team members who are interested in the project but have no formal role in the project team. These individuals may interface with the team but may not be responsible for the success of the project. The non-core roles should be taken into account in any Scrum project. Non-core roles include the following: Business Stakeholder(s), which is a collective term that includes customers, users, and sponsors who frequently interface with the Scrum Core Team and also influence the project throughout the project’s development. Most importantly, it is for the business stakeholders that the project produces the collaborative benefits. Business stakeholders are a subset of all stakeholders in a Scrum project - stakeholders include all individuals and groups affected by the Scrum project, both within and outside the organization (e.g., all core and non-core roles, vendors, internal groups, experts, and so on). © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 11 1 – INTRODUCTION Scrum Guidance Body (SGB) is an optional role, which generally consists of a set of documents and/or a group of experts who are typically involved with defining objectives related to quality, government regulations, security, and other key organizational parameters. The SGB guides the work carried out by the Product Owner, Scrum Master, and Scrum Team. Vendors, include external individuals or organizations that provide products and/or services that are not within the core competencies of the project organization. Figure 1-4 illustrates the Scrum Organization structure. Figure 1-4: Organization in Scrum The Organization aspect of Scrum also addresses the team structure requirements to implement Scrum in large projects, programs, and portfolios. 1.4.3.2 Business Justification It is important for an organization to perform a proper business assessment prior to starting any project. This helps key decision makers understand the business need for a change or for a new product or service, the justification for moving forward with a project, and its viability. Business justification in Scrum is based on the concept of value-driven delivery. One of the key characteristics of any project is the uncertainty of results or outcomes. It is impossible to guarantee project success at completion, irrespective of the size or complexity of a project. Considering this uncertainty of achieving success, Scrum attempts to start delivering results as early in the project as possible. 12 © 2022 SCRUMstudy™. A Guide to the Scrum Body of Knowledge (SBOK® Guide) 1 – INTRODUCTION 1 This early delivery of results, and thereby value, provides an opportunity for reinvestment and proves the worth of the project to interested business stakeholders. Scrum’s adaptability allows the project’s objectives and processes to change if its business justification changes. It is important to note that although the Product Owner is primarily responsible for business justification, other team members contribute significantly. 1.4.3.3 Quality In Scrum, quality is defined as the ability of the completed product or deliverables to meet the Acceptance Criteria and achieve the business value expected by the customer. To ensure a project meets quality requirements, Scrum adopts an approach of continuous improvement whereby the team learns from experience and stakeholder engagement to constantly keep the Prioritized Product Backlog updated with any changes in requirements. The Prioritized Product Backlog is simply never complete until the closure or termination of the project. Any changes to the requirements reflect changes in the internal and external business environment and allow the team to continually work and adapt to

Scrum Body of Knowledge (SBOK® Guide) 4th Edition PDF

Document Details

Tags

Related

Summary

Full Transcript

Upgrade to continue