Skip to main content

Hardening Sprint?

Last post 04:28 pm October 4, 2022 by Mohan Peters
8 replies
02:59 am December 9, 2016

What does the following statement mean?

It is normal to have a “hardening” Sprint to remove all technical debt and prepare the Product for upcoming release.

Thanks

Robb


03:20 am December 9, 2016


Where did you read this?

Every Sprint should deliver a potentially releasable product increment. If team needs a separate Sprint before the product release then we haven't understood the concept of Scrum and Sprint.

I don't mind keeping some technical debt but will prefer re-paying it on regular basis. We should not accumulate it so much that we need a dedicated Sprint for it.


06:53 am December 9, 2016

It's one question in the simulation exam by Mikhail Lapshin (and I guess one of them on Management Plaza too) and of course the answer is no, there is no hardening Sprint in SCRUM.


01:01 am December 10, 2016

But what do "hardening sprint" and "technical debt" mean?


05:51 pm December 10, 2016

> But what do "hardening sprint" and "technical debt" mean?

Technical debt refers to the long-term consequences of poor design decisions.

- Can you see why the metaphor of "debt" is used to describe this?
- If technical debt is allowed to accumulate over multiple sprints, can you see why a "special" sprint (e.g. a so-called "hardening sprint") might be thought necessary in order to remedy the poor decisions that were made?
- Each sprint should produce an increment of release quality. The decisions made should be fit for purpose and technical debt should thus be limited. Can you see how "hardening sprints" might encourage significant technical debt to be incurred in the first place?


06:44 pm December 10, 2016

Very well explained @Ian.

IS it safe to say that some examples of technical debt are the following:

1. Poor Architecture that leads to performance issues
2. Selection of incorrect technology/ language?
3. Not using best development practices?
4. etc
5. etc

Robb


07:37 pm December 10, 2016

Yes


09:14 pm December 10, 2016

Thank you.


12:38 pm October 4, 2022

FALSE. It is not normal. Scrum Teams deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. So, there is nothing to prepare. Each increment contains only “Done” functionality that could be released immediately.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.