Moving work item from one iteration to another
I have implemented RTC for a large group of developers with multiple scrum teams. One of the common questions that has been raised is about moving a work item from one iteration to another.
When certain work item is not completed within an iteration (in this case 2 weeks), the WI needs to be carried forward to the next iteration. If the WI is dropped on to another plan, there is no trace of that WI in the previous plan. and the new plan now has a WI that is half complete
What is the recommended way/best practice to move tasks so that theoriginal iteration plan remains unchanged?
Using RTC 2.0 M2 client : Build # Build id: I20090227-1422 on windows
When certain work item is not completed within an iteration (in this case 2 weeks), the WI needs to be carried forward to the next iteration. If the WI is dropped on to another plan, there is no trace of that WI in the previous plan. and the new plan now has a WI that is half complete
What is the recommended way/best practice to move tasks so that the
Using RTC 2.0 M2 client : Build # Build id: I20090227-1422 on windows
One answer
I'd suggest creating another work item ... a parent for the overall task
(scheduled for the next iteration), and a child for the work that was
completed in the current iteration. It's your choice for whether you
use the existing work item as the "parent" or the "child" ... in either
case, you'll have to edit some of its fields.
Also, this really should only be happening at the very end of the
iteration, where a work item that you thought would be quick ends up
taking longer. If you started on a work item earlier in the iteration,
it should have become clear well before the end of the iteration that
the work item would need to be decomposed into more manageable pieces,
and you would want to create child work items at that time.
Cheers,
Geoff
shekariyer wrote:
(scheduled for the next iteration), and a child for the work that was
completed in the current iteration. It's your choice for whether you
use the existing work item as the "parent" or the "child" ... in either
case, you'll have to edit some of its fields.
Also, this really should only be happening at the very end of the
iteration, where a work item that you thought would be quick ends up
taking longer. If you started on a work item earlier in the iteration,
it should have become clear well before the end of the iteration that
the work item would need to be decomposed into more manageable pieces,
and you would want to create child work items at that time.
Cheers,
Geoff
shekariyer wrote:
I have implemented RTC for a large group of developers with multiple
scrum teams. One of the common questions that has been raised is
about moving a work item from one iteration to another.
When certain work item is not completed within an iteration (in this
case 2 weeks), the WI needs to be carried forward to the next
iteration. If the WI is dropped on to another plan, there is no
trace of that WI in the previous plan. and the new plan now has a WI
that is half complete
What is the recommended way/best practice to move tasks so that the
original iteration plan remains
unchanged?
Using RTC 2.0 M2 client : Build # Build id: I20090227-1422 on windows