Skip to content

Lesson 1 — What is Software Project Management?

At a glance

  • Module: 01 — Foundations of Software Project Management
  • Level: Beginner
  • Estimated time: 30 minutes
  • Example project: the LMS and the inventory system

Learning objectives

By the end of this lesson you should be able to:

  1. Define what a project is, and explain how it differs from ongoing operations.
  2. Explain what a project manager actually does, day to day.
  3. Describe the constraints a project manager balances.
  4. Give an example of a decision that is project management rather than software engineering.

Prerequisites

  • None. This is the first lesson of the course.

Introduction

You already know how to write software. This lesson is about the discipline that surrounds it: deciding what should be built, in what order, and how anyone can tell whether it is going well.

The vocabulary matters more than it first appears. The words project, risk, estimate, and scope all mean something more precise here than in everyday speech, and every later module depends on those precise meanings. This lesson establishes the three ideas the rest of the course builds on: what a project is, what a project manager actually does, and what a project manager is balancing.

1. A project is temporary work that produces something unique

A project is a temporary effort undertaken to create a unique product, service, or result.

Two words carry the weight:

  • Temporary — a project has a definite beginning and, eventually, an end. It is not the same as operations, which is the ongoing, repetitive work of running something that already exists.
  • Unique — the result is not a copy of something produced before. Even a new version of an existing product involves new requirements, new constraints, or a new team.

Consider the difference in software work:

Ongoing operations A project
Keeping an existing service running, patching it, and answering support tickets Building a new feature that has never existed before
Repeating a known release process on a fixed cadence Migrating an application to a new platform
Routine database backups and monitoring Introducing a new payment provider

Operations are managed by processes and are expected to be stable. Projects are managed by plans and are expected to end. The two are managed differently, and confusing them is a common early mistake — for example, applying "keep the lights on" thinking to a project that genuinely needs to be planned.

Projects vs. products

A product is the lasting thing people use and that is developed over time. Many project-shaped pieces of work deliver into one product. The distinction matters because product work is funded and staffed continuously, whereas a project is funded and staffed for a defined period.

2. What a project manager actually does

The title suggests someone who writes plans. In practice, project management is mostly about reducing uncertainty and keeping a shared picture of reality. The core activities are:

  • Defining what is being delivered, for whom, and why — and getting agreement on it.
  • Planning how the work will be done, in enough detail to be useful and not more.
  • Coordinating the people doing the work: sequencing, dependencies, and communication.
  • Measuring what is actually happening against what was planned.
  • Adapting — replanning honestly when reality differs from the plan.
  • Reporting — giving stakeholders an accurate picture, especially when it is unwelcome.
flowchart LR
    accTitle: The project management cycle
    accDescr {
    Define leads to Plan, Plan to Coordinate, Coordinate to Measure, and Measure to Adapt, which
    returns to Plan. Measure also leads out of the cycle to Report.
    }
    A[Define] --> B[Plan]
    B --> C[Coordinate]
    C --> D[Measure]
    D --> E[Adapt]
    E --> B
    D --> F[Report]

Notice that only planning is a document. The rest are activities. A project manager who produces documents but does not measure or adapt is not managing the project.

The core skill

Much of the job reduces to one question asked constantly: "Is what we believe about this project still true?" Everything else follows from answering it honestly.

3. What a project manager balances

Projects operate under constraints. Four appear on almost every project:

  • Scope — what is included, and what is explicitly excluded.
  • Time — when the result is needed, and when it will be ready.
  • Cost — how much money and effort are available.
  • Quality — how well the result must work, and for whom.

These constraints are connected. Change one and at least one other must move. Compressing the schedule, for instance, does not make work disappear; it either increases cost, reduces scope, or puts quality at risk.

A frequent source of trouble is a stakeholder asking to change one constraint while insisting the others stay fixed. Part of the project manager's job is to make the trade-off visible rather than quietly absorbing it.

On the “triple constraint”

"The triple constraint" is often drawn as time, cost, and scope, with quality as the result. Different sources include different factors, and some add a fourth. The diagram is a teaching aid, not a standard — what matters is the idea underneath it.

4. When it is project management, not engineering

Engineering asks "how do we build it well?" Project management asks "are we building the right thing, in the right order, and can we tell how it is going?"

Both of these are real scenarios. Decide which is engineering and which is management before revealing the answer.

Scenario A

A developer chooses to extract a duplicated function into a shared module to make the code easier to maintain.

Answer

Engineering. It improves how the software is built. It may affect the schedule, but the decision itself is a technical one.

Scenario B

A team's new feature is running three weeks late, and the release date is fixed by an external event. The manager asks the team what could be dropped to meet the date without compromising the parts that matter most.

Answer

Management. It is about scope, time, and value — deciding what to trade, with the trade-off made explicit.

Key terms

Term Meaning
Project A temporary effort to create a unique product, service, or result
Operations Ongoing, repetitive work that keeps something already built running
Product The lasting thing users work with, developed across many projects
Constraint A fixed limit the project cannot change, such as a deadline or budget ceiling
Deliverable An output the project produces for its stakeholders
Project manager The person accountable for defining, planning, coordinating, measuring, and adapting the work

Worked example

Task: decide whether four pieces of work are projects or operations, and say what follows from the answer. The organisation is illustrative.

Step 1 — Apply the two tests. Ask is it temporary? and is the result unique? Both must hold before the work is a project.

Step 2 — Test each item.

Work Temporary? Unique? Verdict
Running the nightly data import that already exists No No Operations
Adding single sign-on across three internal systems Yes Yes Project
Answering student support tickets No No Operations
Migrating the customer database to a new platform Yes Yes Project

Step 3 — Say what follows. Operations are managed by stable processes and measured by reliability. Projects are managed by plans, measured against a defined outcome, and expected to end. Applying operational thinking to a project produces a plan nobody agreed to; applying project thinking to operations produces a plan nobody needed.

Step 4 — State the consequence for the team. The sign-on and migration work needs a defined scope, a named owner, an end date, and a decision about what happens when it finishes. None of those apply to the nightly import.

Common misconceptions

“Project management is writing documents”

Documents are a by-product. The work is defining, coordinating, measuring, and adapting. A project with flawless documents and no measurement or adaptation is not being managed.

“A deadline makes something a project”

Urgency is not the test. A project is defined by being temporary and producing a unique result. Repeating a known process under time pressure is still operations.

“The constraints are independent”

Scope, time, cost, and quality are linked. Any request to change one while holding the others fixed is a request to reduce quality or overload the team — which is worth saying out loud rather than absorbing silently.

Practical activity

Classify ten pieces of work. List ten activities from a software organisation you know — a university IT department, a workplace, or a project you have worked on.

  1. For each, mark whether it is temporary and whether the result is unique.
  2. Classify each as project or operations, and note any that are borderline.
  3. For two of the projects, write the single sentence you would use to describe the unique result.

What "good" looks like: at least one borderline case, with an explanation of why the distinction is genuinely difficult and how you decided. A list where everything is obviously one or the other has not been thought about hard enough.

Self-assessment

  1. Give one example of work at a software company that is operations and one that is a project.
  2. Why is "temporary" important in the definition of a project?

  3. A stakeholder wants a feature added with no change to the deadline or the team. What is the honest response, and why?

  4. Apply it — LMS. The teaching office asks your team for two things with one email: “keep the LMS healthy next year”, meaning nightly backups, term-time support and the occasional small change; and “a plagiarism-checking feature before term starts”. Both arrive with the same deadline and the same budget line.

    Hint: A strong answer says which of the two is a project and which is operations, and names the one property that decides it.

Show answers
  1. Example: Operations — running nightly data imports that already work. Project — adding single sign-on to an existing application.
  2. Because a project is funded and staffed for a defined period and is expected to end. Without that boundary, it is really ongoing product or operational work, which is managed differently.
  3. The constraints are linked: adding scope with time and cost fixed must come from somewhere — usually quality, existing scope, or the team's capacity. The honest response is to make that trade-off explicit and let the person who owns the priorities choose.
  4. Only the second is a project. The plagiarism feature is temporary work producing a unique result; it needs a charter, a baseline, and an end. “Keep the LMS healthy” has no end date and no unique result — it is ongoing operations, and it is managed with a service budget, steady staffing, and availability targets rather than a project plan. The honest response to the email is to accept the feature as a project with a defined scope and end, and to route the support work into a service arrangement with its own owner. Managing both as one project is how operations gets starved whenever the feature is late.

Summary

  • A project is temporary and produces a unique result; operations are ongoing and repetitive.
  • Project management is mostly coordinating, measuring, and adapting — not just writing plans.
  • Projects balance linked constraints: scope, time, cost, and quality.
  • The project manager's recurring job is to keep the team's picture of reality accurate.

Further learning

Next

Continue to Lesson 2 — Projects, Programmes, and Portfolios, which explains how individual projects fit into larger structures.