PI Planning
The most vital component of achieving anything of value and essentially the backbone of SAFe, is the Program Increment (PI). A Program Increment is timeboxed to 8-12 weeks, where an Agile Release Train, which is constituted of multiple agile teams work towards accomplishing the objectives of the PI. An Agile
PI Planning
Tracking the progress of the Sprint or Program Increment is vital for any enterprise that is adopting an agile framework. Companies utilize digital boards to do this critical task which not only includes planning but monitoring features, estimates, dependencies, statuses, etc. Atlassian’s Jira is a powerful and popular bug
PI Planning
There are certain words and phrases that are used regularly within the “Agile World”. For some, these words are anthems and a great consequence of their delivery method. The main difficulty is finding the right balance of these terms and maintaining them whilst scaling. For many, these are ambitions or
PI Planning
One of the challenges in scaling is maintaining an insight into the actual progression of the value being delivered by multiple teams. There are various options for meetings and ceremonies that provide a holistic view. In the Scaled Agile Framework (SAFe), System Demo is a ceremony that ensures that the
PI Planning
PI objectives are a set of directives that are summarized to describe the technical and business elements of a goal that needs to be achieved by an agile team or an agile release train. They serve the basis of planning and aligning the outcomes of a program increment. PI objectives
PI Planning
Planning Release or Solution Trains can be an enormous task. With hundreds of individuals involved it is necessary to perfectly align them and to manage the workload efficiently. In order to perfectly execute it, a pre-planning session is held among key members of cross-functional agile teams. Participants of the Pre-Planning