About the IKEA Starter Kit, Spotify and Frameworks

The IKEA kitchen starter kit is a wonderful invention: I need it when I move out of my parents‘ house and set up my first apartment of my own. In this case, it can really make my day: I can use my kitchen, even if I didn’t have a plan for it before. However, if […]

Pragmatic scaling: beyond methods

We are working on a new concept on Agile Scaling. We’ve been doing method-based training on agile scaling, especially SAFe and Less, for some time now. We have learned that it is important to discuss the concepts and principles behind the practices, because only with this background can one adapt the practices to the specific […]

The delivery pipeline in SAFe 4.5

SAFe 4.5 places much more emphasis on describing good practices for a delivery pipeline that provides a solid foundation for a reliable, effective, and continuous value stream. In some implementations, an underestimation of these underlying imperatives has led to mixed success at best. What is new is the explicit description of the iterative and experimental […]

The new SAFe version 4.5 – what does this mean for the application?

The new version 4.5 of SAFe has just been released and this provides an opportunity to reflect not only on the changes in SAFe itself, but also on developments in agile in general. New competitors are apparent: the LeSS framework is ready, now well documented, and has established itself as a clear runner-up in the […]

SAFe 4.5 – the most important innovations at a glance

SAfe 4.5 was released in June and brings some new features. Some are cosmetic, but there are also important additions and clarifications. New Delivery Pipeline Probably the most important addition is the Delivery Pipeline.It is still built on the mantra of „Develop on Cadence, Release on Demand“, which is designed to ensure that the system […]

Team Methods – Teams in a Scaled Environment, Part 3

Scrum/XP as a basis Teams typically use a solid implementation of Scrum as a mainstay and deliver valuable software after each sprint, which is usually every two weeks. They use the roles defined in Scrum: the product owner represents the authority over the user stories to be implemented. The Scrum Master drives the continuous improvement […]

Team skills and qualities – teams in a scaled environment, part 2

Code quality and architecture In larger development, the effect of poor code quality becomes much more pronounced: teams no longer rely on deliverables, cannot make realistic predictions, or make commitments. A scaled environment generally produces long-lived code, and the effects of poor quality add up and hinder deliverability in the long run. Therefore, code quality […]

Team structures and division – Teams in scaled environment, part 1

Multifunctional stable teams The size of self-organized teams is limited, experience shows that they work up to a size of about 10 people, above that subgroups form, daily communication suffers. This limit is set by the number of people we can have in view at the same time and is backed up by many years […]

Four advantages of agile teams

Scaling, Culture and Agile Evolution – Part 1 Why is scaling so hard? And further elaborating, why is it so hard to implement a good agile implementation in the first place? One should take a more thorough look at what the results look like in a good, small agile team and deduce what scaling, implementation […]

HIP Sprints with SAFe and specialized Sprints with Scrum

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 […]