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 acquainted with the Developers

The Developers are a cross-functional, self-managing group that is responsible for converting Sprint Backlog items into working, releasable code. In this section, we'll learn about the Developer responsibilities, the things outside their realm, and we'll answer some commonly asked questions about this role.

The Developers are self-managing

Self-management means that they are responsible for making decisions about the work they are doing and about the way they function. There is no hierarchy among the Developers. No team member can tell another team member what to do. Disagreements must be resolved with discussions and consensus-forming. Traditionally, developers have been structured according to seniority and skillsets. The most senior developers would be making the decisions. Work would be split according to areas of expertise, for instance, the frontend expert would work on the UI, the testing expert would do the testing, and...