Controversy of Hardening Sprints: The Good, Bad and Downright Ugly

Controversy of Hardening Sprints: The Good, Bad and Downright Ugly

You are currently viewing Controversy of Hardening Sprints: The Good, Bad and Downright Ugly

Controversy of Hardening Sprints: The Good, Bad and Downright Ugly. There has been much controversy over whether hardening sprints are necessary or not.
Agile experts, Bob Galen and Shaun Bradshaw, shed light to some of the pros and cons of hardening sprints based on what they have encountered in their real-life coaching experiences.
Furthermore, Bob and Shaun address many variations of these sort of sprints, such as:

  • Stabilization Sprint
  • Release Readiness Sprint
  • Spring Cleaning Sprint
  • Sprint #0
    There has been much controversy over whether hardening sprints are necessary or not.
    See our agile experts discuss the pros & cons of hardening sprints, and learn why a co-founder of agile once threatened to revoke Bob Galen’s agile badge.
    More specifically in regulatory and external vendor contexts as well as contexts where there’s a hardware integration component.
    You’re creating a time to integrate and collaborate with others outside your organization and for that reason it makes for a good application of the agile principles.
    It helps bring other parts of the organization on board with this notion of agile philosophy or values.
    Hardening ultimately can be used to meet people where they are, instead of forcing an organization to do a potential product increment every 2 weeks in which you have to deploy to the customer.
  • Ask yourself, can you do these release trains?
  • Can you cue up functionality in a meaningful way so that it has enough value to release?
  • And last, with an agile mindset, can you qualify that in a hardening sprint?

Leave a Reply