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

Scaling Scrum

Scrum, as we've already discussed, is all about working in small, focused teams off a single Product Backlog. It's the most efficient and productive way of delivering software. Sometimes, however, the product that needs to be delivered is so large and complex that having one small team is not adequate.

This presents the following conundrum: Scrum prescribes a small team of up to eight developers, one Scrum Master, and one Product Owner. How can we have dozens of developers working on the product, all using Scrum? The solution to this is actually simple: we can partition the product work in separate but related workstreams, or product components, and create a Scrum Team to work on delivering each component. Each team will have its own product backlog and will work like any independent Scrum Team does. The teams will have to regularly coordinate to ensure they don't get in each other's way and that they all work towards the same goal.

This approach...