PI Planning Day 1 : Getting Started and Team Planning | PI Planning for Beginners #15

[@danarcanjoofficial]

Amazing explanation, I’m from Brazil and I became a huge fan of yours. Keep going! Congratulations.

[@SAFeintheRealWorld]

Thanks, means a lot !

[@francoispauw8040]

Thanks for the content. Better than my training I paid lots for.!!

[@SAFeintheRealWorld]

Thanks for the vote of confidence Francois, means a lot 😁.

[@Jan123.]

This is amazingly helpful!

[@SAFeintheRealWorld]

Glad it was helpful Jan !

[@AramCober]

Nice and very relevant video series. Well done Ahmed!

[@SAFeintheRealWorld]

Thank you Aram, glad you found it useful!

[@terrybora4075]

Great tutorials! Thank you for doing these. One question, the program increment 1 total capacity is 36, when selecting the features do you have to match the total for the features to the capacity of the increment exactly? The reason I am wondering is, we select 1 as small, 3 as medium and 5 as large. But at the same time we say that each individual hypothetical capacity is 8 for a newly formed team, are these scales matching with the S,ML? We could have said that S is 3, M is 5 and L is 8, but the individual capacity is 8, am I missing something?

[@SAFeintheRealWorld]

Hi Terry, thanks for the great question. 1. If your PI Capacity is 36, you don't need to match exactly, but it gives you a good indication of rough order of magnitude size, so wouldn't go to far off it. Now the way I do it is I measure at the Program Tier - e.g. 36 Feature Points. Then each team has their own Story Point Capacity which you don't try to map onto the Feature Points - hope that makes sense ! Regards Ahmed.

[@rc6864]

In your example, how many story points does each of a small, medium and large story represent?

[@SAFeintheRealWorld]

I usually use Small - 1, Medium - 2, Large - 3, X-Large - 5 or X-Small - 1, Small - 2, Medium - 3, Large - 5, X-Large - 8. Hope this helps.

[@kaboozlyco6589]

Ahmed, this is well presented and could even wok for some organizations, but please don’t call it Agile as it is not the one. This is Waterfall wrapped up in Agile lingo, and it will just confuse organizations thinking that they are going to become Agile by practicing this.

[@fo7743]

SAFe is not really Agile... it's not Ahmed's fault.

[@SAFeintheRealWorld]

Hi Kaboozly, I do agree to some degree with you. Of course SAFe certainly does have it's limitations and so certainly you wouldn't recommend it for all Scaling options (e.g. for very agile and nimble companies). In reality what I've found is many traditional companies are so far away from Agile, that SAFe takes them that one step closer and is a palatable option for many companies, but I take your point. Thanks for taking the time to let me know.

[@SAFeintheRealWorld]

Thanks F O :)

[@brianfabrizio4676]

SAFe is a joke. Just do the dam work and trust your team to figure it out. Such a scam.