Reader small image

You're reading from  The Professional Scrum Master Guide

Product typeBook
Published inJul 2021
PublisherPackt
ISBN-139781800205567
Edition1st Edition
Concepts
Right arrow
Author (1)
Fred Heath
Fred Heath
author image
Fred Heath

Fred Heath is a freelance developer and consultant based in Wales, UK. Over the last 20 years, he's worked at every stage of the software development life cycle using a variety of languages and platforms and ended up falling in love with Ruby and its ecosystem. Fred enjoys solving tricky problems, FOSS, meta programming, Behavior-Driven Development, and Agile processes. He also frequently writes online and speaks at conferences about Ruby, software development, and best practices. Fred is always happy to hear from you and chat about Ruby and Rails on Twitter.
Read more about Fred Heath

Right arrow

Canceling the Sprint

A Sprint may end in one of two ways. The vast majority of times, the Team will have worked throughout the Sprint's duration and will have ended up achieving, not achieving, or partly achieving the Sprint Goal. We have already discussed how to deal with these eventualities in the previous sections of this chapter. However, there are some very rare occasions where the team won't get to the end of the Sprint, as the Sprint gets canceled. Let's examine this more closely.

Canceling a Sprint is a very rare phenomenon. It generally happens when a new situation or extraordinary circumstances shift the team's commitment and focus. A Sprint must not get canceled if the Scrum Team simply decides that it cannot complete the work, or that it cannot reach the Sprint Goal. Frequently canceled Sprints should ring alarm bells. They may be a sign that the Scrum Team is lacking focus and commitment, the product is lacking a vision, or the organization does...

lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
The Professional Scrum Master Guide
Published in: Jul 2021Publisher: PacktISBN-13: 9781800205567

Author (1)

author image
Fred Heath

Fred Heath is a freelance developer and consultant based in Wales, UK. Over the last 20 years, he's worked at every stage of the software development life cycle using a variety of languages and platforms and ended up falling in love with Ruby and its ecosystem. Fred enjoys solving tricky problems, FOSS, meta programming, Behavior-Driven Development, and Agile processes. He also frequently writes online and speaks at conferences about Ruby, software development, and best practices. Fred is always happy to hear from you and chat about Ruby and Rails on Twitter.
Read more about Fred Heath