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)
Section 1: The Scrum Framework
Section 2: Scrum in Action
Section 3: The PSM Certification

Preparing for the first Sprint

In Scrum, every Sprint is treated exactly the same as any other Sprint. It is a time-boxed event in which the Scrum Team delivers value by creating an increment of potentially releasable software. No Sprint is special in that respect. Some teams, however, especially teams inexperienced in Scrum, tend to treat the first Sprint a bit differently than the others.


Avoid the Scrum 0 anti-pattern. A Scrum 0 is a Scrum dedicated to setting up infrastructure, creating a design or architecture, initial backlog refinements, and other preparatory work. Scrum 0 is just a set of preliminary activities and does not produce an increment of potentially releasable software. Sprints designed not to produce a Done increment undermine the Scrum principles and should not be pursued.

A common misconception about the first Sprint is that because it's not expected to produce user-side functionality, then it's a special Sprint and can be used as a repository...