Project Management: What It Is, How It Works, and Where It Fits
Project management delivers a defined piece of change on time, within budget and to the agreed scope. Whether that change was the right one to make is a different question, and the one business architecture helps answer.
By Capstera Business Architecture Staff · Updated
14 min read
Project management is the application of knowledge, skills, tools and techniques to deliver a project: a temporary piece of work with a defined start and end, undertaken to create a unique product, service or result. A project manager plans the work, organizes the people and resources, controls scope, time, cost, quality and risk, and keeps stakeholders informed until the result is delivered.
Every organization runs two kinds of work. Most of it is operations: the same order-to-cash, the same payroll, the same customer service, repeated every day. Some of it is change: a new system, a new product line, a new office, a merger. Operations are run by managers who own a function for years. Change has a beginning and an end, and nobody owns it by default. Project management is the discipline that gives a piece of change an owner, a plan and a finish line. It is one of the most widely practiced management disciplines in the world, with its own professional bodies, certifications and methods, and still a frequent source of disappointment, usually for reasons that sit upstream of the project itself.
Key Takeaways
- A project is temporary and unique; operations are ongoing and repetitive. Project management is the discipline for the first kind of work.
- Projects balance scope, time and cost, with quality, risk and benefits close behind. Changing one changes the others.
- Predictive (waterfall) methods plan most of the work up front; adaptive (agile) methods plan in short cycles. Many organizations combine them.
- Projects, programs and portfolios are different levels: deliver one thing; coordinate related things to achieve a benefit; choose the right things.
- A project can be delivered perfectly and still be the wrong project. That is a portfolio and architecture question, not a delivery one.
- Tie each project to the business capabilities it changes, so its success is measured by the change, not just by the deliverables.
What Is Project Management?
Two definitions do most of the work: what a project is, and what managing one involves.
The Project Management Institute (PMI), the largest professional body in the field, defines a project as a temporary endeavor undertaken to create a unique product, service or result. Both words matter. Temporary means it has a defined beginning and end, even if the result lasts for decades. Unique means it is not a repetition of something the organization does routinely; building the first warehouse is a project, while running it is operations.
Project management is the application of knowledge, skills, tools and techniques to project activities so the project meets its requirements. In practice that means agreeing what will be delivered, planning how, organizing the people and money to do it, tracking progress, managing risks and changes, and closing the project when the result has been handed over.
The discipline has several established bodies of practice. PMI's Guide to the Project Management Body of Knowledge (the PMBOK Guide) describes principles and performance domains. PRINCE2, now owned by PeopleCert, is a process-based method built on principles such as continued business justification. Agile approaches, described in the 2001 Manifesto for Agile Software Development and in frameworks such as Scrum, organize delivery into short, iterative cycles. Each is a different answer to the same question: how do you deliver a defined change reliably?
| Project | Operations | |
|---|---|---|
| Duration | Temporary, with a defined end | Ongoing |
| Output | A unique product, service or result | Repeated products or services |
| Purpose | To change something | To keep something running |
| Typical leader | Project manager, for the life of the project | Functional or line manager, indefinitely |
| Success measured by | Delivering the agreed scope, on time and on budget, and the benefits that follow | Performance against ongoing targets |
What Does a Project Manager Do?
A project manager is accountable for delivering the project's objectives. The role is part planner, part coordinator, part negotiator.
The project manager rarely does the specialist work. Instead, the role organizes the people who do it and protects the conditions they need. That includes agreeing the scope with the sponsor and stakeholders, building and maintaining the plan, assembling the team, tracking progress and spending, managing risks and issues, controlling changes to scope, reporting status honestly, and making sure the result is accepted and handed over.
The project manager is distinct from the sponsor, the senior person who owns the business case and the benefits and makes the decisions only they can make. A common failure is a sponsor who treats the project manager as owner of the benefits, or a project manager who makes business decisions that belong to the sponsor. Clarity on that boundary prevents a surprising number of problems.
- Agree scope, objectives and success criteria with the sponsor
- Plan the work, schedule, budget and resources
- Build and lead the project team
- Identify and manage risks, issues and dependencies
- Control changes to scope, time and cost
- Communicate with stakeholders and report status honestly
- Manage quality and the acceptance of deliverables
- Close the project and hand over to operations
The Phases of a Project
Most projects pass through the same broad phases, whatever method is used. The names vary; the questions do not.
In predictive projects these phases run mostly in sequence. In adaptive projects, planning, execution and control repeat every short cycle, while initiation and closing still bracket the whole. Either way, the most consequential decisions are made at initiation: what problem the project solves, what it will deliver, and how success will be judged. Mistakes there are expensive to fix later and invisible to the delivery metrics that follow.
| Phase | The question it answers | Typical outputs |
|---|---|---|
| Initiation | Should we do this, and what exactly is it? | Business case, project charter, initial stakeholder list |
| Planning | How will we do it? | Scope statement, schedule, budget, risk register, communication plan |
| Execution | Are we doing it? | Deliverables, team coordination, procurement |
| Monitoring and control | Is it going to plan, and what are we changing? | Status reports, change decisions, updated forecasts |
| Closing | Is it done and handed over? | Acceptance, handover to operations, lessons learned |
Project Management Methodologies: Predictive, Adaptive and Hybrid
The choice of method should follow the nature of the work, not fashion.
Predictive methods, often called waterfall, define scope, schedule and cost up front and deliver against that plan, managing changes formally. They suit work whose requirements can be known early and whose deliverable cannot easily be released in pieces: a building, a regulatory reporting change with a fixed date, a data center move.
Adaptive methods, usually called agile, deliver in short cycles, typically one to four weeks, releasing usable increments and adjusting priorities each cycle based on feedback. They suit work where requirements are uncertain or will change as users see results, which is common in software and digital products. Scrum and Kanban are the most widely used agile frameworks.
Hybrid approaches combine the two: a predictive frame for funding, milestones and dependencies, with agile delivery inside it. Many large organizations run this way in practice, whatever their methodology documents say.
| Predictive (waterfall) | Adaptive (agile) | Hybrid | |
|---|---|---|---|
| Planning | Mostly up front | Each short cycle | Up-front frame, cycle-by-cycle detail |
| Scope | Fixed early; changes controlled | Evolves with feedback | Fixed outcomes, flexible features |
| Delivery | At the end, or in large stages | Usable increments every cycle | Increments within staged milestones |
| Best suited to | Stable requirements, physical or fixed-date deliverables | Uncertain requirements, software and digital products | Large programs mixing both kinds of work |
| Common risk | Late discovery that the requirement was wrong | Drift without a clear end state | Two processes, each blamed for the other's problems |
Project, Program and Portfolio Management
The three are often confused. They operate at different levels and answer different questions.
Project management delivers one defined piece of change. Program management coordinates a group of related projects and other work so that, together, they achieve a benefit none would achieve alone, such as a new operating model that needs a new system, a reorganization and new processes. Portfolio management decides which projects and programs the organization should invest in at all, balancing them against strategy, capacity and risk.
The distinction matters because each level fails differently. A project fails when it does not deliver what was agreed. A program fails when its projects deliver and the benefit still does not appear, because nobody managed the dependencies between them. A portfolio fails when the organization delivers many projects well and the strategy still does not move, because they were the wrong projects. Project management practice, however good, cannot fix the second and third kinds of failure.
| Project | Program | Portfolio | |
|---|---|---|---|
| Purpose | Deliver a defined output | Achieve a benefit through related projects | Choose and balance investments to meet the strategy |
| Time frame | Temporary | Temporary, usually longer | Ongoing |
| Success measure | Scope, time, cost, quality | Benefits realized | Strategic objectives met; value of the whole investment mix |
| Typical leader | Project manager | Program manager | Portfolio manager or investment committee |
Project Management and Business Architecture
Project management answers "are we doing it right?" Business architecture helps answer "are we doing the right things, and do they fit together?"
A capability map gives every project a statement of what it changes in the business. Instead of "implement the new claims system", a project's charter can say "raise Claims Adjudication from maturity 2 to 4". That one line does three things. It ties the project to the strategy, because the capability's importance is already assessed. It makes overlaps visible, because two projects claiming to improve the same capability show up side by side. And it gives the project a success measure that survives delivery: the capability's performance after go-live.
At portfolio level, the same map shows which capabilities have several projects aimed at them and which important ones have none. Capability-based planning, which sequences investment by the capabilities the strategy needs, is the portfolio's natural partner. Projects remain the delivery vehicle; capabilities become the unit the organization plans and measures.
The value stream view helps inside the project too. A project that changes several stages of a value stream must test the stream end to end, not just its own deliverable, or it will hand over something that works in isolation and breaks at the handoff.
The project management cluster
- Project charter — The document that authorizes a project and gives the project manager authority.
- Project plan — What a project plan contains and how to keep it honest.
- Project management office (PMO) — The function that standardizes project delivery and supports portfolio decisions.
- Capability-based vs. project-based planning — Planning investment by the capabilities the strategy needs.
Why Projects Fail
Most project failures are visible at initiation, if anyone is looking for them.
- Unclear objectives. If the sponsor cannot say what will be different when the project succeeds, the project cannot be steered toward it.
- Scope agreed in words nobody tested. "Replace the system" means different things to every stakeholder until the first demonstration.
- Optimistic estimates. Plans built on best cases leave no room for the problems every project meets.
- No real sponsor. A sponsor who does not make decisions, or cannot, leaves the project manager making business choices without authority.
- Unmanaged dependencies. A project that relies on another team's delivery, data or decision without a plan for it inherits that team's risk.
- Done, but not adopted. Deliverables are accepted, but the people meant to use them were not prepared, and the old way continues.
- The wrong project, delivered well. On time and on budget, it changes a capability that did not matter to the strategy.
Frequently Asked Questions
What is project management?
Project management is the application of knowledge, skills, tools and techniques to deliver a project, a temporary piece of work undertaken to create a unique product, service or result, so that it meets its agreed scope, time, cost and quality objectives.
What is a project manager?
A project manager is the person accountable for delivering a project's objectives. They plan the work, organize the team and resources, manage risks, issues and changes, report status and see the result through to handover. The business decisions and the benefits belong to the project sponsor.
What are the five phases of project management?
Initiation, planning, execution, monitoring and control, and closing. In agile projects, planning, execution and control repeat in short cycles between initiation and closing.
What is the difference between agile and waterfall project management?
Waterfall, or predictive, project management plans most of the work up front and delivers against that plan. Agile, or adaptive, project management delivers in short cycles, releasing usable increments and adjusting priorities each cycle based on feedback. Many organizations combine the two.
What is the difference between a project and a program?
A project delivers a defined output. A program coordinates related projects and other work to achieve a benefit none of them would achieve alone, and manages the dependencies between them.
What is the difference between project management and operations management?
Project management delivers temporary, unique change. Operations management runs the ongoing, repeated work of the business. Projects hand their results over to operations when they close.
What are the main project management methodologies?
Common approaches include the practices described in PMI's PMBOK Guide, the PRINCE2 method, agile frameworks such as Scrum and Kanban, and hybrid approaches that combine predictive and adaptive delivery.
How does business architecture relate to project management?
Business architecture identifies which business capabilities need to change and how much, which shapes which projects are worth doing and how their success is measured. Project management then delivers each change. A capability map also shows overlaps and gaps across the portfolio of projects.
Pro Tips
- Write one line in every project charter naming the business capability the project changes, and its target maturity.
- Separate the sponsor's decisions from the project manager's on day one, in writing.
- Plan the handover to operations as a deliverable, not an afterthought.
- Choose the method by the work: predictive where requirements are stable, adaptive where they will change.
- Measure success twice: delivery at closing, and the capability's performance a few months later.