Tasker/Implementer Discussion

Tasker - defined at the time of task card creation; a tasker takes a story and ...

a) defines AC/DCs (customer, acceptance criteria, and deliverables) and posts them out to the Wiki

b) creates and estimates the task cards associated with the story

This is done during the 'post pre-planning' meetings, which take place the day of the pre-planning meeting.

Implementer (or 'Prime' or 'Owner') - the Implementer is established when the actual work is taken up and is typically the first person to take down a task card associated with a story. When that happens, the person's name should be attached to the story card (the blue card). The Implementer...

a) drives the story

b) assures quality (by making sure that the acceptance criteria can be met), and

c) is responsible for keeping tabs on the status of the card

The Implementer can change over time, by hingeing off with someone, so he is not married to the task forever. Note that 'responsible' does not mean 'subject to blame' if the story is not finished, but does mean that he is accountable for the status of the story and for knowing why (and why not) the tasks associated with the story have (have not) been completed.