The Project Management Process: 7 Steps from Idea to Closing
By the end of this lesson you'll be able to:
- List the seven steps of the project management process in order
- Say what each step produces and which life cycle phase it belongs to
- Spot the skipped step behind a common project problem
Quick answer: what is the project management process?
The project management process is the step-by-step way a project goes from idea to closing: define the goal, identify stakeholders, plan the scope and tasks, schedule and budget the work, run it, track it against the plan, and close it. In this Kanbanchi lesson you practice all seven steps and see them in the Empire State Building.
The 7 steps of managing a project, in 9 slides
One idea per slide. Use the buttons, the dots or your arrow keys. The full text of every slide is right below the player.
Lesson 2 slides
9 slides
The full lesson: the project management process, step by step
What is the project management process?
The project management process is the step-by-step way a project goes from idea to closing: define the goal, identify stakeholders, plan the scope and tasks, schedule and budget the work, run it, track it against the plan, and close it. Project management is the work of planning, running and closing a project so it delivers its goal within an agreed scope, time and cost. The process is how that definition turns into daily work.
The life cycle tells you which phase you are in. The process tells you what to do next, one step at a time. The project life cycle is the series of five phases a project moves through: initiation, planning, execution, monitoring and controlling, and closing. The seven steps below sit inside those phases: the first two belong to initiation, the next two to planning, then one step each for execution, monitoring and controlling, and closing.
| Step | What you do | What it produces | Life cycle phase |
|---|---|---|---|
| 1. Define the goal | Agree why the project exists, what success looks like and who sponsors it. | A project charter | Initiation |
| 2. Identify stakeholders | List everyone the project affects or who can affect it, and what each of them needs. | A stakeholder list | Initiation |
| 3. Plan the scope and tasks | Decide what is in and out of scope, then break the work into tasks. | A scope statement and a work breakdown structure | Planning |
| 4. Schedule, budget and risks | Estimate the tasks, put them in order with dates, set the budget and list the main risks. | The schedule, budget and risk list, approved as the baseline | Planning |
| 5. Assign and run the work | Give every task an owner, hold the kickoff and produce the deliverables. | Deliverables | Execution |
| 6. Track progress and control changes | Compare progress with the baseline, report status and decide on change requests. | Status reports and change decisions | Monitoring and controlling |
| 7. Close and review | Hand over the result, get sign-off and record lessons learned. | Sign-off and lessons learned | Closing |
Step 1: Define the goal
Agree why the project exists, what success looks like and who sponsors it. Write it down in a project charter, with a measurable result and a date. If nobody can say what "done" means, stop here: every later step depends on it. A good goal names the result, how you will measure it and the deadline, such as "move all 40 people to the new office by June 30 with no lost working days".
Step 2: Identify stakeholders
List everyone the project affects or who can affect it, and what each of them needs. Stakeholders are the sponsor, the team, the users and anyone who can block or approve the work. Ask early what each of them needs: an update every week, a sign-off at a milestone, or simply not to be surprised. The output is a stakeholder list, and it becomes the basis of your communication plan.
Step 3: Plan the scope and tasks
Decide what is in and out of scope, then break the work into tasks. A work breakdown structure splits the deliverables into tasks small enough to estimate and assign, usually a few days of work each. Writing down what is out of scope matters as much as what is in: it is the line you point to when someone asks for "one small extra".
Step 4: Schedule, budget and risks
Estimate the tasks, put them in order with dates, set the budget and list the main risks. A baseline is the approved version of the scope, schedule and budget that actual progress is measured against. Once the sponsor approves it, you have something to measure against. You will learn to draw the schedule as a Gantt chart in Lesson 6 and to find risks early with a pre-mortem in Lesson 8.
This is also the moment to freeze the plan. Changes are cheap while they are still on paper and expensive once the work has started; the case study below shows a building whose design changed fifteen times on paper and was then built to a fixed timetable.
Step 5: Assign and run the work
Give every task an owner, hold the kickoff and produce the deliverables. One owner per task. A task with two owners usually has none. During this step the project manager removes blockers, keeps stakeholders informed and checks that the deliverables meet the agreed quality.
Step 6: Track progress and control changes
Compare progress with the baseline, report status and decide on change requests. Every change request gets a decision against the baseline: accept it and update the plan, or reject it. A short status report each week, with what is done, what is next and what is at risk, keeps everyone working from the same picture. Deciding what to do first when everything feels urgent is a skill of its own, covered in Lesson 7: How to prioritize tasks.
Step 7: Close and review
Hand over the result, get sign-off and record lessons learned. Closing properly is what turns one project into a better next one. Archive the documents, release the people and the budget, and hold a short review: what went well, what did not, and what you will do differently.
The process repeats in smaller loops
Steps 3 to 6 are not done once. When tracking shows a gap, you go back to planning, update the baseline through a change decision and carry on. In agile projects these loops are short and planned; in waterfall projects they happen only when something changes. In agile projects, planning, execution, and monitoring and controlling repeat in every short cycle, while initiation and closing still happen once. You can compare the two approaches in Lesson 4: Agile vs waterfall.
Case study: the Empire State Building, from a fixed date to opening day
The Empire State Building went from the start of construction to a finished structure in 410 days, a little over 13 months, on a plan fixed in advance. It shows every step of the project management process. All facts below come from Kanbanchi's Great Projects page on the Empire State Building.
Great Projects case study
Empire State Building, 1929 to 1931
Buildings · New York City, United States
Steps 1 and 2: a fixed goal, a fixed date and a clear sponsor
The Empire State Building was a speculative office tower developed by Empire State Inc., formed by former General Motors executive John J. Raskob with partners, and with former New York governor Al Smith at its head. The site was the old Waldorf-Astoria hotel on Fifth Avenue. The goal was fixed from the start: the building had to open on May 1, 1931, and the plans were devised within a budget of $50 million.
Steps 3 and 4: freeze the scope, then schedule back from the date
Architects Shreve, Lamb and Harmon worked to a fixed brief. The design changed fifteen times before it was fixed, as the developers pushed for the title of world's tallest building, but those iterations happened on paper, before construction. The schedule then worked back from the opening date: steel to top out around the start of October 1930 and the structure to be finished in late April 1931. Contractor Starrett Brothers and Eken was to deliver the whole job in about 18 months.
Step 5: run the work as a sequence
Demolition of the hotel began on Oct 1, 1929, and the builders overlapped it with the next phase instead of waiting for the site to be cleared. The steel contract was let on Jan 12, 1930, excavation began ten days later, and construction of the building proper started on Mar 17, 1930. Starrett Brothers and Eken ran the site like an assembly line, with trades following each other up the building on a tight cycle, and the frame rose at up to four and a half stories per week.
Step 6: track against the plan
Because the plan had dated milestones, progress could be checked against it. The steel topped out on Sep 19, 1930, twelve days ahead of schedule. The structure was finished on Apr 11, 1931, 410 days after construction began and also twelve days ahead.
Step 7: close, and separate luck from skill in the review
The building opened on May 1, 1931, the planned date. It cost $40,948,900 including the demolition, well under the $50 million budget. Kanbanchi's page adds a caution for the review: part of the underrun came from Depression prices, not management, and the same downturn left so much office space empty that critics called it the Empty State Building.
What this shows about the process
- A goal with a fixed date and budget (step 1) gave every later step something to plan back from.
- Freezing the scope before work started (step 3) is what let the schedule (step 4) run to a rigid timetable.
- A good review (step 7) asks which gains you could repeat and which came from luck.
Source: Empire State Building: planned vs actual cost and schedule, Kanbanchi Great Projects (with the original sources listed on that page).
Exercise: order the steps, then find the skipped one
Two quick steps. The process steps start shuffled, and the problems come from everyday projects: get instant feedback on each one.
Step 1: put the 7 process steps in order
Drag the handles, or use the arrow buttons, to put the steps in the order a project manager works through them. Then check your order.
Worked example
For a team offsite, you first agree why you are meeting and what a good outcome is (define the goal), and the last thing you do is send the summary and ask what to improve next time (close and review). Put all seven steps in order below.
- 1Schedule, budget and risks
- 2Define the goal
- 3Track progress and control changes
- 4Identify stakeholders
- 5Close and review
- 6Plan the scope and tasks
- 7Assign and run the work
Step 2: which step was skipped?
0 of 7 right
Each problem below comes from a skipped or rushed step. Pick the step that would have prevented it. You get feedback on every answer, and you can try again until it is right.
Worked example
"The project finished, but nobody signed it off, so the team kept getting small requests for months" points to Close: formal sign-off is part of step 7. Now find the skipped step in the 7 problems below.
1. The team starts building, and halfway through the sponsor says it is not what she wanted.
Answer: Goal. Nobody agreed what success looks like. A charter with a measurable goal would have caught this before work started.
2. Legal hears about the new customer app a week before launch and blocks it.
Answer: Stakeholders. Legal can block the project, so it is a stakeholder. Listing stakeholders early tells you who must review the work and when.
3. Nobody knows whether the training videos are part of the project or not.
Answer: Scope. This is a scope question. A scope statement says what is in and what is out.
4. The sponsor asks if the project is on budget, and there is no budget to compare with.
Answer: Schedule and budget. Without an approved budget there is no baseline, so there is nothing to compare spending with.
5. Two people each think the other is writing the user guide, so nobody does.
Answer: Assign. Every task needs exactly one owner. Assigning the work is part of step 5.
6. Small requests keep getting added, and the deadline quietly slips by a month.
Answer: Track. Change requests need a decision against the baseline. Without change control, small requests add up.
7. The next project repeats the same mistakes as the last one.
Answer: Close. Nobody recorded lessons learned. A short review at closing is how teams stop repeating mistakes.
Knowledge check: Lesson 2
Five questions on this lesson. Get at least 4 right to complete Lesson 2 and move your course progress forward. Each answer comes with an explanation.
Key takeaways
- The project management process has seven steps: define the goal, identify stakeholders, plan the scope and tasks, schedule, budget and risks, assign and run the work, track and control changes, and close and review.
- The steps sit inside the five life cycle phases, and steps 3 to 6 repeat whenever the plan changes.
- Freeze the scope before the work starts: changes on paper are cheaper than changes on site.
- Track progress against the baseline at each milestone, and separate luck from skill in the review.
Try it on a real board: the 7 steps in Kanbanchi
Want to run your next project step by step? Set it up in Kanbanchi, the task and project management app that works inside Google Workspace:
- Create a board for your project and add a card called "Project charter" with the goal, the sponsor and the deadline.
- Add a "Stakeholders" card with a checklist of everyone who needs updates or sign-off.
- Add a list for each deliverable and a card for each task, with an assignee on every card.
- Give the cards start and due dates, link dependencies and open the Gantt chart view to see the schedule.
- Add a "Change requests" list and a "Review" card in a closing list, so nothing is forgotten.
This step is optional. The course works without an account, and your progress does not depend on it.
Project management process: FAQ
What are the steps of the project management process?
There are seven: define the goal, identify stakeholders, plan the scope and tasks, set the schedule, budget and risks, assign and run the work, track progress and control changes, and close and review. They sit inside the five phases of the project life cycle.
What is the difference between the project management process and the project life cycle?
The life cycle names the five phases a project moves through. The process is the sequence of steps you take inside those phases, such as identifying stakeholders or controlling changes. The life cycle is the map; the process is the route.
Is the project management process the same for agile projects?
The steps are the same, but agile teams repeat the planning, delivery and tracking steps in every short cycle, while defining the goal and closing still happen once.
Which step is skipped most often?
Defining a measurable goal and closing with a review are the two steps teams most often rush. Both feel optional at the time, and both cause problems later: unclear success at the start, and repeated mistakes on the next project.