Planning: Development line vs Iteration
We recently migrated to RTC and we are in the process of setting up our process and streams before rolling out to our developers. Following are our requirements
1) We also need to actively develop 2.1.2 and 2.2.0 releases 2) We need to support 2.1.0 and 2.1.1 releases in maintenance mode Now should i create multiple development lines each for 2.1.2 and 2.2.0 or should i create a single development line and create iterations for 2.1.2 and 2.2.0 What are the factors that needs to be considered before deciding a particular release to be an iteration or a development line. (One thing i know is if it is a development line it has to be a seperate team area) Thanks in advance, Aruljothi.S |
2 answers
This is a follow up to Arul's posting. We are looking for a best practice implementation. That being said, I wanted to add more detail. Building on what Arul stated below.
We have two releases that are being actively developed 2.1.2 and 2.2.0. Should we have one development line with with two top level iterations with child iterations supported in 1 team area or 2 development lines with each supported by a version specific team area? We recently migrated to RTC and we are in the process of setting up our process and streams before rolling out to our developers. Following are our requirements |
Geoffrey Clemm (30.1k●3●30●35)
| answered May 14 '09, 10:36 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
If the two streams have different schedules (e.g. their iterations start
and stop at different times), then you need two different development lines (now called "time lines", which hopefully will make their purpose clearer). An "iteration" then partitions a given time-line into sequential segments (and a sub-iteration sub-partions each partion into sequential sub-segments). So you need to look at your various streams, and decide which ones can/will be on the same schedule. Cheers, Geoff tdunnigan wrote: This is a follow up to Arul's posting. We are looking for a best |
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.