-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update repo to include Github Projects #110
Comments
@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. I never want to hear anyone say: "I don't know what to work on next". |
In #109, @nelsonic proposed the following columns:
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:
DevelopmentProgress (these can sometimes be questionsReady forAwaiting Reviewin-review
label automagically moved the issue into this column, then we could keep the columnIn Test- Even our best POs have not in the past moved any issues in the Project. Unless there is a dedicated Tester, I would vote that we remove this column for simplification - the issue is either awaiting test, has a bug or a question or is 'done'Ready for Signoff (Business)- I would also suggest we remove this column as for now, the vast majority of our issues go fromAwaiting 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.
The text was updated successfully, but these errors were encountered: