Book Image

The Professional Scrum Master (PSM I) Guide

By : Fred Heath
Book Image

The Professional Scrum Master (PSM I) Guide

By: Fred Heath

Overview of this book

Ever wondered why you’d use Scrum over other process frameworks? Or what makes Agile just so agile? Or why you should bother with the PSM certification? This book has you covered. The Professional Scrum Master (PSM I) Guide is a comprehensive tutorial that will not only introduce you to the basics of Scrum, but build you up to be ready to pass your PSM I exam first time round. Where other books avoid detail, this guide provides you with detailed practical examples to take you from being an apprentice to becoming a master. Assuming you’re a total beginner, this book will introduce you to Scrum methodologies with detailed use cases, teaching you the secrets of Scrum in such a way that you’ll be well-equipped for the PSM I exam. This book demonstrates the real-world applications of Scrum in a variety of scenarios, all with practical examples. You’ll understand why the structure of your Scrum team matters, what you can achieve with properly planned sprints, and how to create and manage sprint and product backlogs. The chapters are regularly concluded with quizzes relevant to the exam, reinforcing the values you learn on your journey. Finally, it concludes with some exam preparation and myth-dispelling to make sure you have an edge when it comes to earning your certificate. This is a guide that’ll ensure you won’t fall behind in an ever increasingly agile world.
Table of Contents (15 chapters)
1
Section 1: The Scrum Framework
7
Section 2: Scrum in Action
11
Section 3: The PSM Certification

Creating and managing the Sprint Backlog

The Sprint Backlog is simply a list of Product Backlog items that have been selected for the Sprint, along with the plan for delivering them and accomplishing the Sprint Goal. While the Product Owner is responsible for which items go in the Product Backlog, the developers are solely accountable for which items go into the Sprint Backlog. The Product Owner will make suggestions as to which items should go in the Sprint Backlog, but the developers will decide based on their estimation of the work needed for each item and their own capacity to deliver work within the Sprint. Often, if the Product Owner is very insistent on including certain items in the Sprint, the developers may exclude other items of equal size or complexity from the Sprint Backlog so that they can accommodate the high-priority item. Placing and removing items from the Sprint Backlog must always be driven by the Sprint Goal's imperative. Let's discuss how that happens...