Agile Project Management Crash Course in the AI Era

Somewhere in your organisation there is a plan. It was drawn carefully, by people who knew what they were doing. And the ground it was drawn for has already changed.

That gap is where most work goes wrong. Not through laziness, and not through bad planning. Through planning that could not bend when the answer turned out to be different.

Agile is the response to that problem. It is not a tool, and it is not a personality. It is a way of working that assumes you will learn something after you start.

This course teaches it from nothing.

You do not need to have worked on an agile team. You do not need to know what a sprint is, or a backlog, or a story point. Every one of those words is defined the moment it is first used, in plain language, before anything is built on top of it.

Sixteen short lessons take you through it in order. What agile actually means and where it came from. How a sprint works and why its length never moves. Who decides what, and the three decisions every team needs owned. How large ideas are cut into pieces a team can finish. Why teams size work in points rather than hours. How a sprint is planned honestly, run daily, tracked without flattery, protected from mid cycle requests, demonstrated, and improved.

Each lesson corrects the misunderstanding people usually arrive with. Agile does not mean working without a plan. A sprint is not a deadline to cram work into. Velocity is not a performance score. Points are not secret hours. The scrum master is not the boss.

Every lesson stands completely alone. There is no numbering, and no lesson refers to another. Watch one, use it tomorrow, and come back when you want the next.

What you keep. A pack of one hundred and twenty eight AI prompts, one group for each idea in the course, written for the work in front of you rather than for a textbook example. Three worksheets. A nine tab tracker. A glossary of every term. A reading list of eighteen sources, every one checked. And a page tracing every definition in the course back to its primary source, so you can check any claim made here.

On accuracy. Definitions were checked against the framework itself, not written from memory. Where a practice is common but not part of the framework, this course says so. Where an example uses a shorter timebox than the maximum, it says that too.

This will not make every project succeed. Nothing does. What it will do is remove the confusion that makes people freeze, so you know what the words mean, what each part is for, and what to do on a Monday morning when the plan meets the ground.