# Project Management Without the Bureaucracy: Run One Project from Brief to Closure

> Run work with a deadline without drowning in process. Write a one-page brief, break scope down and cut it before dates, find the critical path, estimate in ranges with one shared buffer, map stakeholders, keep a short risk register, handle changes and delays, and close the project with a blameless retrospective, all on one realistic project: the launch of a new subject at an online tutoring school.

- Source: https://productovi.com/courses/project-management-without-bureaucracy
- Free, no sign-up needed to read.

## Modules

### Module 1. What a project is, and the one-page brief

Project, operations or product work; goal versus outputs; the one-page brief; a brief for the physics launch.

- [Project, operations or product work?](https://productovi.com/courses/project-management-without-bureaucracy/project-operations-or-product-work.md): What makes work a project, how it differs from operations and product work, and when a project frame only adds ceremony.
- [Goal or outputs: what success means](https://productovi.com/courses/project-management-without-bureaucracy/goal-or-outputs.md): Why finished outputs aren't success, and how to write two-part success criteria: delivery and result.
- [The one-page brief](https://productovi.com/courses/project-management-without-bureaucracy/the-one-page-brief.md): Goal, success, scope in and out, limits, testable assumptions, names and a change rule: one page a sponsor can sign.
- [Case: the brief for the physics launch](https://productovi.com/courses/project-management-without-bureaucracy/physics-launch-brief-case.md): Turn Leo's list of outputs into the one-page brief he will sign: a goal that names the change, two-part success criteria, an out list and assumptions you can test.

### Module 2. Scope: what is in and what is out

Breaking work down from deliverables, acceptance criteria, and cutting scope before dates.

- [Break the work down from deliverables](https://productovi.com/courses/project-management-without-bureaucracy/break-the-work-down.md): Deliverables first, tasks second: a tree that covers all the work of the physics launch and nothing twice, flattened into a list with owners and effort ranges.
- [Acceptance criteria: what "done" means](https://productovi.com/courses/project-management-without-bureaucracy/acceptance-criteria.md): "Good lessons" is a wish nobody can accept. Write checks a named person can run, agree them before the work starts, and say what happens when one fails.
- [Must, should, could: cut scope, not the date](https://productovi.com/courses/project-management-without-bureaucracy/must-should-could.md): When the list is longer than the time, sort every deliverable with one test, agree in advance what is dropped first, and keep the fixed date.
- [Case: the deliverable list that doesn't fit](https://productovi.com/courses/project-management-without-bureaucracy/deliverable-list-case.md): Twenty-five deliverables with effort ranges, 150 person-days of capacity. Add up effort by priority, challenge two false musts, and write Leo the scope decision with a drop order.

### Module 3. Time: dependencies and the critical path

Dependencies, milestones, critical path and float, and why effort is not duration.

- [Dependencies and milestones as decision points](https://productovi.com/courses/project-management-without-bureaucracy/dependencies-and-milestones.md): Find what waits for what, including the dependency nobody wrote down, and turn milestones into questions with a decision ready for each answer.
- [The critical path and float](https://productovi.com/courses/project-management-without-bureaucracy/critical-path-and-float.md): A forward pass and a backward pass by hand on eight tasks of the physics launch: the earliest finish, the chain with no room, and how much the other tasks can slip.
- [Effort is not duration: when adding people helps](https://productovi.com/courses/project-management-without-bureaucracy/effort-is-not-duration.md): Why ten days of review don't become two with five reviewers: the parts that can't be split, the cost of coordinating, and the waiting no extra person removes.
- [Case: the schedule to 1 February](https://productovi.com/courses/project-management-without-bureaucracy/schedule-to-a-fixed-date-case.md): Seventeen tasks, one fixed date. Find the critical path and the float, see that the plan lands a week late, compare cutting, parallel work and an extra reviewer, and write Leo the schedule decision.

### Module 4. Estimates and the budget

Estimating in ranges, past projects as a reference, one shared buffer, and a budget over time with a reserve.

- [Estimating in ranges](https://productovi.com/courses/project-management-without-bureaucracy/estimating-in-ranges.md): Three-point estimates that keep the spread: the expected value and standard deviation of each task, how to add several tasks, and how to say a date with its confidence.
- [Past projects as a reference, and one shared buffer](https://productovi.com/courses/project-management-without-bureaucracy/past-projects-and-one-buffer.md): Why padding every task makes the date absurd and still finishes late, how earlier launches correct your optimism, and how one buffer under the lead replaces hidden margins.
- [A budget over time with a reserve](https://productovi.com/courses/project-management-without-bureaucracy/budget-over-time.md): Spread the 600,000 UAH ceiling over the months, keep a contingency reserve for named risks and a management reserve for surprises, and run one earned value check correctly.
- [Case: estimates versus actuals](https://productovi.com/courses/project-management-without-bureaucracy/estimates-vs-actuals-case.md): Use three earlier Klasna launches and the three-point estimates of the chain to tell Leo whether physics can open on 1 February, and how sure you are.

### Module 5. People and stakeholders

Roles, a stakeholder map, influence without authority and a weekly written status.

- [Roles: sponsor, lead, expert, one owner per task](https://productovi.com/courses/project-management-without-bureaucracy/roles-and-one-owner.md): Who decides, who does and who is consulted in a small team where one person holds several roles, and a light responsibility table with exactly one owner per task.
- [The stakeholder map and influence without authority](https://productovi.com/courses/project-management-without-bureaucracy/stakeholder-map.md): Place everyone the launch depends on by how much they can affect it and how much it matters to them, find the stakeholder nobody mapped, and win help from people you cannot direct.
- [The weekly written status and async habits](https://productovi.com/courses/project-management-without-bureaucracy/the-weekly-written-status.md): A five-line status that says where the project really is, honest colours with a forecast and a reason, decisions in writing, and habits for a remote team that works through outages and alerts.
- [Case: the sponsor changes priorities every week](https://productovi.com/courses/project-management-without-bureaucracy/sponsor-changes-priorities-case.md): Leo wants a mobile preview one week and group classes the next. Find what is behind it, show each change's cost in days and money, and ask him to decide in writing.

### Module 6. Risk and quality

Cause, event and consequence; a short register; responses, the pre-mortem and quality built in.

- [Risk, issue, assumption or dependency?](https://productovi.com/courses/project-management-without-bureaucracy/what-is-a-risk.md): Tell a risk from a problem that is already happening, an unchecked assumption and work you are waiting for, and write each risk as cause, event and consequence.
- [A short risk register people actually use](https://productovi.com/courses/project-management-without-bureaucracy/a-short-register.md): Score each risk on written scales (probability, and impact in days or money), give it an owner, a trigger and a next action, and keep the list short enough to review every week.
- [Risk responses, the pre-mortem and built-in quality](https://productovi.com/courses/project-management-without-bureaucracy/responses-premortem-quality.md): Choose a response for each risk (avoid, transfer, reduce, accept or escalate), use opportunities, find hidden risks with a pre-mortem, and check quality while the work is done, not at the end.
- [Case: the launch risk register](https://productovi.com/courses/project-management-without-bureaucracy/launch-risk-register-case.md): Take the team's raw forty-line list, sort out the issues, assumptions and dependencies, score the real risks in days or money, add the missing ones, and send Leo the top five with owners, responses and triggers.

### Module 7. Running the work: changes and re-planning

Change control without a committee, hybrid planning with a fixed date, and re-planning from today.

- [Changes without a committee, and a decision log](https://productovi.com/courses/project-management-without-bureaucracy/changes-without-a-committee.md): Route every change through one door, write a short impact note in days and money, let a named person decide, and record each decision in a few lines.
- [A fixed date with weekly iterations](https://productovi.com/courses/project-management-without-bureaucracy/a-fixed-date-with-iterations.md): Keep the exam date and a few milestones fixed, let scope flex, and run the last weeks in short iterations with a board, limits on work in progress and a weekly demo of working pieces.
- [Re-plan from today](https://productovi.com/courses/project-management-without-bureaucracy/re-plan-from-today.md): Reforecast the remaining work from where the project stands, keep the range, let sunk effort stay out of the choice, and tell the sponsor what changed and what you need.
- [Case: the contractor slips two weeks](https://productovi.com/courses/project-management-without-bureaucracy/contractor-slips-case.md): Three weeks before opening, the checkout contractor needs two more weeks. Re-plan from today, compare cutting scope, adding a developer and moving the opening, and write the decision note to Leo.

### Module 8. Closing and learning

Build, buy or hire, acceptance and handover, the benefits check and a blameless retrospective.

- [Build, buy or hire: contracts by how clear the scope is](https://productovi.com/courses/project-management-without-bureaucracy/build-buy-or-hire.md): Decide per piece of work, pick a fixed price or time and materials by how clear the scope is, write a short request for proposals and pay for accepted work.
- [Acceptance and handover to operations](https://productovi.com/courses/project-management-without-bureaucracy/acceptance-and-handover.md): Run the acceptance checks against the real thing, write known problems down with owners, hand each part to an everyday owner and keep a runbook for outages and alerts.
- [The benefits check and a blameless retrospective](https://productovi.com/courses/project-management-without-bureaucracy/benefits-check-and-retrospective.md): Check the result weeks after launch against the success criteria, run a retrospective on facts and decisions, turn lessons into owned actions and close with a one-page report.
- [Case: the first month against the success criteria](https://productovi.com/courses/project-management-without-bureaucracy/first-month-case.md): Physics opened on time, but bookings are half the target: separate delivery from result, find where the funnel leaked and write the closing report with three actions.