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

Getting ready to Sprint

In Chapter 1, Introduction to Scrum, in the The value of an iterative and incremental approach section, we examined the concept of developing software in short iterations, where each iteration builds upon the working software provided by its predecessors. We call such an iteration a Sprint. A Sprint is a container event, as all the other Scrum Events take place within the duration and context of a Sprint. The ultimate purpose of the Sprint is to have the Developers produce an Increment. An Increment is a piece of working and potentially shippable software that leverages previous Increments. We'll talk more about what this means in a subsequent section. However, the Sprint also provides space and time for all the other Scrum Events, where the whole Scrum Team comes together to plan, inspect, and adapt. A good way to visualize the Sprint is as a cyclical process, demarcated by other events, as illustrated in the following diagram:

Figure 4.1 – The Sprint as an event container