Project Delivery Fundamentals
Plan, run and land a project end to end using the small set of tools that hold up when things go wrong.
Beginner with Desmond Whitlark
Run iterative delivery in a real organization, one that still has a finance cycle, a legal review and a launch date.
Iterative delivery works. What usually fails is the attempt to run it inside an organization that budgets annually, contracts on fixed scope and expects a date in a board pack. Teams end up performing the ceremonies while making all the real decisions the old way.
This course is about that gap. You will learn to slice work so that each slice is genuinely shippable, to forecast from what your team has actually done rather than from optimism, and to have the conversation with finance and legal in terms they can use. It assumes you have already worked in an iterative team and found the friction.
The vocabulary is kept deliberately plain. If your organization uses a particular framework, everything here maps onto it, but you will not be asked to memorize a glossary.
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.
Diagnosing where your team performs iteration while deciding sequentially, and which of your rituals is now pure cost.
Cutting work into slices that deliver something a user can meet, rather than layers that are only useful once the last one lands.
Using your team's actual throughput to produce a forecast, and presenting it as a range without being talked into a single date.
Framing iterative work inside an annual budget cycle and a contract that expects fixed scope, in language those teams can approve.
Running toward a date that genuinely cannot move by managing what is in the release rather than pretending the date is soft.
Building legal, security and accessibility review into the flow of work rather than into a queue at the end.
Choosing the two practices worth defending, retiring the ones that are theatre, and agreeing how the team will keep adjusting.
By the last session of Agile Delivery Without the Jargon 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.
Plan, run and land a project end to end using the small set of tools that hold up when things go wrong.
Beginner with Desmond Whitlark