Open iteles opened 5 years ago
@iteles I'm not "precious" about the names of the columns in the workflow.
All I (deeply) care about is that we optimise our workflow for the biggest "constraint" in any project: Product owner and ("senior") developer time. It should always be immediately clear from glancing at the "board" who is working on what task/feature, how long they expect it to take, whether something in the project is "blocked" and requires someone's attention what everyone's next priority is once they have finished their current task.
I never want to hear anyone say: "I don't know what to work on next". Wasting anyone's time because the backlog is not prioritised is unacceptable.
In #109, @nelsonic proposed the following columns:![tcm-workflow-with-blockers](https://user-images.githubusercontent.com/194400/31735912-26fa7892-b43b-11e7-9da1-75547a348f89.png)
In practice we have been using a more simplified structure, essentially skipping the first 4 proposed columns above and starting from 'Ready for Dev':
Whilst this may seen simpler, in reality it means that more often than not, adding tech spec and time estimates just doesn't get done.
For internal dwyl projects and for our client projects, usually the PO is the final decision maker and provides sign off, so my only proposed modifications to this as a starting point would be:
in-review
label automagically moved the issue into this column, then we could keep the columnAwaiting Testing
toDone
as the PO/tester also provides sign offI suggest we add a 'Dependencies/Open Questions' column to this list because it is useful for the dev team and POs to keep track of what's blocking work.