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

[@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

[@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

[@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.