Pair programming/debugging and Jazz
We were having a discussion amongst those evaluating Jazz for our team and we are wondering how we should deal with pair programming.
Sometimes we come across work items to which we wish to assign multiple owners. What's the best strategy to deal with this? We wish to account for the time that both developers will spend on the work item (for resource/busy time estimation) but we are wary of creating multiple items for the exact same work (could lead to confusion).
How does the Jazz team deal with such circumstances?
Sometimes we come across work items to which we wish to assign multiple owners. What's the best strategy to deal with this? We wish to account for the time that both developers will spend on the work item (for resource/busy time estimation) but we are wary of creating multiple items for the exact same work (could lead to confusion).
How does the Jazz team deal with such circumstances?
One answer
I'd suggest creating a child workitem for the other developer.
From a workitem perspective, I don't think pair-programming is any
different from any other situation where a single logical task is being
performed by multiple people.
Cheers,
Geoff (ClearCase Connector team)
gcastro wrote:
From a workitem perspective, I don't think pair-programming is any
different from any other situation where a single logical task is being
performed by multiple people.
Cheers,
Geoff (ClearCase Connector team)
gcastro wrote:
We were having a discussion amongst those evaluating Jazz for our team
and we are wondering how we should deal with pair programming.
Sometimes we come across work items to which we wish to assign
multiple owners. What's the best strategy to deal with this? We wish
to account for the time that both developers will spend on the work
item (for resource/busy time estimation) but we are wary of creating
multiple items for the exact same work (could lead to confusion).
How does the Jazz team deal with such circumstances?