Skip to main content

RE: Hardening Sprints: good or bad?

Last post 11:49 am March 29, 2013 by Ryan Cromwell
2 replies
08:45 pm March 19, 2013

[00000307:00001125]
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=--boundary_119_1d81fb6a-3baf-4b87-a802-01c1ee90b758

----boundary_119_1d81fb6a-3baf-4b87-a802-01c1ee90b758
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

It may be a step along the path of improvement, but it's not plannable
in the sense that you can understand the extent or time involved.

Allowing unintegrated work to leave a sprint is a risk, plain and
simple. Avoid the assumptions that come with that decision at all costs.
From: ScrumForum@scrum.org
Sent: 3/19/2013 5:36 PM
To: ryan@echelontouch.com
Subject: RE: Hardening Sprints: good or bad? [00000307:00001125]


11:33 am March 29, 2013

Ryan,

the danger of Hardening Sprints are that you accecpt to build technical dept during the "normal" Sprints. Because the complete Scrum Team might say we have enaugh time in the Hardening Sprint to fix that.

Sometimes you need Hardening Sprints (An Example might be: the Test Server are only available to a certain timeframe (you see this in SAP development very often)) but I don't like them anyway and I recommend not doing them as long as it is possible.

best JP

best JP


11:49 am March 29, 2013

@Jean. Mine was a reply to this thread https://www.scrum.org/Forums/aft/307

The system didn't deal well with the email reply.


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.