RTC enhancement/review best practice question
Hi,
I am new to RTC and I wanted to see if I could get some opinions on best practice for handling enhancements that come back after a reviewed. Here is my question:
A developer works on the enhancement and then submits it for review. At this point the developer has completed their work and closed their enhancement work item. A parent work item which contains the enhancement is submitted for review. Post review there is a determination to modify the enhancement.
Should the modification be a modify to the original enhancement work item or should it be a new work item attached to the review as a link?
Thanks,
Austin
I am new to RTC and I wanted to see if I could get some opinions on best practice for handling enhancements that come back after a reviewed. Here is my question:
A developer works on the enhancement and then submits it for review. At this point the developer has completed their work and closed their enhancement work item. A parent work item which contains the enhancement is submitted for review. Post review there is a determination to modify the enhancement.
Should the modification be a modify to the original enhancement work item or should it be a new work item attached to the review as a link?
Thanks,
Austin
2 answers
The short answer is "both approaches are reasonable".
In the former case, there are fewer work items floating around your system.
In the latter case, you have a record of how much work/time went into
the original work, vs. the work/time that went into the modification.
So it really depends which works better for you.
Cheers,
Geoff
On 3/24/2011 9:53 AM, atyler2010 wrote:
In the former case, there are fewer work items floating around your system.
In the latter case, you have a record of how much work/time went into
the original work, vs. the work/time that went into the modification.
So it really depends which works better for you.
Cheers,
Geoff
On 3/24/2011 9:53 AM, atyler2010 wrote:
Hi,
I am new to RTC and I wanted to see if I could get some opinions on
best practice for handling enhancements that come back after a
reviewed. Here is my question:
A developer works on the enhancement and then submits it for review.
At this point the developer has completed their work and closed their
enhancement work item. A parent work item which contains the
enhancement is submitted for review. Post review there is a
determination to modify the enhancement.
Should the modification be a modify to the original enhancement work
item or should it be a new work item attached to the review as a
link?
Thanks,
Austin
Hi Geoff,
I like how you point out the ability to capture the modification time by the number of enhancements added to the review. I think I can make this work.
Thanks for the reply,
Austin
I like how you point out the ability to capture the modification time by the number of enhancements added to the review. I think I can make this work.
Thanks for the reply,
Austin
The short answer is "both approaches are reasonable".
In the former case, there are fewer work items floating around your system.
In the latter case, you have a record of how much work/time went into
the original work, vs. the work/time that went into the modification.
So it really depends which works better for you.
Cheers,
Geoff
On 3/24/2011 9:53 AM, atyler2010 wrote:
Hi,
I am new to RTC and I wanted to see if I could get some opinions on
best practice for handling enhancements that come back after a
reviewed. Here is my question:
A developer works on the enhancement and then submits it for review.
At this point the developer has completed their work and closed their
enhancement work item. A parent work item which contains the
enhancement is submitted for review. Post review there is a
determination to modify the enhancement.
Should the modification be a modify to the original enhancement work
item or should it be a new work item attached to the review as a
link?
Thanks,
Austin