Daily stabilization branches for releases - my experience

My experience with stabilization branches:

  • Despite good intensions they do not work
  • Everything is more complicated
  • Local Optimization prevents system thinking

 

Im my post i share some of my observations what occurred when the developers decided to introduce a stabilization branches.

 

Context

In the context I am talking about, there was

  • Scrum with multiple teams working on a trunk and temporary one additional release branch
  • a build/deployment pipeline, where only good builds were picked / moved to the next stage in the pipeline.
  • User Story acceptance could only be done on a stage, where the prerequisite / the criteria for a "good build" to be deployed on this stage was a green regression
  • The regression test ran 1-3 times a day on the trunk and the release branch and was often red in the morning.


Results

The concept was tried and ... failed:

  • Only 1/10 of the red regressions were green after fixing the tests on the stabilization branch (!)
  • Several stabilization branches were thrown away due to the better test result in the release branch they were branched from!

The concept increased merge efforts:

  • Downward merge rule: Stabilization Branch -> Branch -> Trunk

The concept led to huge confusion where to fix what and when to check in

  • more confusion, less testing, more checkins during agreed check in stops (stop-the-line rule self by the teams)
  • this lead to more red regressions and more broken builds.

 

The concept also violates the idea of continuous integration and is a real example of local optimization, which (even with good intensions) lead to bad results.

 

An article about Continuous Integration from Martin Fowler from 2006 can be found here

Kommentar schreiben

Kommentare: 2
  • #1

    Adela Wynter (Mittwoch, 01 Februar 2017 09:44)


    Stunning story there. What happened after? Good luck!

  • #2

    Creola Schroyer (Donnerstag, 02 Februar 2017 05:13)


    I've been surfing online greater than three hours nowadays, yet I by no means found any fascinating article like yours. It's lovely worth sufficient for me. In my opinion, if all webmasters and bloggers made good content material as you probably did, the web might be much more helpful than ever before.

Nils Bernert, Agile Coach & LeanStartup enthusiast, valtech.de
Nils Bernert, Agile Coach & LeanStartup enthusiast, valtech.de

Next Appearances

  • ? 05.12.14-07.12.14 LSM Berlin
  • 26.01.15 - 30.01.15 OOP Munich 2015 (Workshop)

Past Appearances

  • 09.08.13 - 11.08.13 LeanStartupMachine (Mentoring)
  • 21.08.13 Stoos MUC: Coaching Dojo (Organizer)
  • 06.09.13 Lean Agile Scrum Zürich (Workshop)
  • 23.09.13 - 25.09.13 Scrum Gathering Paris (Workshop)
  • 03.02.13 - 07.02.13 OOP München (Workshop)
  • 21.02.14 - 24.02.14 Play4Agile (Unconference)
  • 08.03.14 Leancamp Stuttgart (Open Space)
  • 21.03.14 - 22.03.14 Design Thinking Camp München (Barcamp)
  • 30.06.14 - 01.07.14 Scrum Day Stuttgart (Workshop & Presentation)
  • 01.08.14 - 03.08.14. Lean Startup Machine Munich 2014 (Organizer & Mentor)
  • 06.09.14 Javascript Coding Dojo Munich
  • 30.10.14 - 31.10.14 Business Model Generation Masterclass, London
  • 31.10.14 - 02.11.14 LSM Amsterdam (Mentor & Speaker)

Blogroll