From charter to scope baseline
Your charter said "we will build a treehouse." Now you need the plan for every plank, every nail and what "finished" looks like. If you do not write it down, everyone pictures a different treehouse.
- Before this course: Project Management Basics (course 8.4). You should already be able to write a one-page charter, list tasks, keep a simple risk list and give a status report. This course goes deeper on each of those and does not repeat the basics.
- A requirement is something the project must deliver or a condition it must meet. Write each one so it can be tested ("The booking page loads in under 3 seconds on a phone"), not vague ("fast").
- A scope statement describes the deliverables, what is out of scope, the assumptions and the acceptance criteria (how the sponsor will decide a deliverable is done).
- A WBS (work breakdown structure) splits the scope into smaller pieces. A common rule of thumb is the 100% rule: the pieces under any item must add up to all of that item's work, and nothing extra.
- A WBS dictionary adds a short entry for each work package: description, owner, acceptance criteria and estimate.
- Together, the approved scope statement, WBS and WBS dictionary are called the scope baseline. After approval you change it only through change control.
| Document | Question it answers |
|---|---|
| Requirements list | What exactly must it do? |
| Scope statement | What is in, what is out, how do we accept it? |
| WBS | What are all the pieces of work? |
| WBS dictionary | What does each piece mean, and who owns it? |
- Take the charter from your Beginner project (or a new small project of 2 to 6 weeks).
- Write 8 to 12 requirements. Make each one testable.
- Write the scope statement: deliverables, out of scope, assumptions, acceptance criteria.
- Build a WBS with 3 to 5 deliverables and at least 15 work packages.
- Check the 100% rule: do the parts under each deliverable add up to the whole deliverable and nothing more?
- Add a dictionary line for each work package: owner and acceptance criteria.
- Ask the sponsor to approve the scope baseline.
- Check: every requirement maps to at least one work package.
Read the video script
[Host] "A charter says why. A scope baseline says exactly what."
[Screen: list of requirements with test words] "Write requirements you can test. 'Fast' is not testable. 'Under three seconds on a phone' is."
[Screen: WBS tree with dictionary notes] "Break the scope into a WBS and give each piece an owner and acceptance criteria."
[Text on screen: Scope baseline = scope statement + WBS + dictionary] "Once the sponsor approves it, changes go through change control."
Write 8 to 12 testable requirements, a scope statement and a WBS with a dictionary for one small project. Ask someone to read it and say what "done" means. If their answer differs from yours, fix the text.
ClaudeStuck? Copy a ready-made prompt for Claude
Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.
For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.
I'm learning "Project Management in Practice: schedules, risks and tools" on The Future Market. Lesson 1: "From charter to scope baseline".
What the lesson teaches:
- Before this course: Project Management Basics (course 8.4). You should already be able to write a one-page charter, list tasks, keep a simple risk list and give a status report. This course goes deeper on each of those and does not repeat the basics.
- A requirement is something the project must deliver or a condition it must meet. Write each one so it can be tested ("The booking page loads in under 3 seconds on a phone"), not vague ("fast").
- A scope statement describes the deliverables, what is out of scope, the assumptions and the acceptance criteria (how the sponsor will decide a deliverable is done).
- A WBS (work breakdown structure) splits the scope into smaller pieces. A common rule of thumb is the 100% rule: the pieces under any item must add up to all of that item's work, and nothing extra.
- A WBS dictionary adds a short entry for each work package: description, owner, acceptance criteria and estimate.
- Together, the approved scope statement, WBS and WBS dictionary are called the scope baseline. After approval you change it only through change control.
- Document - Question it answers
The exercise I'm working on:
Write 8 to 12 testable requirements, a scope statement and a WBS with a dictionary for one small project. Ask someone to read it and say what "done" means. If their answer differs from yours, fix the text.
I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.I'm a parent helping my child (about 8 years old) with a lesson called "From charter to scope baseline" from the course "Project Management in Practice: schedules, risks and tools". Here's what the lesson says: Your charter said "we will build a treehouse." Now you need the plan for every plank, every nail and what "finished" looks like. If you do not write it down, everyone pictures a different treehouse. The activity: Write 8 to 12 testable requirements, a scope statement and a WBS with a dictionary for one small project. Ask someone to read it and say what "done" means. If their answer differs from yours, fix the text. Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words. Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Sources
- PMI, Moving from a Work Breakdown Structure to a critical path schedule: www.pmi.org/learning/library/moving-work-breakdown-structure-critical-
- PMI, Practice Standard for Scheduling (second edition): www.pmi.org/-/media/pmi/documents/public/pdf/certifications/practice-s
Estimating with ranges
This lesson is part of full access: every course and every level for one payment.
Build the schedule and find the critical path
This lesson is part of full access: every course and every level for one payment.
Budget and earned value
This lesson is part of full access: every course and every level for one payment.
A risk register that works
This lesson is part of full access: every course and every level for one payment.
Run status reporting in a tool
This lesson is part of full access: every course and every level for one payment.
Change, close and show your work
This lesson is part of full access: every course and every level for one payment.
Final project
This lesson is part of full access: every course and every level for one payment.
Quiz
What three documents make up the scope baseline?
The approved scope statement, WBS and WBS dictionary.
What is the PERT average formula?
(O + 4M + P) / 6.
What is the difference between effort and duration?
Effort is work hours; duration is calendar time.
What is float?
How long a task can slip without delaying the project end date (late start minus early start).
What is true of tasks on the critical path?
They have zero float.
What do CPI and SPI equal?
CPI = EV / AC and SPI = EV / PV.
What does a CPI of 0.89 mean?
The project is over budget (below 1.0 is unfavourable).
How do you score a risk on a 1 to 5 scale?
Probability times impact.
What is a trigger in a risk register?
The warning sign that tells you to act.
What is a baseline?
A saved copy of the approved plan used to compare actual progress.
Final exam
This lesson is part of full access: every course and every level for one payment.
Certificate
This lesson is part of full access: every course and every level for one payment.