Hi Vy, The Pre-PI Planning session is necessary when you have a solution train with independant Agile Release Trains (ARTs). If you look at the Large Solution/Full SAFe Big Picture you'll see them over there at the Large Solution tier. Whether it is necessary depends upon the context. The use case for it is when you have multiple ARTs with many cross train dependencies, this happens when your Value spans multiple ARTs and then you would use Capabilities in addition to Epics and Features to 'bind' the value together. Hope this helps. Ahmed.
Hi Sunil, I don't think I would like to pretend I can answer 'ALL' the best practices, but here are 10 key ones in my opinion: 1) Be clear on your Vision and Goals. 2) Have very well written Features. 3) Make sure that the teams are familiar with the Features (don't surprise them). 4) Ensure you have an adequate architectural runway (not too much, not too little). 5) Don't turn it into an RTE show - bring other people along for the journey. 6) Make sure you are very well prepared for the event. 7) Manage time on the event very carefully. 8) Reduce surprises by ensuring your team know what to expect through training. You can go to sprint0.com/safe-program-increment-planning/ if you want a quick 3 - series training overview. 9) Be clear on your capacity for : the Agile Release Train; for each team on the ART. 10) Ensure clear outputs and make sure that you have a high confidence level. [ Okay, well I cheated a bit there, but 10 sounds cooler than 11 :)]. Hope this helped. Ahmed.
It’s really great sharing, Thanks Bill.
Thanks Eugene.
Great video. Thanks.
Thanks Thomas.
Good job
Thanks Prasad, really appreciate you taking the time out of your busy schedule to give me feedback.
What about Pre- PI planning session? Is it necessary? When should it be done?
Hi Vy, The Pre-PI Planning session is necessary when you have a solution train with independant Agile Release Trains (ARTs). If you look at the Large Solution/Full SAFe Big Picture you'll see them over there at the Large Solution tier. Whether it is necessary depends upon the context. The use case for it is when you have multiple ARTs with many cross train dependencies, this happens when your Value spans multiple ARTs and then you would use Capabilities in addition to Epics and Features to 'bind' the value together. Hope this helps. Ahmed.
@@SAFeintheRealWorld thanks :)
@@SAFeintheRealWorld when you have large solutions, the value stream does a pre pi planning
Can we just use jira for big room planning?
@@ultimatenehal ine does not contradict another :) Jira is just tracking tool
Can anyone answer "what are all the best practices in PI Planning"??
Hi Sunil, I don't think I would like to pretend I can answer 'ALL' the best practices, but here are 10 key ones in my opinion:
1) Be clear on your Vision and Goals.
2) Have very well written Features.
3) Make sure that the teams are familiar with the Features (don't surprise them).
4) Ensure you have an adequate architectural runway (not too much, not too little).
5) Don't turn it into an RTE show - bring other people along for the journey.
6) Make sure you are very well prepared for the event.
7) Manage time on the event very carefully.
8) Reduce surprises by ensuring your team know what to expect through training. You can go to sprint0.com/safe-program-increment-planning/ if you want a quick 3 - series training overview.
9) Be clear on your capacity for : the Agile Release Train; for each team on the ART.
10) Ensure clear outputs and make sure that you have a high confidence level. [ Okay, well I cheated a bit there, but 10 sounds cooler than 11 :)]. Hope this helped. Ahmed.