One of the heatedly discussed aspects of SAFe(Scaled Agile Framework) is the specified HIP sprints. HIP stands for Hardening, Innovation and Planning. In earlier versions of SAFe these were called Hardening Sprints.

In Scrum implementations, we usually view the need for a stabilization phase with a fair amount of suspicion – it almost always goes hand-in-hand with a poor code base and suboptimal development practices. That’s why these Hardening Sprints have caused quite a sharp reaction in the Scrum community (also from me).

Now I’ve found that this criticism has at least been put into perspective – and for me, that’s not just because of the renaming

  • In a large development, the individual Scrum team must guarantee a higher planning reliability than in an autonomous environment. You have to buy planning security with a buffer. This is the first application for the HIP Sprint.
  • All Scrum teams are involved in a rough planning of the cadence of 3-4 months, defining „objectives“, i.e. goals they consider achievable and „stretch objectives“, i.e. things that will only be achieved under optimal conditions. The Scrum teams prepare for this big joint planning meeting, that is the second goal of the HIP Sprint
  • Third, the HIP Sprint is the period during which experiments, learning activities, and the like are conducted – across: Innovation. When the team has completed the other two activities, this is the built-in reward for effective and well-planned work.

Going back to pure Scrum, one thing remains the same: the need for stabilization sprints indicates weaknesses in the previous sprints: the result of a sprint should be software of deliverable quality.

However, special sprints have always been discussed (and sometimes hotly disputed) in Scrum as well:

  • Sprint 0 for initial planning, possibly also for calibrating the expected velocity.
  • A product owner is expected to compile the backlog items in such a way that they can be used to designate nameable increments for the sprints – if you look at it closely, these are also specialized sprints.
Twitter
LinkedIn

HIP Sprints with SAFe and specialized Sprints with Scrum

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert

On Key

Related Posts

Thoughts about strategy

… Vision is different from purpose. A purpose is similar to a direction, a general course. A vision is a specific goal, a picture of

Gedanken über Strategie

… Vision ist etwas anderes als Zweck. Ein Zweck ist ähnlich wie eine Richtung, ein allgemeiner Kurs. Eine Vision ist ein bestimmtes Ziel, ein Bild

Five steps to building trust

Last week in our Meetup on Growing Adaptive Organizations we had a very interesting topic: Leadership for Trust i.e. what aspects of leadership are important for building trust.

I present a small part of the discussion here.

Cookie Consent Banner von Real Cookie Banner