SN-Logo NewSN-Logo NewSN-Logo NewSN-Logo New
  • Scrum Courses
  • Agile Keynotes
  • Agile Books & Tools
  • Blog
  • About
  • Contact
0

CHF0.00

✕
/ch/open Event: Scrum, Success and Quality
18-04-2008
Rational Scrum?
22-04-2008

Handling a Good Sprint Gone Bad

Published by Peter Stevens on 21-04-2008
Categories
  • delay
  • planning
  • product owner
  • scrum
  • scrummaster
  • sprint
  • sprint contract
Tags

I was recently confronted with a sprint dilemma: At the start the sprint, the team committed to delivering a certain amount of functionality within the defined time period at the defined level of quality. Sometimes bad things happen. In this case, there was a heavy support load — getting the previous sprint’s functionality formally accepted. This was preventing the team from working on the goals for the current sprint. The Scrum-Master recognizes this in a timely fashion. What happens next?

Certainly the Scrum-Master should give early warning to the Product Owner. But what alternatives can he or should he offer? Theoretically one could:

  1. Increase the staff
  2. “Do what it takes” to finish the sprint
  3. Prolong the sprint
  4. Finish the sprint at the date planned, completing less work than committed.

The right answer is almost always 4) Finish the Sprint on the date planned. But why?

Options one and three both break the sprint contract and raise the cost of the Sprint. Increasing the staff raises the issue of training and integrating the new staff. Brooks taught us 30 years ago that adding people late in a late project makes the project later. So it’s not really an option.

“Doing what it takes” usually means compromising on quality to achieve quantity, often accompanied by overtime. It also breaks the contract, but in a much subtler fashion. The increase in “productivity” is accompanied by an increase in defects, which are much more expensive to identify and correct later in the release, deployment or operational phases than if they were caught in development. Overtime is not only not sustainable, it also compounds the effects of working under pressure. So it might be an alternative in some cases, but the side effects are probably not what you want.

Prolonging the Sprint is tempting. The quality is maintained, but there are other serious disadvantages.

  1. It is an administrative nightmare – all the sprint meetings which occured like clockwork have to be rescheduled, with the accompanying potential for scheduling conflicts
  2. It falsifies the velocity – it looks like the team is making better progress (as measured in points per sprint) then it really is
  3. It deprives the Product Owner of the chance to inspect progress and adjust priorities until the functionality is completed
  4. It discourages an examination of the issues behind the delay

This last issue is actually true of all the options (except for finishing the sprint as planned). If the project is not going as planned, it is important to recognize the fact and ask the “why?” questions to determine the causes.In our case, there are some serious problems getting to “done” (and I am starting to have real reservations about using scrum within a waterfall. It’s better waterfall, but it’s still a waterfall!)

Only by asking way can we determine and address the real issues dragging down the team’s productivity.

So, take your lumps, get a true picture of the velocity and start asking the right questions to remove impediments, increase staff availability, solve the problems or fix whatever problems the answers to the those questions reveal.

BTW – there are few cases where prolonging the sprint might make sense. Well, I’ve prolonged two sprints. Once was legitamate, once was debatable. But that’s a topic for another post….

Share
0
Peter Stevens
Peter Stevens

Related posts

05-06-2019

The Sprint Contract


Read more
05-02-2019

Is your agile transition building a train but ignoring the track?


Read more
31-03-2018

Scrum is simple to understand but difficult to master(?)


Read more

2 Comments

  1. Corey Jackson says:
    22-04-2008 at 20:02

    I think if you find yourself taking out a majority of the sprint, it means your planning was not successful and you should stop the sprint, and start over with a fresh planning session. Otherwise, I agree with you, the only option is to take the work back onto the backlog to be done in a future sprint.

  2. Peter says:
    22-04-2008 at 21:10

    Hi Corey,

    Hmm, I hadn’t thought of breaking off the sprint. It’s certainly a legitimate alternative though.

    Cancelling the sprint is fairly violent act. I had always thought of it as a last resort item when the team has no chance of completing the planned work (more for conceptual than operational reasons though).

    Cancellation forces an analysis of the issues earlier than if the team waited until the end of the sprint. It carries the same administrative overhead of prolonging the sprint (i.e. potentially rescheduling all appointments — my calendar is relatively flexible, but getting a meeting room can be a challenge!)

    A good point! Thank you.

Learn more about Agile

  • Certified Scrum Product Owner | Face-2-Face | English | 230413-CP2
    in Zürich
    April 13, 2023 -
    April 14, 2023
    Register Now
  •  

  • Certified Scrum Master | Face-2-Face | English | May 22-23, 2023
    in Zürich
    May 22, 2023 -
    May 23, 2023
    Register Now
  •  

  • Certified Scrum Product Owner | Face-2-Face | English | Jun 15-16, 2023
    in Zürich
    June 15, 2023 -
    June 16, 2023
    Register Now
  •  

  • Certified Scrum Master | Face-2-Face | English | Jul 06-07, 2023
    in Zürich
    July 06, 2023 -
    July 07, 2023
    Register Now
  •  

High Performing Teams

  • Get Stuff Done
  • Get Right Stuff Done
  • Create Alignment
  • Leadership

Free Resources

  • Personal Agility Institute
  • Impressum
  • Terms and Conditions
  • Privacy Policy

Upcoming courses

  • Certified Scrum Product Owner | Face-2-Face | English | 230413-CP2 in Zürich
    April 13, 2023 -
    April 14, 2023
    Register Now
  • Certified Scrum Master | Face-2-Face | English | May 22-23, 2023 in Zürich
    May 22, 2023 -
    May 23, 2023
    Register Now
© 2020 Saat Network GmbH. All Rights Reserved.
    0

    CHF0.00

      ✕

      Login

      Lost your password?

      We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
      Read more about our Privacy Policy
      Cookie SettingsAccept All
      Manage consent

      Privacy Overview

      This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
      Necessary
      Always Enabled
      Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
      CookieDurationDescription
      cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
      cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
      cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
      cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
      cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
      cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
      viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
      Functional
      Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
      CookieDurationDescription
      mailchimp_landing_site1 monthThe cookie is set by MailChimp to record which page the user first visited.
      Performance
      Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
      Analytics
      Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
      CookieDurationDescription
      CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
      _ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
      _gat_gtag_UA_42152348_11 minuteSet by Google to distinguish users.
      _gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
      _gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
      Advertisement
      Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
      CookieDurationDescription
      NID6 monthsNID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.
      test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
      VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
      YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
      yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
      yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
      Others
      Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
      CookieDurationDescription
      COMPASS1 hourNo description
      cookies.jssessionNo description available.
      S1 hourNo description available.
      SAVE & ACCEPT
      Powered by CookieYes Logo