Unique specific tasks
…breaking work items into tasks.
✣ ✣ ✣
Getting tasks done in a couple of hours or a day at most is fulfilling and demonstrates progress. Understanding how it actually needs to be done to achieve the desired results helps hammering out details of the next greater thing you want to create—the ‘what’. Getting a real grip on things also brings up the important questions. Answering these questions will make you feel comfortable to start working on the product backlog item because you know how.
Remember, no guessing. We are aiming for the exact solution.
The build crew needs:
- a detailed and shared understanding of how the sprint is going to be delivered; and
- to understand what they need to modify, extend, create and delete in order to achieve the necessary results.
The tasks are just a possible side effect but not the purpose of the sprint planning meeting.
- Extend page flow A → B → C with…
- Extend Service X to cope with new…
- Sit with Domain Expert to come up with…
- Update Repository XY with…
- Create table A, B, C…
- Fill table A with data from file…
- Fill table B with data from file…
- Fill table C with join of A and B.
- Pair test/develop initial FitNesse tests for…
- Create component Z for…
Split a work item into unique tasks that are specific to this work item just before backlog refinement meeting as it will surface any questions.
✣ ✣ ✣
Apply one-two-automate to any repetitive work that can be automated.
✣ ✣ ✣
|Goal||get something done in an hour or two +|
|Pearl||Product backlog item +, No guessing +, Build crew +, Sprint +, Sprint planning meeting +, Backlog refinement meeting +, Scrum +, Sprint plan +, One-two-automate + and Unique specific tasks +|
|So||Split a work item into unique tasks specific to this work item. +|
|Theme||Agile +, Scrum + and Kanban +|
|Wish||Feeling comfortable about how to get a thing done +|