blob: 52a6d7a2ff41e10be507136aa4535a7d13faba13 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
# Kanban board
| Backlog | Ready | Doing |
| -------- | -------- | -------- |
| | | epic-000 |
| ======== | ======== | ======== |
| | task-072 | |
| | task-085 | |
| | task-001 | |
| | task-064 | |
| | task-086 | |
| | task-030 | |
| | task-029 | |
| | task-078 | |
| | task-057 | |
| | task-061 | |
| | task-071 | |
| | task-075 | |
| | task-074 | |
| | task-013 | |
| | task-068 | |
| | task-076 | |
| | task-080 | |
| | task-081 | |
| | task-077 | |
| | task-079 | |
| ======== | ======== | ======== |
| epic-008 | | |
## Usage notes
- The backlog is a list of tickets to refine next. Therefore, I only record
tasks in the backlog once I've decided it's coming up next. Not all tickets
need to be present on the board: that would be a waste of time.
- If I haven't got enough tasks in the backlog, these commands help me to find
what work needs to be done:
- `req.sh list -S req`
- `req.sh list -D task`
- There is no 'Done' column. When a task is done, it is removed from the board.
- Tasks are grouped by Epic. There is a row of === after an epic ticket, and
after the last ticket in the Epic. No task should be on the board without an
Epic.
|
