PI Planning
PI Planning is a 2 hour event
MYTH: PI Planning can take a few weeks
All features need to be split into stories before we start the breakout sessions.
MYTH: the suggested approach is to prepare the top 10 features and to start familiarising the teams with the content, create the stories needed before the Final Report
Scrum of Scrums is part of the ART sync
FACT: SoS together with the PO sync are two events of the ART sync, they can also be combined if appropriate
PI Planning can be performed remotely
FACT: Yes, using the right technology it can be held remotely
Epics need to have value before we start considering them for the PI.
Truth: Epics should be valuated so as to be able to prioritize the ones which will need to be worked on first.
The System Demo occurs every two weeks
FACT: The System Demo is an event that occurs at the end of each iteration. The PI System demo takes place at the end of each PI i.e. during the Inspect and Adapt.
Once the planning is completed the plan cannot be changed
MYTH: changes are welcomed even late in development if they bring a benefit that is of value to the business
If the RTE is not going to be able to attend the PI, it must be postponed
MYTH: the person that was closest to the RTE during the preparation can facilitate PI planning
The System Demo can be skipped if there is nothing to show
MYTH: System Demos are often neglected because of the inability to integrate effectively. Rather than solve that issue, organisations skip the demos. This is not a good pattern.
All team members should attend PI planning
FACT: collaboration and alignment across all team members is fundamental to the success of PI Planning
Product Management should review the top features for the upcoming PI with Architects
FACT: Collaboration is important to balance business features with technical enablers that will be used to build the future set of business features
Features completed can be deployed in production
FACT: Features that are functionally completed can be deployed but ‘toggled’ off to not disrupt existing functionality
PI Planning can be skipped if people do not have capacity for it
MYTH: PI planning is a cadence-based event that serves as the heartbeat of the Agile Release Train and cannot be skipped.
A senior executive shares about the current state of business context during PI Planning
FACT: business context and vision is an important part of the PI planning
The ART sync is not required for a mature Agile Release Train
MYTH: The ART sync is important so that all trains can provide visibility of progress, scope, risks and impediments