Checklists put everything you need to do right in front of you. You can see the beginning, middle and end of what needs to be done. Though this helps some people tackle tasks in front of them, it can also be distracting. If you are the type who prefers to take things one step at a time, you might enjoy working through a checklist. Big picture people might struggle with a large collection of isolated items, however, and might need other tools such as mind maps, ideas lists and deadline reminders to help them focus on what needs to be done.
We’ve mentioned debugging as a component of the deployment process. However, a process of removing existing and potential errors in the code can be optimized with checklists describing the most important steps for both novice and experienced team members. With that in mind, you will turn the never-ending process of fixing errors into an organized and tailored activity for product optimization.
Checklists support is another essential point that we decided to place out of the list. Some powerful project management tools have changed their attitude to this feature and enhanced their functionality with integrable plugins like Jira checklist. A bunch of capabilities including the creation of acceptance criteria, definition of done, and other ToDo lists, splitting, arranging, prioritizing, and others became available to multiple users. This superficially subtle innovation shows a growing demand for implementing checklists within PM tools as an integral element of workflow organization.
To build a proper testing checklist you need to take into account not only the product requirements and user stories, but also cover a wider spectrum of implementation. At the same time, the test scope should be narrow enough to focus on a product’s functionality. It is also important to make separate tests for different parts or elements of activity. For example, a purchase activity on a website may consist of three parts - signing in, adding products to the cart, and signing out. Splitting your checklists for testing procedures will isolate test failures and keep the focus on the essential details.
Accepting the fallibility of our memories and the overwhelming amount of information we need to manage and apply in our jobs is an important first step. Realize, as Gawande wrote, that "Knowledge has both saved us and burdened us," and recognize that the checklist can make sure your brain doesn't fail you—ever. Then, you'll be ready to create and rely on a checklist, one that that will help you perform better, and more consistently.
Agile software development leverages a technique called the user story to get enough information for implementing software features from an end-user perspective. Shaping acceptance criteria is an integral part of this process that can be improved with a checklist's help. You can create a special format containing categories, point assessments, labels, names, etc. For example, a Definition of Ready can be transformed in Definition of Done category after changing the story specification. On the picture below, you can see an implementation plan, which is, in fact, a ToDo list containing guidance on how to handle the user story written in the description section.
In healthcare, this technique is used in resuscitation procedures. Healthcare workers are trained and recertified, in low and high fidelity simulators, to commence procedures such as Advanced Cardiac Life Support without referring to a checklist. When the patient is not readily revived or responding as expected, the team will refer to their checklists or algorithms to make sure the steps have been executed properly, and that they have not forgotten anything. For this reason, healthcare workers often keep a cognitive aid (a ‘checklist’ of sorts) posted on emergency carts, tucked into pockets or loaded onto mobile devices. ‘Boldface’ checklists can be effective whenever there is a critical sequence to be completed but time is short, or the situation does not enable a physical list to be immediately accessed and used.
It’s likely that the bulk of the audience doesn’t need any explanation of what a checklist is. In a nutshell, it is a list of questions or bullet points that characterize the status/progress of a certain activity or process. The list may contain any essential data regarding your accomplishments or plans. Due to their versatility, checklists can be leveraged in any industry regardless of the business focus. But what is the purpose and benefit of using this process organization tool?
If you do not want to exhaust your team members’ creativity, checklists are a must-have tool for production. Their function is simple - to check whether anything is forgotten or unfinished. And the most important thing is that you do not have to create a new checklist every time a task appears. Creative energy can be channeled to the more exacting tasks.
NO, I don’t. I call them “to do” lists. LOL! They’re very helpful, they keep me sane and keep stress away. For many years now, I keep a daily list prepped the night before; and a weekly list that’s prepped every Sunday. Keeps things smooth-sailing all the time. So at the end of the day, if all items are crashed-out (as in “done”!), I feel so good about myself. :)
B-17 Bombers. You’re likely familiar with the iconic B-17 “Flying Fortress” Bomber. But did you know if it weren’t for a simple checklist, it never would have gained its renown in WWII? In the 1930s, the U.S. Army Air Corps held a competition for airplane manufacturers vying to secure a contract to build the military’s next long-range bomber. Boeing produced a plane that could carry five times as many bombs as the army requested, and flew faster and further than previous bombers. On the day Boeing demonstrated its Flying Fortress, the plane lifted off the tarmac, stalled at 300 feet, and then crashed in a fiery explosion.