Checklist manifesto

Checklist manifesto.
[ ] Team must come up with it.
[ ] Not too many items.
[ ] Critical for the task at hand
[ ] When? Before deployment. Db schema change. When website goes down.
[ ] Quick to perform, unique to the situation and repeatable.
[ ] Not a huge matrix.
[ ] Task oriented.
[ ] Way to self organize.
[ ] Automate it if possible.
[ ] On boarding a new employee
[ ] Checklist for definition of done.
[ ] Documentation, move user story card. Unit tests, etc.
[ ] Things to be delegated.
[ ] Share your checklists.
[ ] Update a single copy. Source control?
[ ] The expert is not the right person to make the list, but should be involved.
[ ] What to do, not how. (Link the how)
[ ] Why are we doing these items?
[ ] Checklist is not a test.
[ ] Use them! GTD. Get things done. Make it a habit to use checklists.
[ ] Prune your checklists. Less is better.
[ ] For times when you must think fast.
[ ] Find the pause points. Before deploy. When something goes wrong. When a new person joins the team.
[ ] Discover what is essential.
[ ] TDD is a checklist. What is the next condition you would like to test for?
[ ] Checklist for building checklists. See book. Checklist manifesto.
[ ] Could be pictograms.
[ ] Checklist smells. Too long. Not performed. Tooany paths.
[ ] Remove ego barriers.
[ ] Teachable moment when something goes wrong.
[ ] Model how things go right with checklists.