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

Managing technical debt

Technical debt is a software development concept. It reflects the implied cost of additional rework caused by choosing a quick and restrictive solution instead of a more comprehensive but slower one.

Technical debt is generally an issue that transcends Scrum and applies to any type of software development process or methodology. However, it is particularly prominent in Scrum due to its application of short, focused development iterations.

How is technical debt created?

Let's consider a simple example: Bob, a developer, is working on a task that requires the storing of customer and product details in a database. Bob creates a single database table and inputs the data for both customers and products in it. This solution works and will continue to work for as long as the number of customers and products is small.

However, as this number increases with time, the maintenance of that table will become more difficult, data duplication will occur, and...