Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Professional Scrum Master Guide

You're reading from   The Professional Scrum Master Guide The unofficial guide to Scrum with real-world projects

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781800205567
Length 174 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Fred Heath Fred Heath
Author Profile Icon Fred Heath
Fred Heath
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1:The Scrum Framework
2. Chapter 1: Introduction to Scrum FREE CHAPTER 3. Chapter 2: Scrum Theory and Principles 4. Chapter 3: The Scrum Team 5. Chapter 4: Scrum Events 6. Chapter 5: Scrum Artifacts 7. Section 2:Scrum in Action
8. Chapter 6: Planning and Estimating with Scrum 9. Chapter 7: The Sprint Journey 10. Chapter 8: Facets of Scrum 11. Section 3:The PSM Certification
12. Chapter 9: Preparing for the PSM I Assessment 13. Assessments 14. Other Books You May Enjoy 15. Index

Managing defects

Defects are an unavoidable part of software development. No one is perfect and no methodology is foolproof; as a result, every Scrum Team will deal with defects at some time during product development. Scrum provides plenty of opportunities for inspection and adaptation, thereby helping to take steps to minimize the occurrence and impact of defects. The way we deal with defects in Scrum depends largely on when the defects are discovered:

  • In-Sprint defects are defects discovered within the current Sprint.
  • Out-of-Sprint defects are discovered in previously released increments.

Before delving into these two scenarios, let's talk a bit more about defects.

Knowing how to triage defects

A defect is a discrepancy between the software's actual and expected behavior. A defect is usually caused by a coding or design error (a bug) or by a misunderstanding of the user requirements. When the Scrum Team becomes aware of a defect, they should ensure...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image