Project Checklists: A Exam Study

PMBOK v8 Definition

A checklist is a list of items, actions, or points to be considered. Checklists are often used as reminders and are developed based on historical information and knowledge accumulated from similar projects and other sources of information. Using checklists is an effective way to capture lessons learned from similar completed projects, listing specific individual project risks that have occurred previously and that may be relevant to the current project.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions testing your understanding of risk identification tools and organizational process assets. Questions typically ask about when to use checklists, their limitations, and how they differ from other risk identification techniques. Expect scenario-based questions where you must identify the appropriate tool for capturing historical risk information.

Key Points to Remember (for the exam)

• Primary Purpose: Checklists serve as reminders and capture lessons learned from similar completed projects
• Risk Focus: They list specific individual project risks that have occurred previously and may be relevant to the current project
• Sources: Organizations may maintain checklists based on completed projects or use generic checklists from the industry
• Critical Limitation: It is impossible to build an exhaustive checklist—the project team should also explore items that do not appear on the checklist
• Maintenance Requirement: Checklists should be reviewed from time to time to update new information as well as remove or archive obsolete information
• Additional Use: Checklists can serve as "definition of ready" or "full kit" to ensure a project or task is ready to start, particularly useful in minimizing rework
• Governance Application: Project teams may check governance using instruments such as compliance audits or checklists against internal or external standards/benchmarks for predictive approaches

Typical PMI Exam Example

A project manager is leading a new software development project similar to three previous projects in the same organization. During risk identification, the project manager wants to quickly identify risks that occurred in the past projects. What tool should the project manager use? → Answer: A checklist based on historical information and lessons learned from the completed projects.

PMI Exam Traps

• Trap: Thinking checklists are exhaustive and cover all possible risks

• Reality: It is impossible to build an exhaustive checklist; the team must explore items not on the checklist

• Trap: Confusing checklists with risk registers or risk breakdown structures

• Reality: Checklists are historical lists of risks from similar projects; risk registers are current project documents

• Trap: Believing checklists are only for risk identification

• Reality: Checklists also serve as "definition of ready" or "full kit" to ensure tasks are ready to start and minimize rework

• Trap: Assuming checklists are static documents

• Reality: Checklists should be reviewed periodically to update new information and remove or archive obsolete information

Important PMI Connections

Quick Review Questions

1. A project team is using a checklist from a completed project. What must the team remember about this checklist?

2. During a project audit, the team discovers that the checklist being used contains outdated information. What should the project manager do?

3. A project manager wants to ensure a task is ready to begin and minimize rework. Which tool should be used?

4. What is the primary source of information for developing project checklists?

5. A team identifies all risks listed on their checklist. Is the risk identification process complete? Why or why not?

PMBOK v8 Reference

Section 2.2 - Organizational Process Assets (Checklists as part of Organizational Knowledge Repositories) and Section on Tools and Techniques for Risk Identification (Checklists)