Adding confidence to backlog prioritization for a large team
![]()
We have the agile roles of product owner chicken, customer chicken, and chief programmer "work together" to define the prioritization of the ordering in our product backlog using the folders and prioritization withing folders capability of the iteration plan. Basically we only have 3 people on the team with write permissions to that backlog. This works rather well expect that we have about 500 items on this backlog and cannot tell who or when prioritization may have moved, we have even had one case of an accidental overwrite messing up the prioritization of the full queue. Today we have to save off the plan daily using firefox to have a history of the backlog prioritization in case of another accidental overwrite, and to see when things have moved in priority order.
We opened these enhancements for to make this process easier for others to give confidence to the prioritization, and give people a heads up on a potential land mine here so people can learn from what we did. Enhancement 60346 - Allow Changes in Ordering to be Tracked for iteration plan Enhancement 60344 - Allow Work Item Prioritization to be Seen in the Jazz Client Defect 64114 - Don't see any parent - children linking or unlinking in the History tab of a work item to know if they have been added or removed from a plan More on using the backlog in RTC is described in this post also https://jazz.net/forums/viewtopic.php?t=2230 |
One answer
![]()
Thanks for your input. Our goal for 2.0 is it to improve SCRUM support
which includes the issues you mentioned below. -- Cheers, Johannes Agile Planning Team mmallo5 wrote: We have the agile roles of product owner chicken, customer chicken, |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.