Iteration without release?
When you create a work item, the only iterations that show up in the "planned for" attribute are iterations for which the check box of "release planned for iteration" is checked.
So what is the use for iterations for which that's not checked, if you can't assign work items to them? I'm thinking of the situation where we have a milestone iteration (with "planned for release" checked) and several internal child iterations...we want to plan the work items we will do within each of those internal iterations but we don't have an external release planned. If this isn't the use of an iteration without a release planned, what is the intended use? |
2 answers
Ummm. Huh? I find the example very good to explain how I might use this but I guess I've never come across this need. Is this the primary use case?
I arrived here while trying to figure out why that checkbox even exists and I'm surprised at the answer. True, it would be more useful in waterfall development; agile projects with 2 week sprints will see little utility here. I suppose to have the tightened process controls in effect the sub-iteration would have to be the current iteration; but the current plan would be tied to the parent iteration and so it seems confusing. Seems like a bit of a hack to use iterations with this checkbox for this use case (even though it works). Also, it's not intuitive as to why work items can't be assigned to an iteration that does not have this checkbox checked. No need for further explanation here as I do understand it but trying to explain this someone leaves all shaking our heads and shrugging our shoulders.. huh?
|
Geoffrey Clemm (30.1k●3●30●35)
| answered May 08 '11, 9:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
One purpose of having sub-iterations that don't get work items assigned
to them is to allow process variations to occur at a time granularity that is finer-grained than the level at which plans are defined. In particular, the purpose of assigning a work item to an iteration is so that you can plan for that iteration. But suppose you want stricter processes to be enforced towards the end of that planning iteration? You can achieve that by having a sub-iteration towards the end of the planning iteration. Note that this is more likely to occur in non-agile environments, where the planning iterations are longer (many months, rather than many weeks). Cheers, Geoff On 5/7/2011 11:38 PM, ajberner wrote: When you create a work item, the only iterations that show up in the |
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.