Project management is the work of coordinating people, plans, and resources to meet project requirements and deliver an intended result. A project is a temporary effort to create a unique product, service, or outcome; project management helps define what will be delivered, organize the work, address risks, and keep stakeholders informed.
What project management means
The Project Management Institute (PMI) defines project management as “the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.” In practical terms, it connects the goal of a project to its scope, deliverables, schedule, responsibilities, risks, and communication. See PMI’s project-management overview.
A project is temporary and aims to create something unique. Ongoing work that repeats as part of an organization’s normal activity is operations, rather than a project. PMI’s examples of projects include developing a video game, constructing a building, responding to a disaster, and running a promotional campaign. The distinction is useful even when a project’s result becomes part of ongoing operations: the effort to create or change that result has a defined purpose and endpoint. See PMI’s project and lifecycle overview.
Which project management approach should you use?
Choose an approach based on how stable the requirements are, how much uncertainty remains, how often users or stakeholders can give feedback, and how much of the work can be planned reliably in advance. PMI describes predictive, adaptive, and hybrid approaches; none is best for every project.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
| Approach | When it fits | How work is organized |
|---|---|---|
| Predictive | Requirements and outcomes are stable enough to plan in detail upfront. | Work follows a planned sequence, with phases and deliverables established early. |
| Adaptive | Requirements or solutions are uncertain, and feedback can change priorities. | The team works iteratively or incrementally, collaborating frequently and adjusting as it learns. |
| Hybrid | Some parts are predictable while others need frequent adjustment. | The team plans stable components predictively and manages more uncertain components iteratively. |
“Agile” is commonly associated with adaptive work, particularly in software, but it is not a synonym for every adaptive approach. The Agile Manifesto sets out values for software development; a project can be adaptive without following a particular Agile method. PMI recommends tailoring the approach to the project’s circumstances.
What are the project phases?
A project lifecycle is a framework for organizing work from initial evaluation through completion. Common phase names include feasibility, design, build, test, deploy, and close, but they are examples—not a universal required sequence. Teams may combine, rename, repeat, or omit phases depending on the project and its context.
Feasibility
Check whether the project’s business case makes sense and whether the organization has the capability to do the work. This is where a team can assess the intended result before committing to detailed execution.
Design
Plan and analyze the deliverables. The detail will vary: a predictive project may define much of the solution early, while an adaptive project may refine parts of it as feedback arrives.
Rank #3
- book
- A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition and The Standard for Project Management (ENGLISH)
Build
Create the deliverables and carry out quality activities. The work may happen as one planned effort or through repeated increments.
Test
Review and inspect deliverables before acceptance or transition. Testing can reveal issues that require rework or a change in the plan.
Rank #4
- Harvard Business Review Project Management Handbook: How to Launch, Lead, and Sponsor Successful Projects
- Harvard Business Review Press
- BLANK BOOK
Deploy
Put the deliverables into use and manage the transition. Depending on the project, this can include preparing users, transferring responsibility, or moving a product or service into its operating environment.
Close
Complete the work, archive relevant knowledge and artifacts, release the team, and close contracts where applicable.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteBest Value
Project phases are not process groups
Phases describe how a lifecycle is organized; process groups describe ways of organizing project-management work. PMI explicitly cautions against treating the traditional five process groups as five universal project phases. A project can use lifecycle phases tailored to its work without treating process groups as a fixed phase-by-phase recipe. This distinction also addresses the question of whether process groups apply only to traditional projects: they are a way to organize management work, not a mandatory lifecycle that every predictive or adaptive project must follow.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Practical project management tools
Tools are useful when they make important project information visible. Start with the smallest system that lets the team understand the work, responsibilities, timing, risks, and decisions; add governance or tracking as complexity requires. PMI identifies scope, deliverables, risks, and communication as key aspects of project management. Its PMBOK Guide page highlights governance, scope, schedule, finance, stakeholders, resources, and risk as performance domains.
- Define scope and deliverables. Write down what is included and what counts as done. This gives the team and stakeholders a shared reference when requests or assumptions differ.
- Break work into tasks and make the schedule visible. Identify dependencies, owners, and timing. A calendar may be enough for a small effort; a Gantt chart can make sequence and dependencies easier to see.
- Keep a risk log. Record uncertainties, their likely impact, and who owns a response. Review it as the project changes rather than treating it as a one-time document.
- Coordinate tasks and communication. A shared task board and regular check-ins can show progress, blockers, and who needs to act next.
- Record decisions and changes. Note choices that affect scope, schedule, or acceptance so the team can understand what changed and why.
These are practical examples, not a PMI-mandated checklist. An individual task may need only a brief checklist. A project involving several teams may need explicit governance, budget, stakeholder, and risk tracking. The right level of detail is the level that helps people make and carry out decisions without creating unnecessary administration.
Current PMBOK Guide reference
PMI lists the PMBOK Guide—Eighth Edition as a 408-page PMI standard published in November 2025. Its listing describes six core principles and seven performance domains, with expanded coverage of AI, PMOs, and procurement. PMI says the errata sheet for the second printing was last updated in April 2026. Because editions and corrections can change, consult PMI’s PMBOK Guide page for the current listing and errata. The guide is an optional standards reference, not a prerequisite for managing a project.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
