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

Managing the art of estimation

Estimation is an essential part of software development and project management. Some people call it a necessary evil. I don't know about the evil part, but I certainly agree with the necessary part. The Scrum Guide doesn't say anything about how to estimate the items in our Product Backlog. However, the industry has adopted some techniques that we will discuss in the following sections. But first, let's examine why estimation is so important. Having estimates allows the Scrum Team to do the following:

  • Prioritize items in the Product Backlog: This happens as part of the Backlog refinement process, which we talked about in Chapter 5, Scrum Artifacts. There are many ways to prioritize the items in the Product Backlog, and effort or size estimates are one way to do so.
  • Choose which items to place in the Sprint Backlog: This happens during the Sprint planning event, as described in Chapter 4, Scrum Events. If we can't estimate...