In personal life, I find checklist useful to: * not forget small tasks that if piled up, eventually become too big or annoying to tackle (daily budget update,

In personal life, I find checklist useful to: * not forget small tasks that if piled up, eventually become too big or annoying to tackle (daily budget update, email zero-inbox, browser bookmarks cleanup). I group such repeating tasks in daily routines (morning routine, evening routine) or periodical reviews (weekly, monthly etc.) * keep up the habits (flossing, weighing myself) * keep up with events rare enough to forget some pieces of it (weedings - tie a tie, give the shirt to the laundry) Similarly, in software development. I've realized recently that things get less cluttered if you have a process (a checklist, basically) with steps to cover in particular activities. Examples: * work shutdown routine (put a work log to Jira, reply all remaining emails, git push everything). * Definition of Done (DoD): code delivered, tests written, docs updated, etc. That is useful if you (or your team) want up-to-date README but keep forgetting to update it. * topics to cover on project kick-off, here's mine if anyone's interested: http://bartoszkrajka.com/2018/12/28/kick-off-dev-related-topics-to-cover/ http://bartoszkrajka.com/2018/12/28/kick-off-dev-related-top...