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

Identifying a Scrum Team

The Scrum Team is a small group of people who work together to deliver a software solution or product to a client. The Scrum Team consists of three specific roles, a Product Owner, a Scrum Master, and Developers. The Scrum Team is a cohesive unit of professionals focused on delivering a product. The team is responsible for performing any and all product-related activities needed in order to achieve the Product Goal. They are empowered by the organization to manage their own work.

Scrum Teams differ from traditional software teams. Before Agile became a thing, software project teams would consist of a number of software developers working within well-defined boundaries and within a strict hierarchy of duties and responsibilities. Traditionally, business analysts would communicate with the stakeholder and capture requirements. These would then be passed to the developers. The software system's architecture and high-level design would be established in...