It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×1,220

question asked: Dec 23 '13, 5:02 p.m.
question was seen: 4,355 times
last updated: Dec 26 '13, 7:32 p.m.

Related questions

RTC - Tracking hours for reviews - best practices

0
Sandra Santos (32●1●25●25) | asked Dec 23 '13, 5:02 p.m.
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

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Dec 24 '13, 1:12 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
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.
0
permanent link
Sandra Santos (32●1●25●25) | answered Dec 26 '13, 7:32 p.m.
 Great suggestion Geoffrey.
I will do that.
Thanks

Your answer

Register or to post 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.