SAFe®️ PI Planning: Preparing Program Board - 6 of 7

As we understand in the PI Planning meeting, each agile team has its PI Objectives. To achieve these PI Objectives, teams also need to track dependencies on other teams. Program Board is an information radiator that helps make these dependencies visible and helps in overall execution.
Our Seven PI Planning Videos
------------------------------------------------
#1: Program Backlog Readiness • SAFe® PI Planning : Pr...
#2: PI Planning Readiness with Agile Teams • SAFe®️ PI Planning: Re...
#3: Agenda and Structure of PI Planning meeting • SAFe®️ PI Planning : A...
#4: PI Planning Team Breakout Sessions • SAFe®️ PI Planning: Te...
#5: PI Objectives - Committed / Uncommitted • SAFe®️ PI Planning: P...
#6: Preparing Program Board • SAFe®️ PI Planning: Pr...
#7: PI Planning Roles and Responsibilities • SAFe®️ PI Planning: Ro...
Check our upcoming SAFe sessions here: www.izenbridge...
In case of any query feel free to reach [e-mail] or ([phone]
More information on scaled agile framework can be found at : scaledagilefram...

[@tanvisaxena9707]

I so wanted to have this information... thank you sir .. very informative

[@izenbridge]

Glad it was helpful!

[@Dconstr]

Hi, could you please also make a similar set of videos on the Portfolio level which you have done in Program level in this series

[@Immakeepgoin]

Hello, are there any tools for creating the program board instead of using a physical board and sticky notes?

[@izenbridge]

Program Board is called ART Planning Board now, just change of Name in SAFe 6. Jira Align helps in making this. During PI Planning, one can also use tools like PIPlanning.io

[@Dconstr]

So are the dependancies only from user story to Feature ... and Feature to Milestone only ? Or can it be dependancy between Feature 1 and Feature 2 ?

[@izenbridge]

Yes it is possible to have dependacies between features, but in general we should avoid that and create say separate API or something only for dependency part.

[@sirisha000]

Which statement describes accepts of the team’s commitment during PI planning a. the team commits to all the stories they put on their plan b. A team doesn't commit to uncommitted objectives c. A team commits only to the PI objectivities with high business value d. A team commits to all the features they have put on the program board As per what I understood the answer to the above is the last one.I felt its confusing but still you say PI planning is mostly about features instead of user stories .Please correct me whether I am correct or not

[@izenbridge]

I am not sure about the source of question, but I see statement B is right, since in your D statement, we may have uncommitted features also showing up on program board. In case you want to learn SAFe with the help of training, check our Leading SAFe schedule here : www.izenbridge.com/scaling-agile/safe-agilist-certification-training