Why wouldnt you just use sprint goals to for the PI Objectives and use labels? Additionally the three Portfolio, Solutions, Program level items are really well implemented in Jira Portfolio.
Hi Matt! Many thanks for your comments! I actually encourage the use the Sprint goals as drivers for the PI goals during the PI Planing...:) It helps understanding the concept of PI. Now, the reason for having PI Objectives as such is because we not only want to keep track of the items that contribute to those PI Objectives (can belong to several different iterations and different types of items), but we also want to keep track of the Planned business value as also the business value achieved by the end of the PI. As such this was the viable solution I found. Regarding JIRA Portfolio, I have to admit that I analysed it 2,5 years ago and it wasn't enough. This is why we selected another solution. As such, my experience with JIRA Portfolio is not up to date and I can't say how easy/hard it easy. I built my solution based on Bigpicture.
@@DOITAGILE Makes sense. I find that as long as the teams plan the epics (including the planned value) and releases well that holding so much additional detail on what is essentially the sprint goal, is overhead. (I understand your implementation, just one of my problems with SAFE), but ya Portfolio has come a long way. definitely worth a second look. They essentially redid it last year after they rolled out the new Jira UI.
Great video! Thank you
Thanks a lot for your support! Feel free to share with anyone you believe may also find it helpful :)
Why wouldnt you just use sprint goals to for the PI Objectives and use labels? Additionally the three Portfolio, Solutions, Program level items are really well implemented in Jira Portfolio.
Hi Matt! Many thanks for your comments!
I actually encourage the use the Sprint goals as drivers for the PI goals during the PI Planing...:) It helps understanding the concept of PI.
Now, the reason for having PI Objectives as such is because we not only want to keep track of the items that contribute to those PI Objectives (can belong to several different iterations and different types of items), but we also want to keep track of the Planned business value as also the business value achieved by the end of the PI. As such this was the viable solution I found.
Regarding JIRA Portfolio, I have to admit that I analysed it 2,5 years ago and it wasn't enough. This is why we selected another solution. As such, my experience with JIRA Portfolio is not up to date and I can't say how easy/hard it easy. I built my solution based on Bigpicture.
@@DOITAGILE Makes sense. I find that as long as the teams plan the epics (including the planned value) and releases well that holding so much additional detail on what is essentially the sprint goal, is overhead. (I understand your implementation, just one of my problems with SAFE), but ya Portfolio has come a long way. definitely worth a second look. They essentially redid it last year after they rolled out the new Jira UI.
Thanks Matt! I'll definitely take a look!