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

Canceling the Sprint

A Sprint may end in one of two ways. The vast majority of times, the Team will have worked throughout the Sprint's duration and will have ended up achieving, not achieving, or partly achieving the Sprint Goal. We have already discussed how to deal with these eventualities in the previous sections of this chapter. However, there are some very rare occasions where the team won't get to the end of the Sprint, as the Sprint gets canceled. Let's examine this more closely.

Canceling a Sprint is a very rare phenomenon. It generally happens when a new situation or extraordinary circumstances shift the team's commitment and focus. A Sprint must not get canceled if the Scrum Team simply decides that it cannot complete the work, or that it cannot reach the Sprint Goal. Frequently canceled Sprints should ring alarm bells. They may be a sign that the Scrum Team is lacking focus and commitment, the product is lacking a vision, or the organization does...