AI Banner 3
PM terms
album-art
00:00

Project Management Basics

This page is for anyone new to project management or anyone who has been doing it for years without learning the formal vocabulary. It explains the terms PMs use every day, walks through how projects fit into the larger picture of organizational work, and provides a starter glossary of agile terms. Read it end to end as an orientation, or jump to the section you need.

Project

What Is a Project?

A project is a temporary initiative in a unique context undertaken to create value. Three words in that definition do most of the work.

  • Temporary: a project has a start and an end. Once the goal is met (or it becomes clear it will not be), the project closes. Operations, by contrast, run continuously.
  • Unique: every project produces something that did not exist in exactly that form before. Even similar projects, like building two warehouses to the same design, will have different sites, teams, and conditions. No two projects are identical.
  • Value: projects exist to deliver something worthwhile. That might be revenue, cost savings, a regulatory outcome, a happier customer, or a social benefit. If a project is not creating value, it should not be running.

 

Examples of projects include launching a new product, building a bridge, migrating to a new payroll system, running a clinical trial, or organizing a conference. Examples of work that is not a project include answering the company phone, processing weekly payroll, or running the production line. That ongoing work is operations.

project success criteria

Project Success

The modern view of project success is broader than the traditional triple constraint of on time, on budget, and in scope. A project is successful when there is consensus among the intended beneficiaries, other stakeholders, and project participants that it delivered value worth the effort and expense.

That means a project can hit every milestone, come in under budget, and still fail if the customer does not get the value they wanted. It also means a project can run late and over budget yet still be judged a success if the value delivered justifies the overrun.

Project Management

What Is Project Management?

Project management is the application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed the intended value. The project manager is the person accountable for leading that work. The role looks different in different settings, but it almost always includes planning the work, organizing the people, communicating with stakeholders, tracking progress, handling problems as they arise, and closing things out at the end.

In some settings the title is project lead, project coordinator, delivery manager, scrum master, or product owner. The label matters less than the function: someone is responsible for getting the work done.

Project, Program, Portfolio, and Operations

These four words get used interchangeably in everyday conversation, but they mean different things in project management. Understanding the hierarchy makes it easier to know where any given piece of work sits.

Nesting Dolls 4 levels
Portfolio

Portfolio

A collection of projects, programs, and operations managed as a group to achieve strategic objectives. A portfolio aligns work with business strategy. Portfolios are led by portfolio managers, and their job is to make sure the organization is working on the right things, in the right order, at the right time.

Program

Program

A group of related projects, subsidiary programs, and program activities managed in a coordinated way to obtain benefits that would not be available if each project were managed individually. Programs are led by program managers. A program will always have projects beneath it, but a project is not always part of a program.

For example, building a new airport might be a program. The program contains projects for the terminal, the runways, the air traffic control tower, the access roads, and the ground handling systems. Each project has its own manager, its own team, and its own deliverables, but coordinating them as a program delivers the overall airport benefit.

Project

Project

A temporary initiative, in a unique environment, to create a unique result. Often limited in time and led by a project manager.

Operations

Operations

The ongoing, repeatable work an organization performs to deliver its products and services. Running the manufacturing line, processing insurance claims, answering customer support calls, and serving meals in a restaurant are all operations. Operations are permanent. They produce the same kind of output day after day.

Projects often hand their deliverables over to operations at completion. A team builds the new mobile app (project), then the IT operations team runs and maintains it (operations).

How They Fit Together

Organizations use organizational project management as a strategy execution framework. Strategy decides what work matters most. Portfolios pick the right programs and projects to deliver on that strategy. Programs coordinate related projects to realize benefits. Projects deliver specific outputs. Operations run the results and capture the value over time. Performance information feeds back to strategy, which adjusts as the world changes.

As project managers, we work mostly at the bottom of this stack, turning the hopes and aspirations of strategy into real results. It pays to understand the language used above us, because the project we are running was selected by someone for a reason, and that reason came from somewhere higher up.

In the illustration below we see a program to create a new airport. The airport program is comprised of several distinct projects. One for building the terminal, one to build the runways, one for the control tower, etc.

Program and Projects example

Project Life Cycles and Development Approaches

A project life cycle is the series of phases a project passes through from start to finish. The phases vary by approach, but every project goes through them in some form. A common predictive life cycle looks like this:

  1. Aspiration and ideation: someone has a problem to solve or an opportunity to chase.
  2. Business case: the idea gets analyzed for whether it is worth doing.
  3. Create charter: the project is formally authorized.
  4. Develop project plan: the work is planned in detail.
  5. Execute project plan: the work gets done.
  6. Finish project: the deliverables are handed over and the project is closed.
  7. Monitor and control: ongoing across all phases.

How the work flows through these phases is determined by the development approach. There are three to know.

Traditional Icon

Predictive Approaches

Sometimes called waterfall or plan-driven. Predictive approaches plan the work upfront in detail, then execute the plan. The mantra “plan the work, work the plan” captures the character well.

Predictive approaches work well for defined, repeatable projects with clear requirements and low expected change. Construction, manufacturing, and infrastructure projects often suit predictive approaches. Common artifacts include Gantt charts, network diagrams, work breakdown structures, and detailed specification documents.

Traditional Icon

Adaptive (Agile) Approaches

Adaptive approaches plan in small increments and adjust as they go. Work is delivered in short timeboxed iterations (often called sprints), typically two to four weeks long. After each iteration, the team reviews what was built, takes feedback, and adjusts what comes next.

Adaptive approaches work well when requirements are uncertain or expected to change, when frequent feedback is valuable, and when the team needs to learn as they build. Software development is the most common home for agile, but the mindset has spread to product development, marketing campaigns, research, and other knowledge work.

Hybrid icon

Hybrid Approaches

Hybrid approaches combine elements of both. A hybrid project might do a significant amount of upfront planning, like a predictive project, then execute iteratively, like an agile one. Or it might use predictive approaches for some components and adaptive for others.

An optimist might call hybrids the best of both worlds. A pessimist might say they combine the worst of both. The truth sits somewhere in between, but because there is no single hybrid definition, stakeholders usually need a quick orientation to whatever hybrid was created for the project.

Spectrum icon

The Spectrum of Hybrid Approaches

Since hybrids are unique blends, they come in many varieties. On the spectrum from highly predictive to highly adaptive (Traditional to Agile) they occupy the entire middle ground. This means we can create hybrids that are close to traditional, predictive approaches – such as a traditional approach with a series of proof of concepts before committing to a single path. Or a hybrid that is very close to a pure agile approach, but with additional documentation, approvals and governance.

Choosing where to work on the continuum is a tailoring decision driven by the nature of the work, the stability of requirements, risk, and the organizational culture.

Life Cycle Spectrum

The Agile Mindset

Agile Mindset

Agile is an umbrella term covering a variety of methods, approaches, and frameworks. These include team-based approaches such as Scrum and Extreme Programming (XP), and scaling approaches such as Scaled Agile Framework (SAFe) and Disciplined Agile. There are more than 50 known agile approaches in use, which is too many to learn individually. The good news is that they all share a common mindset, and once that mindset clicks, the specific practices make sense.

Agile is a way of thinking. It is big on sharing information, using visualizations, and getting the people doing the work involved in planning and decision making. The agile mindset rests on four values and twelve principles, all set out in the Agile Manifesto from 2001.

The Four Agile Manifesto Values

The Manifesto reads: “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:”

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

“That is, while there is value in the items on the right, we value the items on the left more.”

The Manifesto was written for software, but the values translate. Replace “software” with “the thing you are building” and the values still hold. Focus on people, deliver real outcomes, work closely with the customer, and adjust when the world changes.

The Twelve Agile Principles

The Manifesto authors expanded the four values into twelve guiding principles:

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity, the art of maximizing the amount of work not done, is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Agile Mindset

Doing Agile vs Being Agile

There is a meaningful difference between doing agile and being agile. A team can hold daily standups, work in two-week iterations, and run retrospectives, yet still operate with a command-and-control mindset. They are doing agile, but they are not being agile.

Being agile means internalizing the values: adopting a flexible way of thinking, understanding why the practices exist, picking the right practices for the context, and trusting the team. Once you see the core ideas, you stop having to memorize practices, because each practice is just an expression of the underlying mindset.

The core ideas to look for:

  • Focus on delivering value
  • Build incrementally
  • Gather early feedback
  • Inspect, adapt, and learn as you go
  • Let the team decide as much as possible
  • Be transparent and show progress, good and bad

 

When you see a new agile practice, ask which of these ideas it reflects. The answer is usually obvious, and the practice will then make sense.

Doing Agile vs Being Agile
Glossary icon

A Starter Glossary of Agile Terms

If you have come from a predictive background, agile vocabulary can feel like a foreign language. Here are the terms you are most likely to hear early on.

Iteration / Sprint

A short, timeboxed period during which a team builds a usable increment of the product. Iterations are usually one to four weeks long, often two. “Sprint” is the Scrum-specific name. The terms are used interchangeably in most settings.

Product Backlog

A prioritized list of everything that might be done on the product. The highest-priority items sit at the top. Items near the top are well understood and broken into small pieces. Items further down are larger, less defined, and will be elaborated later as they move up.

Sprint Backlog

A subset of the product backlog selected for the current sprint/iteration. The team commits to delivering this set of items by the end of the sprint/iteration.

User Story

A short description of a piece of functionality, written from the user’s perspective. The common format is: “As a [role], I want [capability] so that [benefit].” For example: “As a returning customer, I want to log in with face recognition so that I do not have to remember my password.”

Acceptance Criteria

The conditions that must be met for a user story to be considered complete. Often written in Given-When-Then form: “Given the user is not signed in, when their face is recognized by the camera, then log them in with their credentials.”

Epic

A large piece of work that is too big to fit in a single sprint/iteration. Epics are broken down into smaller user stories before being worked on.

Feature

A grouping of related stories that together deliver a piece of meaningful functionality, often described in user-facing terms.

Increment

The working output of a sprint/iteration. An increment should be potentially shippable, meaning it could be released if the business decided to do so.

Product Owner

The person who owns the product backlog. They prioritize the work, define what each story means, and decide what gets built next. The Product Owner is the team’s primary connection to the business and customers. In Scrum, the Product Owner has the authority to make scope and priority decisions on behalf of the sponsor.

Scrum Master / Team Lead / Agile Coach

The person who helps the team work effectively. They remove obstacles, facilitate events, coach on agile practices, and shield the team from disruption. They do not assign work, manage individuals, or direct the team. Their job is to make the team better at directing itself.

Development Team

The cross-functional group of people who do the actual building. They include all the skills needed to take a story from idea to working increment. The team is self-organizing: they decide together how to do the work.

Sprint Planning

A meeting at the start of each sprint/iteration where the team and Product Owner agree on what will be worked on. Stories from the top of the product backlog are pulled into the sprint backlog and broken down further if needed.

Daily Standup / Daily Scrum

A short (15 minute or less) daily meeting where the team coordinates. Each person typically shares what they did yesterday, what they will do today, and any blockers. The point is coordination, not status reporting to a manager.

Sprint Review / Demo

A meeting at the end of each sprint/iteration where the team demonstrates the working increment to the Product Owner and other stakeholders. Feedback is gathered, and the backlog may be updated based on what was learned.

Sprint Retrospective

A meeting after the sprint review where the team reflects on how the sprint went and what to improve. The output is one or two concrete process changes to try in the next sprint/iteration.

Velocity

A measure of how much work a team typically completes per sprint/iteration, usually expressed in story points. Velocity is used for forecasting, not for performance management. Comparing one team’s velocity to another’s is a category error.

Story Points

A relative estimate of the effort to complete a user story. Story points account for complexity, risk, and the amount of work, not the number of hours. The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) is a common scale.

Definition of Done

The shared agreement on what “done” means for a piece of work. It might include written, tested, reviewed, integrated, deployed to a staging environment, and accepted by the Product Owner. A consistent Definition of Done prevents “done but not really done” surprises.

Burndown Chart and Burnup Chart

Two ways of visualizing progress. A burndown chart shows work remaining over time, falling toward zero. A burnup chart shows work completed over time, rising toward the total scope, with a second line showing total scope changes.

Kanban Board / Task Board

A visual board, physical or digital, showing the state of work items. Cards move from left to right across columns such as To Do, In Progress, and Done. The board is an example of an information radiator: visible, always current, and accessible to anyone walking past.

Information Radiator

A general term for any large, visible display of project information. Burndown charts, task boards, and impediment lists are all information radiators. The point is transparency without anyone having to ask for a status report.

Minimum Viable Product (MVP), Minimum Marketable Feature (MMF), Minimum Business Increment (MBI)

Three commonly confused terms that all start with “Minimum.”

  • MMF is the smallest feature that delivers real value to a user.
  • MVP is the smallest version of a product that lets the team learn something important about whether they are on the right track. An MVP might contain no MMFs, one MMF, or several.

The Project Management Office

Many organizations have a Project Management Office (PMO), a department or team that centralizes activities related to managing portfolios, programs, and projects. Not every organization has one, and PMOs are not required for project management to happen. Where they do exist, they take different shapes.

Supporting PMO

Supportive PMO

Acts as a resource centre. Develops preferred practices, methodologies, standards, and templates. Coaches and mentors project managers. Low control, high helpfulness.

Controlling PMO

Controlling PMO

Monitors compliance with project management standards, policies, and procedures. Often runs project audits. Medium control: helpful, but with teeth.

Directing PMO

Directive PMO

Manages shared resources, coordinates communication across projects, and exerts direct control over how projects are run. High control. Project managers in directive PMOs report into the PMO rather than into the business.

Agile COE

Agile Centre of Excellence

A newer type of PMO that focuses on building agile capability across the organization. Coaches teams, mentors product owners and sponsors, and helps grow the agile mindset and skills throughout the business.

Organizational Structures

How an organization is structured affects how projects are run, how much authority the project manager has, and how easy it is to get the resources you need. There are four main shapes.

Org Structures
Functional

Functional

The organization is divided by function: engineering, marketing, finance, operations. Staff report to their functional manager. Projects happen within or across functions, but the project manager rarely has direct authority over team members. In a purely functional organization, the project manager role often does not exist as a separate job.

Matrix

Matrix

A blend of functional and project structures. Staff have two reporting lines: a functional manager and a project manager. The balance of authority varies. A weak matrix gives most authority to the functional manager. A strong matrix gives most authority to the project manager. A balanced matrix splits it roughly evenly.

Projectized

Project-Oriented

Staff are organized into project teams led by project managers. Team members work full-time on the project and report directly to the project manager. The project manager has high authority and control. This structure is common in construction, defence, and consulting.

Composite

Composite

Most real organizations are a mix. A composite organization uses different structures for different parts of the business. The IT department might be functional, the new product development group might be project-oriented, and the rest might be matrix.

How Structure Affects the Project Manager

The relative authority of the project manager varies widely depending on the structure:

  • In a functional structure, team loyalty sits with the functional department, the project manager role is seldom identified, and team members work on projects part time.
  • In a matrix structure, team loyalty is conflicted, the project manager role ranges from coordinator to full project manager, and control is shared.
  • In a project-oriented structure, team loyalty sits with the project, the project manager is full-time and responsible, and team members work on the project full-time.

When you take on a project, identify which structure you are working in. It tells you how hard you will have to work to get resources, decisions, and attention.

Project Management Principles

Modern project management is built on a set of principles that apply across all approaches. These are not rules to follow blindly. They are guidance for how to think about the work.

Adopt a Holistic View

See the project as part of a larger system. Decisions in one area ripple through to others. A clever cost saving in procurement might create a quality problem in delivery. Step back regularly and look at the whole picture.

Focus on Value

Every project exists to deliver value. Every decision should be tested against whether it increases or decreases that value. Activities that do not contribute to value are candidates for removal.

Embed Quality into Processes and Deliverables

Quality is built in, not inspected in at the end. Defects found late cost far more to fix than defects caught early. Bake quality checks into how the work is done, not just into the final review.

Be an Accountable Leader

Take responsibility for outcomes. Acknowledge mistakes and fix them. Project managers who quietly point fingers at others when things go wrong rarely retain the trust of their teams or stakeholders.

Integrate Sustainability Within All Project Areas

Consider environmental, social, and economic impacts. Sustainability is no longer a side concern; it shows up in regulation, in customer expectations, and in long-term cost.

Build an Empowered Culture

Trust the team. Let people make decisions about their own work. Empowered teams are faster, more creative, and more engaged than teams waiting for permission.

Tailoring

No two projects are the same, so no two projects should be managed in exactly the same way. Tailoring is the deliberate adaptation of the project management approach, governance, and processes to make them more suitable for the project at hand.

Tailoring is not optional. Picking up a textbook process and applying it without adjustment is a recipe for friction. A small internal project does not need the governance of a major capital programme. A high-risk regulatory project needs more rigor than an internal tool migration.

Tailoring decisions include:

  • Which development approach to use (predictive, adaptive, hybrid)
  • How much documentation to produce
  • Which meetings to hold and how often
  • How decisions get made
  • Which tools and templates to apply
  • How quality is checked
  • How risk is managed

Tailoring happens at the start of the project and continues throughout. As you learn more about the work, adjust the approach to fit what you now know.

Key Roles on a Project

A starter list of who is involved on most projects:

Sponsor

Project Sponsor

The senior person who provides resources and political support for the project, makes major decisions, and is accountable for the project delivering value. The sponsor signs the project charter, helps remove obstacles, and champions the project at senior levels.

Project Manager

Project Manager

Leads the team and the work. Plans, coordinates, communicates, tracks progress, manages risk, handles change, and brings the project to a successful close.

Team

Project Team

The people who do the work. The mix of skills depends on the project: engineers, designers, analysts, testers, vendors, subject matter experts, and so on.

Testimonial icon

Customer

The person or group receiving the project’s outputs. The customer’s view of value is usually the most important measure of success.

Stakeholders

Stakeholders

Anyone affected by the project, or anyone who can affect it. Stakeholders include sponsors, team members, customers, users, vendors, regulators, the public, and even competitors and protest groups. Identifying stakeholders early and understanding what they need is one of the most important things a project manager does.

Change Control Board

Governance Board / Steering Committee

A group of senior stakeholders who oversee the project, review key deliverables, and provide direction on major decisions. The board typically includes the sponsor, senior business representatives, and sometimes PMO resources.