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

MIME-Version: 1.0
Content-Type: multipart/alternative;

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.
Sent: 3/19/2013 5:36 PM
Subject: RE: Hardening Sprints: good or bad? [00000307:00001125]

11:33 am March 29, 2013


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

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