RTC - Tracking hours for reviews - best practices
Hi folks,
I would like to get your best practice about tracking hours for review activities (eg. peer review) in a sprint ?
If I spend more than 2 hours in a review activity, should I create a task for review plus the review/approval in the original workitem ? Approval record as an execution item would solve this issue, so I could report how many hours I spent reviewing the item. Do you agree?
Any general advice surrounding how people manage the review and approval process will be welcome.
Tks
2 answers
Rather than create a separate work item for a review, I would just create a "review" work item for the week, specify how much time you expect to spend reviewing (you can always update), and then if you want, you can link that review work item to the work items which contain the reviews. For me, that is more consistent than sometimes creating review work items, and sometimes not.