Tag: PI planning

Most Common Mistakes When Implementing SAFe

We would like to share with you a few tips on the journey of implementing Scaled Agile Framework (SAFe). Based on our experience there are a few things to watch out for when starting up your first scaled teams’ setup, your first Agile Release Train and then when it is already running full steam ahead. There are many things that can go wrong and the only thing you could be sure of is that some of them will absolutely arise sooner or later. The main thing is for you to be prepared for the worst-case scenario. If you won’t have it – lucky you! If you will face it, you can immediately react.

PI Planning demystified

In our previous article we shared with you an Innovation & Planning sprint (IP) – concept that is coming in from Scaled Agile Framework® (SAFe®). Briefly we mentioned the Program Increment Planning (PI Planning). As this is a wider topic which, in our opinion, requires bigger attention and should be explained in more detail, here we come with it. We decide to implement a scaled agile approach when we have multiple teams (minimum 5) and together work on development of one product. Only then any scaled approach starts to make sense and only when having multiple teams, working together, we need a cross-team alignment and plan for a longer horizon than one sprint. SAFe® calls it PI Planning and it’s one of the best tools to synchronize, align and integrate between teams.