diff options
| -rw-r--r-- | requirements/kanban.md | 16 | ||||
| -rw-r--r-- | requirements/tasks/task-041.md | 9 |
2 files changed, 25 insertions, 0 deletions
diff --git a/requirements/kanban.md b/requirements/kanban.md new file mode 100644 index 0000000..8a78a3b --- /dev/null +++ b/requirements/kanban.md @@ -0,0 +1,16 @@ +# Kanban board + +| Backlog | Ready | In Progress | +| -------- | ----- | ----------- | +| epic-000 | | task-041 | + +## 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. diff --git a/requirements/tasks/task-041.md b/requirements/tasks/task-041.md new file mode 100644 index 0000000..44c5a30 --- /dev/null +++ b/requirements/tasks/task-041.md @@ -0,0 +1,9 @@ +# task-041 + +Status: in progress + +Engineer the first pass of requirements. + +I don't have to spec everything in detail: it's OK to have placeholder tasks if +I judge that eliciting something is lower-priority. However, everything should +be documented in some way, even if it is a placeholder. |