Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
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

What to do when the Sprint Goal is not achieved

Occasionally, the team will realize they are not able to reach the Sprint Goal by the end of the Sprint or that the Goal hasn't been achieved at the end of Sprint. This usually happens because of two reasons:

  • The Developers haven't been able to deliver all the Sprint Backlog items.
  • The increment is not in a usable state.

Let's examine both causes, starting with the first one. When one or more Sprint Backlog items have not been finished by the end of the Sprint, this is sometimes due to extraneous circumstances (for example, a Developer has fallen ill). Most often, however, it happens because the Developers did not estimate the items correctly. Unfinished items by the Sprint's end are not uncommon, although this tends to happen more often during the early Sprints, when the team hasn't yet established its internal rhythm and delivery cadence.

Important note

Some teams and organizations refer...

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