How about if we write a big room planning pattern for multi-team environments without using the SAFe language, or any other framework's language for that matter?
There's a lot of value in big room planning sessions, online or in-person, but PI Planning is stuck in legacy ideas (it wasn't always this bad) that need to be left behind.
Playing it SAFe does not fit well to a complex situation. You can have both detailed and long-term plans but not detailed long-term ones. If you apply all your suggestions, why even calling it PI Planning? Could be a quarterly alignment on a higher level - a lot more lightweight. A kind of combination of OKRs done right with EBM.
How about if we write a big room planning pattern for multi-team environments without using the SAFe language, or any other framework's language for that matter?
There's a lot of value in big room planning sessions, online or in-person, but PI Planning is stuck in legacy ideas (it wasn't always this bad) that need to be left behind.
Will you take the challenge Willem-Jan? :)
Let's go for it Vasco!
Awesome! Just DM”d you a doc for collab editing.
If anyone else wants to join, just DM me, I’ll share the link
I am also curious. I don't know how much I can help but I see this as a current gap.
Playing it SAFe does not fit well to a complex situation. You can have both detailed and long-term plans but not detailed long-term ones. If you apply all your suggestions, why even calling it PI Planning? Could be a quarterly alignment on a higher level - a lot more lightweight. A kind of combination of OKRs done right with EBM.