What Is Project Management? The Project Life Cycle

What you'll learn

Tell a project apart from day-to-day operations, and why the difference matters.
Explain what a project manager actually does all week.
Use the triple constraint (scope, time and cost) to make trade-offs out loud.
Walk through the five phases of the project life cycle with a real example.
Choose between a predictive, agile or hybrid approach for your next project.

Project management is the discipline of getting a one-time piece of work done on purpose: with a clear goal, a plan, a budget, a deadline and someone accountable for pulling it all together. It applies to launching a website, opening a second store, building an office addition or rolling out new software. In this lesson you'll learn what makes something a project, what a project manager does, and the five phases every project moves through, using a small bakery in Austin as the running example.

5phases in the life cycle: initiating, planning, executing, monitoring and controlling, closing

3constraints you always juggle: scope, time and cost (with quality riding on all three)

1person accountable for coordinating the whole thing: the project manager

Spot a project
Know the PM's job
Balance the constraints
Follow the life cycle
Pick an approach

What counts as a project?

A project is temporary work, done in a unique context, to create a specific result. It has a start and an end. When the result is delivered, the project is over and the team moves on. Operations, on the other hand, are the repeating work that keeps a business running: baking the bread every morning, processing payroll every two weeks, answering support tickets.

The distinction is practical, not academic. Operations are managed with routines, checklists and staffing schedules. Projects need something different: a goal everyone agrees on, a plan built from scratch, and decisions about trade-offs, because nobody has done exactly this work in exactly this situation before.

Question	Project	Operations
Does it end?	Yes, when the result is delivered	No, it repeats
Is the output unique?	Yes (a new website, a new building)	No (the same product or service each time)
How is it managed?	Plan, budget, schedule, risks	Procedures, KPIs, shift schedules
Bakery example	Launching online ordering	Baking 600 kolaches every morning

Projects often create new operations. Once the bakery's online ordering is live, taking those orders every day becomes part of operations. The project's job is to hand over something that works.

1. Which of these is a project?

Restocking the warehouse every Monday
Running monthly payroll for 40 employees
Moving the company's files from a local server to a cloud drive by March 31

The cloud migration is temporary (it ends on March 31) and produces a unique result. Restocking and payroll repeat on a schedule, so they're operations.

What a project manager actually does

A project manager (PM) doesn't do all the work. The PM makes sure the right work gets done by the right people, in the right order, for the agreed budget. In a small business, the "PM" is often the owner or a manager wearing a second hat. That's fine: the skills are the same.

Sets direction

Gets the sponsor and key people to agree on the goal, what's included and what "done" looks like.

Output: a project charter and a scope statement.

Plans the work

Breaks the work into tasks, sequences them, estimates time and cost, and spots risks early.

Output: schedule, budget and risk register.

Leads people

Coordinates the team, clears roadblocks, resolves conflicts and keeps stakeholders informed.

Output: communication plan and status reports.

Tracks and adjusts

Compares the plan with reality every week and decides what to change before small slips become big ones.

Output: change log and updated forecasts.

Notice how much of the job is communication. Most projects don't fail because someone couldn't do a task. They fail because people had different ideas of the goal, because problems surfaced too late, or because nobody decided who owned what.

The triple constraint: scope, time and cost

Every project is a balancing act between three things:

Scope: what you'll deliver (features, deliverables, requirements).
Time: when you'll deliver it (the schedule and the deadline).
Cost: how much money and effort it takes (the budget).

Change one and at least one of the others has to move, or quality quietly takes the hit. If a client adds features without adding time or money, the team cuts corners, and the result is bugs, rework or burnout.

Example: Rosa's bakery wants it sooner

Rosa Delgado owns a 12-employee bakery in East Austin. Her project: launch online ordering with local delivery in 10 weeks with an $18,000 budget. Two weeks in, she asks whether it could go live in 8 weeks, before a big neighborhood festival. A good PM doesn't just say "we'll try." She lays out the options:

Option	Scope	Time	Cost
A. Keep the plan	Full: ordering, delivery, loyalty program	10 weeks	$18,000
B. Add a second freelance developer	Full	8 weeks	$21,000 (+$3,000)
C. Move the loyalty program to phase 2	Ordering and delivery only	8 weeks	$18,000

Rosa picks option C: the festival matters more than points and rewards on day one. That's the triple constraint working for you. The decision is explicit, written down and owned by the person paying for the project.

"Fast, cheap and complete" is not a plan

When someone asks for all three, ask which one they'd give up first if they had to. Their answer tells you the project's real priority, and you'll need it later when something goes wrong.

2. A client adds two new features but insists the deadline and the budget stay the same. What's the most likely result if nothing else changes?

The project finishes early because the team is motivated
Quality suffers: rushed work, more defects or an exhausted team
Nothing happens; scope doesn't affect time or cost

More scope with the same time and money leaves only one place to absorb the change: quality. The professional move is to show the trade-off (more time, more money or fewer features) and let the client choose.

The project life cycle: five phases

Every project, from a bakery website to a skyscraper, moves through the same five phases. Monitoring and controlling isn't really a separate step at the end: it runs alongside the work from the first day of planning until closure.

Week 1 · InitiatingDefine why and whatRosa and her PM agree on the goal (online orders from 30% of regulars within three months), the budget and the deadline, and write a one-page charter.
Weeks 2–3 · PlanningDecide howThey list the deliverables, break them into tasks, pick an ordering platform, build the schedule and list what could go wrong.
Weeks 4–9 · ExecutingDo the workMenu setup, product photos, delivery zones, staff training and a soft launch with friends and family.
All along · Monitoring and controllingCompare plan and realityA 20-minute check-in every Friday: what's done, what's late, what's at risk, what changed.
Week 10 · ClosingHand over and learnRosa signs off, the staff takes over daily operations, final invoices are paid and the team writes down what they'd do differently.

Phase	Key question	Typical outputs
Initiating	Why are we doing this, and is it worth it?	Business case, project charter, list of stakeholders
Planning	What exactly will we deliver, and how?	Scope statement, WBS, schedule, budget, risk register, communication plan
Executing	Are we building what we planned?	Deliverables, team meetings, vendor work
Monitoring and controlling	Are we on track? What needs to change?	Status reports, change requests, updated forecasts
Closing	Is it accepted, and what did we learn?	Sign-off, final report, lessons learned, archived files

Where the effort goes

Rosa's project took about 400 hours of work across the bakery staff, a freelance developer and the PM. Here's how those hours split across the phases:

Initiating (5%) 20 hGoal, budget, deadline and the charter.
Planning (15%) 60 hScope, tasks, schedule, vendor selection and risks.
Executing (70%) 280 hBuilding, configuring, photographing, training and testing.
Monitoring and controlling (5%) 20 hWeekly check-ins, tracking and change decisions.
Closing (5%) 20 hSign-off, handover and lessons learned.

Executing takes most of the hours, but the 80 hours of initiating and planning decide whether those 280 hours are spent on the right things.

3. During which phase do you compare actual progress with the plan and approve or reject changes?

Initiating
Closing
Monitoring and controlling, which runs throughout the project

Monitoring and controlling isn't a one-time step. It runs in parallel with planning and executing, so problems get caught while they're still small.

Predictive, agile or hybrid?

The five phases describe what happens. The approach describes how you move through them. There are three broad families:

PredictivePlan it all, then build

Requirements: Clear and stable from the start
Change: ●●●●
Best for: Construction, events, equipment installs, regulatory work.

Fixed scope

AgileDeliver in short cycles

Requirements: Discovered and refined as you go
Change: ●●●●
Best for: Software, digital products, marketing experiments.

Fast feedback

HybridMix both on purpose

Requirements: Some fixed, some evolving
Change: ●●●●
Best for: Business projects with a fixed launch date and flexible features.

Most common

Rosa's project is a typical hybrid. The festival date is fixed and the budget is tight (predictive), but the ordering pages are refined week by week based on what her regulars say during the soft launch (agile). You'll learn the predictive tools in Levels 1 and 2 and the agile ones (Scrum and Kanban) in Level 3.

A quick rule of thumb

If changing your mind halfway through is expensive (pouring concrete, printing 5,000 brochures, signing a venue contract), plan more up front. If changing your mind is cheap (a web page, an email campaign), deliver small pieces and learn from real users.

4. A Denver startup is building a new mobile app, and customers' needs are still unclear. Which approach fits best?

Agile, with short cycles and frequent feedback from users
Predictive, with every screen designed before any coding starts
No approach: just start coding and see what happens

When requirements are uncertain and changes are cheap, agile reduces risk: you show working pieces early and adjust based on real feedback instead of guessing everything up front.

Common beginner mistakes

Jumping straight into execution because "we already know what to do."

Spend a few hours on goal, scope and risks. It's the cheapest time on the whole project.

Treating the project like operations, with no end date and no owner.

Name one accountable person and write down the finish line.

Accepting new requests without discussing time or cost.

Every change gets a quick trade-off conversation, even a two-minute one.

Checking progress only at the end.

Set a weekly check-in from day one; it's how you catch slips early.

Skipping closure because everyone is busy with the next thing.

Get formal sign-off and capture lessons learned while memories are fresh.

Practice exercise

Marcus runs a landscaping company in Round Rock, Texas. He wrote down six activities for next quarter:

Mowing 45 residential lawns every week.
Designing and installing a xeriscape garden for a new commercial client by May 15.
Sending invoices on the first of every month.
Switching from paper scheduling to a scheduling app before spring.
Ordering fertilizer every two weeks.
Launching the company's first website.

(a) Which are projects and which are operations? (b) His app switch will take about 240 hours: 12 initiating, 36 planning, 168 executing, 12 monitoring and controlling and 12 closing. What percentage of the effort is planning, and what percentage is executing?

See solution

(a) Projects: 2 (xeriscape garden), 4 (scheduling app) and 6 (website). Each one is temporary and produces a unique result. Operations: 1, 3 and 5, which repeat on a schedule.

(b) Check the total first: 12 + 36 + 168 + 12 + 12 = 240 hours. Planning is 36 ÷ 240 = 15%. Executing is 168 ÷ 240 = 70%. The remaining 15% is split evenly among initiating, monitoring and controlling, and closing (5% each).

One more thing for Marcus: once the scheduling app is running, using it every day becomes part of operations. The project ends at handover, not when people stop using paper "someday."

Summary

A project is temporary and unique; operations repeat. Projects often create new operations.
The project manager coordinates goals, plans, people and tracking; communication is most of the job.
Scope, time and cost are linked: change one and another moves, or quality pays the price.
Every project goes through initiating, planning, executing, monitoring and controlling, and closing.
Choose predictive when change is expensive, agile when it's cheap and needs are unclear, and hybrid when you have both.

Next lesson: Project Initiation: SMART Goals and the Project Charter. You'll turn a vague idea into a SMART goal, check whether the project pays off and write a one-page charter.