Tracking multiple collaborators per work item

Recently I came across following issue. In an electronic (or physical) Kanban board it’s possible to assign a given work item to specific person. Many work/task tracking tools support that (and it’s not specific for Kanban only).

What I wonder about is the possibility to have multiple people working on same item at the same time. In some cases – the work item can be decomposed into several smaller sub-items. I’m not talking about these. What I have in mind is work on which multiple people work together at same time to produce a single output (e.g. pair programming; or doing some discovery/analysis on one and the same topic – and different people contribute with their findings).

What’s the purpose of tracking who’s working on what

I want to focus on an environment which should stimulates self organization and pull style of work. So the purpose is not to punish/prize the responsible person if he doesn’t meet or exceeds some expectations. (I also consider the team could be non-collocated – so the electronic board is something they rely on for coordinating their work).

So here are some options:

  • Visualizing responsible per work item may help people coordinating their work. E.g. avoiding having tasks in “in progress” state which however are not being worked on.
    Having two responsible ones – may lead to situations where each thinks that the other guy is taking care of that work.
  • Tracking and limiting the number of tasks each person is working on at given moment. (I.e. per person WIP).
    This may be valuable in order to avoid hidden excessive multi-tasking.

Some options for tracking collaborators

  1. Each task must have one and only one responsible person (to avoid the above-mentioned situation: nobody working on the task).
    In our pairing scenario – we can somehow select just one of the pairing team-mates to be primary responsible

    1. and either track the other collaborators as secondary ones;
    2. or not track them at all
  2. To stimulate whole-team approach it could be considered best not to track who’s assigned to specific task at all.
    Since it’s a whole team responsibility. If we assign specific person – the others may tread that task as “foreign” one (especially for teams new to the whole team approach idea).
  3. And what remains is – tracking all collaborators per work item as equals without having a dedicated primary one. (Variation of this is – ability to define team/sub-team working on single task).

Since some tools don’t support assigning multiple people per work item. So in case we want 1.A or 3 – a possibility is to create artificial sub-tasks per collaborator. (I would say – that’s a bit weird decomposition of work and is likely to lead to confusion).

And if we want to follow 2 – then if tools allows work assignment, this may lead to confusion.

Conclusion

Presently we’re working like describe din 1.B and the collaboration on single work item is just not tracked in the electronic tool.

I’m still not sure what would be the best way to handle such scenarios. Any comments and suggestions are welcome.

About these ads
This entry was posted in Agile & Lean, Kanban, scrum and tagged , , . Bookmark the permalink.

2 Responses to Tracking multiple collaborators per work item

  1. I can see how this is a tough question. In my personal experience, a task is much less likely to get done if someone is not held accountable for getting it done. Therefore, having the primary responsible person for getting it done is a great idea. When my team uses an electronic Kanban board to work collaboratively on projects, we always have a primary responsible person attached to each task. It helps with collectively holding each other accountable.

    To make sure I understand correctly, you’re currently tracking the primary person in the electronic tool but not the collaborator or the fact that it’s a collaborative task, right? My first thought is that if this method has been working and the work is getting done, then keep it up. My second thought: the Kanban board features won’t solve all of our problems, so in this case, the collaborators need to talk to each other frequently enough to make sure that each of them is on task with getting the job done.

    Hope this helps a little bit. Any questions, feel free to let me know.

  2. javornikolov says:

    Thanks for your comments, @Andy!
    I think the both purposes I described in my post are actually to some extent orthogonal (and in theory can be handled both by separate features in a Kanban tool if both are needed). I.e. – who is the primary accountable is one thing; and who contributed to the given work item – could be different.

    In our case we’re tracking primary person. And at some moment when second collaborator started working on other person’s work item – she created a new card. Which seemed a bit weird – and that second card was dropped, but still it raised ineresting question.

    Yes, I agree a Kanban board won’t solve all problems :-) The question is how to make better use of it. So if hidden collaborators are significantly influencing lead & cycle times (and their predictability) – that’s maybe something which is worth to track.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s