Optional: What are "Agile" and "Waterfall" approaches and how do they differ?
This video is a primer, aimed at people who have heard the terms "agile" and "waterfall" but don't know what they mean. It's not a detailed "compare" and "contrast" exercise for those already familiar with the terms.
Agile is usually used in the context of software development and that's its origins, with the Agile Manifesto. So if software development is part of your project, it useful to understand what the terms mean.
I have increasingly heard people talking about "agile business change" but it's quite a loose use use of the term "agile", in a similar way that people bandy about the term "lean".
I am not knocking the idea of agile business change. Indeed, depending what is meant, it probably has a lot in common with the ideas in the course, But if in doubt about what is meant by "agile, look up the Agile Manifesto.
There are two main ways of managing agile projects at a detailed level:
If you want to understand the essence of scrum then this YouTube video of one of it's originators, Ken Schwaber, giving a talk at Google is a great explanation of the essence/intention of Scrum, without a lot of process-police stuff that it seems too have picked up over the last few years. Ken's talk is about an hour but it's good value.
If you want to understand Kanban, check out my next video in this course.