New project leads, team members, founders, and operators who need a practical system for coordinating a finite piece of work across people and deadlines.
Course 29 · Work playbook 09
Learn Project Management by Running a Real Project
Define outcomes, organize scope, assign ownership, build a schedule, manage risk and change, and close with evidence.
A complete lightweight project system with charter, work plan, schedule, risk log, status rhythm, and retrospective.
A useful primer before lesson one.
This video is published by Project Management Institute. It complements the Life Starter sequence; it does not replace the work inside the lessons.
Watch directly on YouTubeKnow the route before you begin.
This is the working brief for the full course: who it serves, what to prepare, what good work looks like, and the language you will use along the way.
- Choose a real project with a clear end state, at least two stakeholders, and a four- to twelve-week horizon.
- Collect existing commitments, constraints, deadlines, approvals, resources, and known dependencies.
- Choose one shared source of truth the team can actually access and maintain.
Finish with proof you can use.
Run a real project using a signed charter, stakeholder and responsibility map, scoped work breakdown, dependency schedule, risk and decision log, weekly status, change control, acceptance record, and retrospective.
The rules behind the steps.
Outcome before activity
A project succeeds by delivering an accepted result, not by generating a large quantity of tasks and meetings.
Ownership must be singular
Many people can contribute, but each deliverable and decision needs one clearly accountable owner.
Plans are living evidence
Schedules and forecasts should change when reality changes, with the reason and effect made visible.
Key terms worth knowing.
- Charter
- A short authorization document defining the project’s outcome, boundaries, sponsor, lead, constraints, and success.
- Dependency
- A relationship in which one task, decision, resource, or deliverable affects when another can proceed.
- Risk
- An uncertain event or condition that could affect project objectives.
- Acceptance criteria
- Observable conditions that must be met for a deliverable to be approved.
Six lessons.
One finished outcome.
Work in order the first time. Each lesson makes something the next lesson can use.
- 1Up next
Write a useful project charter
Create shared agreement on the outcome, authority, boundaries, constraints, and measures before work expands.
- 227 min
Map stakeholders and ownership
Identify affected people, decision rights, communication needs, and one owner for every important result.
- 335 min
Break outcomes into controlled scope
Decompose the final result into reviewable deliverables and tasks without losing acceptance criteria.
- 436 min
Build a dependency-based schedule
Sequence work using dependencies, capacity, milestones, and uncertainty rather than arbitrary due dates.
- 538 min
Manage risk, status, and change
Surface uncertainty early, report decision-ready status, and control changes to scope, time, cost, and quality.
- 630 min
Accept, close, and learn
Verify the outcome, transfer ownership, close obligations, preserve records, and improve the next project.
Make the lesson easier to act on.
Trust, then verify.
The practice sequence is original editorial synthesis. Current rules, safety details, and platform requirements should be confirmed with these primary or authoritative sources. References reviewed September 9, 2026.
Start with the first useful move.
You’ll always know what to do, what to make, and where to go next.
Illustrative fit—not a recommendation: Project software, collaboration platforms, professional training
See open opportunities