- Overall status
- Amber
- Progress
- Integration testing is running behind, but the team is confident the Site A pilot will still start in week 4.
- Budget
- On track.
- Next steps
- Continue testing and monitor closely.
Project management practice
Six projects. Every artifact you’ll be judged on.
Build the schedule, the risk register, the RACI, the status report and the change request for realistic delivery projects. Then get a reviewer’s notes on each one, before a sponsor reads yours.
Free plan: 10 exercises a month, 5 with AI review. No card needed.
Schedule Warehouse scanner rollout
Slip a dependency and watch it travel Simplified example
Demo data
- Device deliveryBaseline days 0 to 15. Forecast days 0 to 15.
- Integration testingBaseline days 8 to 18. Forecast days 8 to 18.
- Site A pilotBaseline days 18 to 25. Forecast days 18 to 25.
- StabilisationBaseline days 25 to 35. Forecast days 25 to 35.
- Sites B and CBaseline days 35 to 47. Forecast days 35 to 47.
Moves the integration testing finish date later. Everything that depends on it moves too.
Forecast go-liveDay 47 · W10
Buffer before commitment3 days
StatusOn track
What a reviewer expects next
- ScheduleThe baseline holds, with three days of buffer before the committed go-live.
- Risk registerKeep integration defects logged as a risk, with the Systems lead as owner.
- Status reportReport green, and say what would turn it amber.
- 6delivery scenarios
- 8artifacts in each
- 48reviewed exercises
- 12skill areas tracked
The projects
One project at a time, artifact by artifact.
Each scenario has its own facts, constraints, budget and people. You work through it the way delivery unfolds: read the situation, map who matters, plan it, protect it, report on it and change it.
| Project | .1Case study | .2Stakeholder map | .3Schedule | .4Risk register | .5RACI matrix | .6Status report | .7Change request | .8Scenario quiz |
|---|---|---|---|---|---|---|---|---|
| 01Community clinic relocationMove a clinic in six weeks without losing appointment capacity. | 1.1 | 1.2 | 1.3 | 1.4 | 1.5 | 1.6 | 1.7 | 1.8 |
| 02Nonprofit donor eventHost 180 donors in five weeks with the catering contract still unsigned. | 2.1 | 2.2 | 2.3 | 2.4 | 2.5 | 2.6 | 2.7 | 2.8 |
| 03Warehouse scanner rolloutReplace paper picking with scanners at three warehouses in ten weeks. | 3.1 | 3.2 | 3.3 | 3.4 | 3.5 | 3.6 | 3.7 | 3.8 |
| 04Municipal permit portalLaunch a city’s permit portal in twelve weeks with accessibility and legal gaps still open. | 4.1 | 4.2 | 4.3 | 4.4 | 4.5 | 4.6 | 4.7 | 4.8 |
| 05Hospital laboratory upgradeUpgrade lab instruments over twenty weeks while emergency testing keeps running. | 5.1 | 5.2 | 5.3 | 5.4 | 5.5 | 5.6 | 5.7 | 5.8 |
| 06Multi-country supplier transitionMove critical packaging supply across four countries before the current contract expires. | 6.1 | 6.2 | 6.3 | 6.4 | 6.5 | 6.6 | 6.7 | 6.8 |
Every cell is one exercise with its own rubric. Pick an artifact in the header to start there after you sign up.
How feedback works
A reviewer who reads your report against the facts.
Each artifact is scored against its rubric and the scenario you were given. The notes point at the sentence that needs work and say what a stronger version would include.
Forecast. Your own schedule shows testing finishing on day 24, which pushes the pilot into week 5. Report the forecast you can defend.
Variance. How far behind, against which baseline? Put the number in: six days late against the baseline.
Decision. That isn’t a next step. Name the owner, the action and the date, and ask the Operations VP for the decision you need.
- Report actual progress and variance truthfully: missed
- Make forecast and risks understandable: partly met
- Name owners, next actions and decisions required: missed
Delivery projects · Essential and up
Then run a whole project, from charter to handover.
A delivery project walks you through five phases and twelve steps. Start from one of three practice briefs, or describe your own project. Practice facts are clearly marked as synthetic.
- Phase 1
Define and authorize
- Project charter
- Stakeholder map
- Phase 2
Plan delivery
- Scope and acceptance
- Project schedule
- Risk register
- Budget and responsibilities
- Phase 3
Execute and coordinate
- Delivery coordination
- Decision and issue log
- Phase 4
Monitor and adapt
- Status report
- Change control
- Phase 5
Accept and close
- Acceptance and handover
- Lessons learned
Starting points
- Community clinic relocationPredictive
- Permit service improvementAgile
- Supplier transition with a critical dependencyHybrid
- Your own projectYour approach, kept private
Essential: 1 delivery project a year · Professional: 3 a month · Max: unlimited
Project Workbench · Essential and up
The paperwork that keeps a project honest, in one place.
Documents, drafted with AI help
- Project charter
- Scope and acceptance
- Delivery plan
- Kickoff agenda
- Communication plan
- Status report
- Change request
- Handover and closure
- Lessons learned
Controls you keep up to date
- Schedule and WBS
- Dated tasks, dependencies, milestones, baseline and forecast.
- Budget
- Baseline, approved changes, actual spend and remaining forecast.
- RAID register
- Risks, assumptions, issues and dependencies, each with an owner.
- RACI matrix
- One accountable owner per deliverable, with gaps made visible.
- Change control
- An accepted change creates a new baseline version. The old one stays on record.
Voice coaching · Professional and Max
Rehearse the conversations that decide a project.
Live voice sessions with an AI counterpart playing the sponsor, the specialist or the hiring manager. Graded sessions are scored against a rubric for that conversation.
- Project MentorThink through planning, governance, risk and dependencies. Not graded.
- Stakeholder roleplayNegotiate scope, schedule, resources, change and acceptance.
- Requirements and acceptance interviewDraw out constraints, testable acceptance and who signs off.
- Project management interviewMock interviews from project coordinator to delivery or programme manager.
- Project briefingsStatus update, escalation, change recommendation, kickoff or handover.
Pricing
Start free. Upgrade when you want to run whole projects.
Prices in euros. Change plan or cancel any time from the billing portal.
Free
€0
No card needed
- 10 exercises a month
- 5 AI reviews a month
- Skill profile across 12 areas
Essential
€14/month
or €120 a year (€10/month)
- Unlimited exercises and AI reviews
- Project Workbench
- Personal OKR plan
- 1 delivery project a year
Adds voice coaching
Professional
€25/month
or €240 a year (€20/month)
- Everything in Essential
- 3 delivery projects a month
- Voice coaching
Max
€76/month
or €640 a year (€53/month)
- Everything in Professional
- Unlimited delivery projects
- More voice coaching time
Questions
Before you start
Is this PMP or PRINCE2 exam prep?
No. Project Mastery is practice of the work itself: planning, controlling and reporting on realistic projects. It isn’t accredited and doesn’t replace an exam course, but it’s a good place to apply what one teaches.
Who reviews my work?
An AI reviewer scores each artifact against the rubric for that exercise and the facts of the scenario, then explains what’s missing. Treat it as practice feedback, not a formal assessment.
Predictive, agile or hybrid?
The six scenarios cover all three approaches, from beginner to advanced. When you start a delivery project, you choose the approach.
Can I use my own project?
Yes, on paid plans. Describe your project when you create a delivery project. Your details and documents stay private to your account.
Can I cancel?
Yes. Paid plans are billed through Stripe, and you can change plan, cancel or download invoices from the billing portal at any time.
I manage products, not projects.
Take a look at Product Mastery, our separate platform for product managers. Same account, separate progress.
Make your mistakes on these six projects, not the next real one.
Ten exercises a month are free. Start with the scenario closest to your work.
Start practising free