stories to track group uses of time (like code review meetings?)
Hi all,
Right now, my group is making an effort to use the Tracker to keep a handle on tasks both big & small. This includes code review meetings, where four people get together for 2+ hours to walk through a piece of code.
Currently, it seems like each person has to add their own story for the shared code review. What are the best practices for using Tracker for group activities like this? Or is it really not meant to be used in this way?
thanks,
Michael
Right now, my group is making an effort to use the Tracker to keep a handle on tasks both big & small. This includes code review meetings, where four people get together for 2+ hours to walk through a piece of code.
Currently, it seems like each person has to add their own story for the shared code review. What are the best practices for using Tracker for group activities like this? Or is it really not meant to be used in this way?
thanks,
Michael
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?I don't know if I can "bump" this question back up to visibility or not, but I'm still wondering: are there known best practices for indicating that two or more people are working on the same task?
-
Inappropriate?This is a big question for us too-- we have a variety of meetings with multiple developers including code reviews, security certifications, hosting coordination, etc.
Loading Profile...



