What is "A release is scheduled for this iteration"
Hi,
I'm using RTC2.0.0.2 Fix3 with simple team process.
In "Project Area -> Overview", when editing or creating iteration, there is a check box of "A release is scheduled for this iteration".
What is it?(How does it affect RTC when it is checked and unchecked?)
Regards
James
I'm using RTC2.0.0.2 Fix3 with simple team process.
In "Project Area -> Overview", when editing or creating iteration, there is a check box of "A release is scheduled for this iteration".
What is it?(How does it affect RTC when it is checked and unchecked?)
Regards
James
2 answers
Hi,
I'm using RTC2.0.0.2 Fix3 with simple team process.
In "Project Area -> Overview", when editing or creating iteration, there is a check box of "A release is scheduled for this iteration".
What is it?(How does it affect RTC when it is checked and unchecked?)
Regards
James
Hi James,
"To enable the iteration for an iteration plan, click A release is scheduled for this iteration. Only iterations with deliverables are eligible for iteration plans. "
That means if you don't check this option, you can not create a plan for the iteration.
Kevin, Foundation Process Authoring Team
An iteration can also be used to modify the process rules. So for
example, suppose you have a 6 week planning iteration that has stricter
process rules in the last week. You can define two sub-iterations, a 5
week sub-iteration with the looser rules, and a 1 week sub-iteration
with the stricter rules.
Cheers,
Geoff
On 5/27/2011 1:08 PM, mikom wrote:
example, suppose you have a 6 week planning iteration that has stricter
process rules in the last week. You can define two sub-iterations, a 5
week sub-iteration with the looser rules, and a 1 week sub-iteration
with the stricter rules.
Cheers,
Geoff
On 5/27/2011 1:08 PM, mikom wrote:
So not checking this option makes the iteration pretty useless. What
is it's purpose then?
Comments
Suppose that you wanted to change the process half-way through a particular planning iteration (e.g. make the delivery requirements more strict), but you don't want separate plans for the first and second half of that iteration. In that case, you'd create the sub-iterations so the process changes, but you don't want people to schedule work items separately for the first and second half.