Where projects end and operations begin, what a project manager is accountable for, and the four phases every project moves through.
Four ways to organize a project's work — Waterfall, Agile, Lean, Six Sigma — what each trades away, and how to pick between them.
Why the same PM title means very different things depending on how the company around it is organized, plus what a PMO does.
The short document that turns "someone had an idea" into a project with a sponsor, a scope, and boundaries.
Turning "make it better" into a scope statement, a measurable SMART goal, and a deadline everyone actually agreed to.
Who can make or break a project, how to map them with a RACI chart, and how to prioritize attention with the power/interest grid.
Turning an approved charter into a list of concrete work, in the right order, with checkpoints along the way — milestones, the Work Breakdown Structure, and task sequencing.
Why a single-number estimate is almost always wrong — the planning fallacy, three-point (PERT) estimating, and sizing buffers without just padding every task.
Which chain of tasks actually controls the finish date, how to compute it by hand, and why a valid schedule can still fail without enough people to run it.
Turning a schedule of tasks into a dollar figure a sponsor can actually approve — direct vs. indirect costs, CAPEX vs. OPEX, and contingency vs. management reserves.
How a project brings in outside help without getting burned on scope, cost, or fairness — RFPs, contract types, the statement of work, and ethical sourcing.
Finding the things that could derail a project before they do — the risk register, the probability/impact matrix, and choosing avoid/mitigate/transfer/accept.
Turning "we should keep people updated" into a concrete plan — push vs. pull vs. interactive communication, and matching frequency to each audience.
Four different tools for answering "are we on track?" for four different audiences — Gantt charts, roadmaps, burndown charts, and status reports.
What happens when the plan meets a request to change it, a piece that's out of your control, or a problem too big to fix alone — change control, external dependencies, and escalation.
Quality isn't "as polished as possible" — it's meeting the requirements that were actually agreed on. QA vs. QC, the cost of quality, DMAIC, and user acceptance testing.
Using numbers to catch a problem before it shows up in the schedule — leading vs. lagging indicators, vanity metrics, and Goodhart's law.
Most project managers lead people who don't report to them — Tuckman's stages of team development, influencing without authority, and task vs. relationship conflict.
A room full of people is one of the most expensive things a project spends — which meetings earn their place, and how to run a retrospective that surfaces real problems, not blame.
Shipping the deliverable and finishing the project aren't the same thing — the closure checklist, closeout reports, and the difference between output and outcome.
Agile is a set of values, not a checklist — the Manifesto's four values, Agile as a mindset vs. a specific method, and when it's actually the right fit.
The most widely adopted Agile framework, and notably, one with no "project manager" role at all — Scrum's three roles, three artifacts, and five events.
Scrum isn't the only way to practice Agile — Kanban's continuous flow and WIP limits, XP's engineering practices, and Lean's focus on eliminating waste.
Scrum was designed for one small team — here's what happens once a product needs a dozen of them. Scrum of Scrums, LeSS, SAFe, and the Spotify model compared.
Negotiating isn't a rare event on a project — positions vs. interests, BATNA, and the four elements of principled negotiation.