Agile Delivery Without the Jargon
Run iterative delivery in a real organization, one that still has a finance cycle, a legal review and a launch date.
Intermediate with Desmond Whitlark
Plan, run and land a project end to end using the small set of tools that hold up when things go wrong.
A great deal of project management training teaches a framework and its vocabulary. This course teaches the handful of things that actually determine whether a project lands: knowing what is in and out of scope, sequencing work so the risky parts happen early, estimating in a way that survives being questioned, and telling people bad news at the point where it is still cheap.
You bring a live project. It can be a system rollout, an office move, a product launch or a report that four departments have to contribute to. Each week you apply that week's tool to your own project and bring the result back to the cohort for review. By week six you have a plan you have already tested against real stakeholders.
There is no certification exam and no method to memorize. If your organization uses a formal method, this course will make you better at using it, because the underlying judgment is the same.
Applications for the Q4 2026 cohort close on Friday 18 September 2026. We reply to every application within two business days.
Delivery planning and workload design
You bring a live project. By the last week you have a plan for it that survives contact with your actual stakeholders.
Each module has one live session and one piece of practice applied to your own work.
Writing what the project will and will not deliver in language a sponsor will agree to in writing, and what to do when the boundary moves.
Ordering work so that the parts most likely to break happen while you still have time to react, rather than in the final fortnight.
Producing estimates you can explain, showing uncertainty honestly, and holding a range when somebody asks for a single date.
Keeping a short list of things that would genuinely hurt, with an owner and a trigger, instead of a long document nobody opens.
Mapping who needs what and when, and delivering a slipping date early enough that it is still a decision rather than an announcement.
Getting to genuinely finished, handing over to the people who will live with the result, and running a review that changes the next project.
By the last session of Project Delivery Fundamentals you will have practised each of these on your own work, not on a case study.
Planning, sequencing and landing work when the deadline is real and the resources are fixed.
Run iterative delivery in a real organization, one that still has a finance cycle, a legal review and a launch date.
Intermediate with Desmond Whitlark