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

What to do when the Sprint Goal is not achieved

Occasionally, the team will realize they are not able to reach the Sprint Goal by the end of the Sprint or that the Goal hasn't been achieved at the end of Sprint. This usually happens because of two reasons:

  • The Developers haven't been able to deliver all the Sprint Backlog items.
  • The increment is not in a usable state.

Let's examine both causes, starting with the first one. When one or more Sprint Backlog items have not been finished by the end of the Sprint, this is sometimes due to extraneous circumstances (for example, a Developer has fallen ill). Most often, however, it happens because the Developers did not estimate the items correctly. Unfinished items by the Sprint's end are not uncommon, although this tends to happen more often during the early Sprints, when the team hasn't yet established its internal rhythm and delivery cadence.

Important note

Some teams and organizations refer...