Checklists are :

  • A practical means of capturing processes and procedures
  • Ensures that issues are not missed
  • Quick to create
  • Quick to update
  • Easy to follow
  • Easy to adapt to any situation

A quote from Steve McConnell, author of Code Complete and Rapid Development, editor of IEEE Software's "Best Practices" column.

"Create and use checklists. Checklists are an often-overlooked, low-tech development tool, but they are useful in many areas. They are created from experience, so they're inherently practical. Use them during requirements time to avoid missing key requirements. Use them at architecture and design time to be sure your design accounts for all relevant considerations. Use them during design and code reviews to help reviewers catch the most common problems. Use them at software release to assure that, in the last-minute rush to release the software, you don't make careless mistakes. "

Principles related to checklists:

When using a checklist, if an item doesn't apply, then don't use it. If you aeroplane doesn't have retractable undercarriage then you don't have to check that you undercarriage is down.