Meetings (as a Tool/Technique)
Meetings are a tool and technique used across nearly all project management processes to discuss, plan, make decisions, resolve issues, and share information among project stakeholders.
Know it well enough for the exam? Questions on Meetings (as a Tool/Technique) are scenario-based, not definitional.
Practice it freeExplanation
In the PMBOK Guide, meetings are recognized as a formal tool and technique, not merely a routine activity. They appear across all process groups and most knowledge areas. Common types of meetings include kick-off meetings, status meetings, steering committee meetings, retrospectives, lessons learned sessions, daily standups, planning workshops, and change control board meetings.
Effective meetings require clear objectives, a prepared agenda, appropriate participants, a designated facilitator, documented minutes, and action items with assigned owners and due dates. Poorly managed meetings waste time and resources, while well-run meetings accelerate decision-making and alignment. The project manager is often responsible for ensuring that meetings are productive and that outcomes are captured.
Meetings serve different purposes depending on the process. In Develop Project Management Plan, meetings bring the team together to discuss and agree on the plan components. In Perform Integrated Change Control, meetings are used by the CCB to evaluate change requests. In Close Project or Phase, meetings capture final lessons learned and confirm closure activities. The agile framework uses meetings extensively — sprint planning, daily scrums, sprint reviews, and retrospectives are all structured meeting types.
Key Points
- •A formal tool and technique used across nearly all PMBOK processes
- •Types include kick-off, status, steering committee, retrospectives, CCB, and standups
- •Require agendas, clear objectives, appropriate attendees, and documented outcomes
- •In agile, meetings include sprint planning, daily scrum, review, and retrospective
Exam Tip
The exam treats meetings as a legitimate tool and technique, not just an administrative activity. Know the purpose of different meeting types, especially kick-off, retrospective, and CCB meetings.
Frequently Asked Questions
Related Topics
Develop Project Management Plan
Develop Project Management Plan is the process of defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan.
Perform Integrated Change Control
Perform Integrated Change Control is the process of reviewing all change requests, approving or rejecting changes, managing changes to deliverables, project documents, and the project management plan, and communicating the decisions.
Close Project or Phase
Close Project or Phase is the process of finalizing all activities for the project, phase, or contract, including archiving project information, releasing resources, and completing final deliverable acceptance.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Part of
Integration Management
Practice Meetings (as a Tool/Technique)
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.