Learn · Apply · Deliver
A two-week intensive that goes well past the Scrum framework — hybrid delivery from business case to benefits, the tools you'll be judged on, the metrics executives accept, and a full day on AI with Claude and ChatGPT. Every day ends with a PSM or CSM-style assignment. Taught by a practising delivery lead with over a decade across six industries, not by a full-time trainer.
Why this one
Hybrid delivery, end to end: why projects get funded, how they move through phases, and how governance, risk and schedule sit alongside the sprints.
Every day closes with an assignment written in PSM and CSM exam style. By day ten you have practised the way the certifications actually test you.
You build the Jira project, the workflows, the Confluence space and the Miro boards yourself. Nobody hires a Scrum Master who has only seen screenshots.
One organisation, followed from business case to benefits — with real constraints, an awkward stakeholder and a change nobody asked for.
Velocity, burndown and flow, then KPIs, OKRs and dashboards. Reporting upwards is the skill that separates a Scrum Master from a delivery lead.
Not a token mention, but a complete session on Claude and ChatGPT: how the models work, a reusable prompting toolkit, agents, and an automation you build and keep.
What you'll learn
Everything below is taught live, practised in the tools, and reinforced by a certification-style assignment that same evening.
The framework in full, plus what to do when it stops behaving.
The wider project job that Scrum-only training leaves out.
Turning vague executive ambition into work a team can start on Monday.
Built by you, from empty project to working board — and yours to keep.
Turning delivery into numbers a sponsor will act on.
How the models actually work, a prompting toolkit you reuse, and an automation you build and take with you.
Live sessions, cameras on, small enough that you cannot hide at the back.
The case study
One project, followed from the moment someone decides it is worth funding through to the moment its benefits are signed off.
Patients are waiting hours to be discharged. Beds sit occupied. Nurses, pharmacy and transport each hold a piece of the process and none of them can see the others. That is where the project starts — with a problem, not a backlog.
You walk the whole journey: why the hospital funds this at all rather than the twelve other things competing for the money, and how a business case becomes a charter, a sponsor and a budget. Then how discovery turns ambition into scope, how scope becomes a roadmap and a backlog, and how the work moves through delivery sprint by sprint — with dependencies, risks and a schedule that all still apply.
Then the parts most courses never reach: absorbing a change nobody asked for, reporting to a board that wants numbers rather than ceremonies, and closing the project against the benefits it promised.
It is written, not improvised — the same scenario for every cohort, refined each time it runs.
Why Skillora exists
I kept meeting people who had passed the certification and still couldn't run anything.
I have sat in these classes and I have taught them. The shape is almost always the same: two days, the framework, a workshop exercise, an exam voucher, good luck. People walk out able to define a sprint and unable to plan one. Then they join a team, and the gap shows up in week one.
That gap has been widening. Real delivery was never just the framework — it sits inside funding decisions, business cases, governance, budgets, dependencies, and executives who want a number by Thursday. Teaching Scrum on its own leaves people fluent in the ceremonies and lost in the job.
The ground has shifted again since. AI is now part of how delivery work actually gets done, yet it is either bolted onto the end of a course as a novelty or skipped entirely. Understanding it properly is no longer optional for anyone who wants to stay useful.
So Skillora is the course I would want someone joining my team to have done. Ten days rather than two. A whole project rather than a framework. The real tools, a certification-style assignment every night, and a full day on AI taught seriously. The test I hold it to is simple: if you could not do it on Monday morning, we did not teach it.
Who teaches it
A practitioner who still delivers, teaching the job rather than the framework.
Founder · Instructor
I've spent over a decade delivering projects across hospitality, banking, healthcare and aged care, technology and government — sectors with almost nothing in common, except that the work still has to land on a date somebody has already promised.
That range is why Skillora isn't a Scrum-only course. I've delivered in waterfall, in hybrid and in fully agile teams, and I teach all three, because almost no real organisation runs one of them cleanly. Knowing only one leaves you stranded the moment you change employer.
I teach Agile the way I've had to practise it. The ceremonies matter, but so does what you do when a sprint is failing on day six and someone senior wants a status update — and that is the part these ten days are built around.
Enrol
Introductory price for the first cohort — 20% off. Held for everyone who registers before the dates are announced.
Tell us where you're at and we'll send you the cohort dates and the full day-by-day outline first.