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

Managing defects

Defects are an unavoidable part of software development. No one is perfect and no methodology is foolproof; as a result, every Scrum Team will deal with defects at some time during product development. Scrum provides plenty of opportunities for inspection and adaptation, thereby helping to take steps to minimize the occurrence and impact of defects. The way we deal with defects in Scrum depends largely on when the defects are discovered:

  • In-Sprint defects are defects discovered within the current Sprint.
  • Out-of-Sprint defects are discovered in previously released increments.

Before delving into these two scenarios, let's talk a bit more about defects.

Knowing how to triage defects

A defect is a discrepancy between the software's actual and expected behavior. A defect is usually caused by a coding or design error (a bug) or by a misunderstanding of the user requirements. When the Scrum Team becomes aware of a defect, they should ensure...