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)
1
Section 1: The Scrum Framework
7
Section 2: Scrum in Action
11
Section 3: The PSM Certification

The foundation of Scrum

Scrum is founded on an empirical process theory of knowledge, or empiricism. Empiricism is derived from the Greek word Empeiria, that is, experience. It is the theory that all knowledge should be based on, and justified by, practical experience. Learning is based on our observations, perception, and experience gained from practice. Empiricism is often contrasted with rationalism, another theory of knowledge that regards reason as the chief source and standard of knowledge. In other words, rationalism determines truth based on the adoption of and adherence to intellectual templates and standards. Empiricism, on the other hand, determines truth based on the results of experimentation, evaluation of evidence, and its alignment with a perceived useful outcome.

At this point, you're probably asking yourself What has this philosophical stuff got to do with software development? Allow me to use a simple thought experiment:

Alice is managing a widget factory...