Work Load Across Multiple Iterations/Releases?
We often have multiple releases ongoing at any point in time. (e.g. fix pack, full release, etc.) A developer on our team may have tasks or assignments in more than one release within the same month. Right now, I represent this in Jazz as separate tasks within the same iteration. Therefore my April iteration contains items from our fixpack, full release, etc. This allows me to use the work load view to determine which developers are overbooked, underbooked, etc. Ideally, I would like to have a stream for each release that contains only work items that relate to that deliverable. The only negative thing about this setup is that the workload view only shows a resources load within a particular iteration, not across multiple overlapping iterations.
Is there a better way to represent this? |
2 answers
I'm interested in the answer to this as well. Anyone on the Jazz team want to comment? Thanks.
|
For 1.0 the team load section in team central is scoped to an iteration.
The reason behind is that a projection onto a time line (e.g overbooked / underbooked) gets really complicated for multiple iteration if they don't have the same start/end date (e.g. you need to defines a work item sequence across iterations to determine whether a user is overbooked / underbooked). There are two setups you can use: - you manage your work in one iteration but deliver the work to different streams (you have a stream for the fix pack / full release / ....). The drawback is that all the work happens in one dev line using the same process. - you create different dev lines (one for full release one for fix pack) and separate teams for each dev line. For the team members in these teams you specify what their work assignment is to that dev line (in %). The team load section will honor the work assignment. A more flexible solution is planned for post 1.0. Dirk Baeumer Agile Planning Component. jshafer wrote: We often have multiple releases ongoing at any point in time. (e.g. |
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.