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

Keeping on the right track with the Daily Scrum

The Daily Scrum is a daily occurring event held at the same time and place every day, usually at the start of the day. The Daily Scrum is solely for the benefit of the Developers. The Scrum Master and Product Owner may attend the event, but only as observers. They are not allowed to disrupt or participate. The Scrum Master may want to be present to ensure the meeting does not exceed its maximum duration (time-box) of 15 minutes and that it is not disrupted by external people.

The objective of the event is for the Developers to inspect the work done since the last Daily Scrum and plan the work for the next 24 hours. The structure of the event and the way it's conducted is entirely up to the Developers. A common structure is that each team member gives a brief summary on three things:

  • What they've been working on since the last Daily Scrum
  • What they plan to work on in the next 24 hours
  • Any potential impediments...