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

Producing a Product Increment

A Product Increment is the working software that's created during the Sprint. It is a demonstrable stepping stone toward the Product Goal. Each increment is cumulative to previous increments and thoroughly verified, ensuring that all the Increments work together. An Increment must do the following:

  • Be usable – a usable increment is a piece of software that can be used by stakeholders to enact some functionality required and related to the Sprint Goal.
  • Meet the Definition of Done, as discussed in the Making a commitment – Definition of Done section.

An Increment is created the moment a Sprint Backlog item meets the Definition of Done.

Important note

Multiple Increments may be created within a Sprint. The sum of all Sprint Increments is presented at the Sprint Review so that all the work can be inspected. However, an Increment may be delivered to stakeholders before the end of the Sprint. Value, in the shape of...