During a PI, with only one issue per column the planner is much too High
Userlevel 4
+3
Hi
In terms of functionality, though, I would question the need for multiple columns as no two pieces of work ever have exactly the same priority. There is always something, no matter how small, that determines that one piece of work is more/less important than another.
During PI Plannings on restitutions, each team tells how they will do the work during the 9-10 weeks
We (at Allianz) use a planner view for each team and its automatic capacity calculation on story points, and its great
But as the height of planner is very high because of number of tickets, what should be useful for teams and for stakeholders, is to have swimlanes per Epic, with their tickets on 2 or 3 columns , order by epics priorities (on PIs priorities are on Epics not on stories)
Regards
Sylvain
Userlevel 4
+3
Userlevel 7
+3
Thanks for sharing this question
Hope you all can join us for our What’s New Product Webinar too
Userlevel 4
+3
Hope you all can join us for our What’s New Product Webinar too
I’ve put the EMEA and APAC sessions in my calendar, to make sure I don’t miss it :)
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.