Nested iterations
I have a team that uses "nested iterations" - where some of the sub-teams in our organization do 2 week iterations and others do two 1 week iterations nested within that, but all are working on the same release.
We're trying to work out the best way to handle this in RTC.
I *think* we should be able to define an iteration structure like this:
Release 4.0
- I1 (Weeks 1 & 2)
- - I1a (Week 1)
- - I1b (Week 2)
- I2 (Weeks 3 & 4)
- - I2a (Week 3)
- - I2b (Week 4)
- ...
and then have the two-week-iteration teams create iteration plans for I1 and I2, and the one-week-iteration teams create plans for I1a, I1b, I2a, I2b.
Does anyone see any problems with this approach? Anyone got experience doing it?
Thanks!
Mark
We're trying to work out the best way to handle this in RTC.
I *think* we should be able to define an iteration structure like this:
Release 4.0
- I1 (Weeks 1 & 2)
- - I1a (Week 1)
- - I1b (Week 2)
- I2 (Weeks 3 & 4)
- - I2a (Week 3)
- - I2b (Week 4)
- ...
and then have the two-week-iteration teams create iteration plans for I1 and I2, and the one-week-iteration teams create plans for I1a, I1b, I2a, I2b.
Does anyone see any problems with this approach? Anyone got experience doing it?
Thanks!
Mark
One answer
wainwmr wrote:
I don't think that you get in bug trouble with that setup. Note that the
plan type guessing and relation plans (which we introduced with 2.0.0.2)
won't work as expected. For us a leave iteration, e.g I1a, is a sprint
and its parents are considered to be releases. So when creating a plan
for I1 make sure to manually select Sprint Plan as plan type. Besides,
you might want to activate the 'Items for Sub-Iterations' filter.
--
Cheers, Johannes
Agile Planning Team
I have a team that uses "nested iterations" - where some of
the sub-teams in our organization do 2 week iterations and others do
two 1 week iterations nested within that, but all are working on the
same release.
We're trying to work out the best way to handle this in RTC.
I *think* we should be able to define an iteration structure like
this:
Release 4.0
- I1 (Weeks 1 & 2)
- - I1a (Week 1)
- - I1b (Week 2)
- I2 (Weeks 3 & 4)
- - I2a (Week 3)
- - I2b (Week 4)
- ...
and then have the two-week-iteration teams create iteration plans for
I1 and I2, and the one-week-iteration teams create plans for I1a,
I1b, I2a, I2b.
Does anyone see any problems with this approach? Anyone got
experience doing it?
Thanks!
Mark
I don't think that you get in bug trouble with that setup. Note that the
plan type guessing and relation plans (which we introduced with 2.0.0.2)
won't work as expected. For us a leave iteration, e.g I1a, is a sprint
and its parents are considered to be releases. So when creating a plan
for I1 make sure to manually select Sprint Plan as plan type. Besides,
you might want to activate the 'Items for Sub-Iterations' filter.
--
Cheers, Johannes
Agile Planning Team