My latest Briefing compilation video covers the basics of Agile Project Management. Keep an eye out later this year for three further briefings on Agile Concepts, Tools, and Frameworks.
Thank you for watching. Please support the channel and all the free content I provide. - Like, comment, and subscribe to the channel. - Why not join my community, free! Sign-up at onlinepmcourses.com/assets440251/the-onlinepmcourses-newsletter/ - And to show maximum appreciation, use the $ Thanks button, under the video, to make a small donation with a highlighted comment.
Oh no not again! Project management has NEVER been defined by a life-cycle. Nobody ever talked about 'traditional' or 'waterfall' project management until some Agilists sought to sell agility in the project space and needed a bogeyman. Agile project management is the adaptation of ALL 4 Values and ALL 12 Principles of the Agile Manifesto to ALL aspects of project management. It makes NO sense to restrict agility to projects with an iterative life-cycle. I and many many others have led agile programmes and projects with varying life-cycles. A final note: not even the Agile Manifesto mentions the word iteration, so it does even define agile software development.
I agree with you on some points and not others. So, I'll take each point on its merits. But before I do, let's keep this civil. 'Oh no not again!' is an inflammatory way to start a comment. 1. 'Project management has NEVER been defined by a life-cycle.' No, that's not how we define project management, but all projects do follow a lifecycle. They don't all follow the same one - and those often presented are nothing more than teaching aids. But yes, each project has a beginning, and end, and therefore something (or things) in the middle.. 2. You are right that the terms 'traditional' or 'waterfall' project management arose in contradistinction to agile. I also consider that many uses of 'waterfall' by agile practitioners are intended as derogatory. Waterfall is a straw dog: What is Waterfall Project Management? ua-cam.com/video/W4lE6ozdjls/v-deo.html 3. If anything originally kicked-off agile, it was the manifesto and its 4 statements (which are not strictly values, but things the authors have 'come to value'.) So, I agree with what I think you are saying. However, the thought that PMs before the manifesto did not value interactions, working solutions, collaboration, and welcoming change, is fanciful. 4. It makes NO sense to restrict agility to projects with an iterative life-cycle.' I think I agree. Although iteration is at the heart of what makes agile really a new way of *doing* things. 5. No, the manifesto does not mention iteration. But I am not sure the manifesto set out to define agile. Tat's not what a manifesto is for. It sets out a number (4 in this case) of things the authors believe are true and intend to uphold. It says nothing about the 'how'. In agile, adaptation, iteration, and incrementally are among the ways we can better adapt to the needs of users and changing demands.
Thank you. By the way: if anyone is reading this and also runs a YT channel, be aware that it is against YT's terms of service to do what this channel's name appears to suggest. It's not something I have done, nor would ever do.
My latest Briefing compilation video covers the basics of Agile Project Management. Keep an eye out later this year for three further briefings on Agile Concepts, Tools, and Frameworks.
Thank you for watching. Please support the channel and all the free content I provide.
- Like, comment, and subscribe to the channel.
- Why not join my community, free! Sign-up at onlinepmcourses.com/assets440251/the-onlinepmcourses-newsletter/
- And to show maximum appreciation, use the $ Thanks button, under the video, to make a small donation with a highlighted comment.
Thank you Mike very much for an excellent video covering all aspects of Agile Project Management. Truly amazing.
You're very welcome.
I frequently hear this term but couldn't quite understand it. great explanation! very helpful, thank you!
I am glad to have helped!
great sharing and great video 🎉
Thank you.
Very nice information sir
Thank you.
Oh no not again! Project management has NEVER been defined by a life-cycle. Nobody ever talked about 'traditional' or 'waterfall' project management until some Agilists sought to sell agility in the project space and needed a bogeyman.
Agile project management is the adaptation of ALL 4 Values and ALL 12 Principles of the Agile Manifesto to ALL aspects of project management.
It makes NO sense to restrict agility to projects with an iterative life-cycle. I and many many others have led agile programmes and projects with varying life-cycles.
A final note: not even the Agile Manifesto mentions the word iteration, so it does even define agile software development.
I agree with you on some points and not others. So, I'll take each point on its merits. But before I do, let's keep this civil. 'Oh no not again!' is an inflammatory way to start a comment.
1. 'Project management has NEVER been defined by a life-cycle.' No, that's not how we define project management, but all projects do follow a lifecycle. They don't all follow the same one - and those often presented are nothing more than teaching aids. But yes, each project has a beginning, and end, and therefore something (or things) in the middle..
2. You are right that the terms 'traditional' or 'waterfall' project management arose in contradistinction to agile. I also consider that many uses of 'waterfall' by agile practitioners are intended as derogatory. Waterfall is a straw dog: What is Waterfall Project Management? ua-cam.com/video/W4lE6ozdjls/v-deo.html
3. If anything originally kicked-off agile, it was the manifesto and its 4 statements (which are not strictly values, but things the authors have 'come to value'.) So, I agree with what I think you are saying. However, the thought that PMs before the manifesto did not value interactions, working solutions, collaboration, and welcoming change, is fanciful.
4. It makes NO sense to restrict agility to projects with an iterative life-cycle.' I think I agree. Although iteration is at the heart of what makes agile really a new way of *doing* things.
5. No, the manifesto does not mention iteration. But I am not sure the manifesto set out to define agile. Tat's not what a manifesto is for. It sets out a number (4 in this case) of things the authors believe are true and intend to uphold. It says nothing about the 'how'. In agile, adaptation, iteration, and incrementally are among the ways we can better adapt to the needs of users and changing demands.
Bravo!
Thank you.
By the way: if anyone is reading this and also runs a YT channel, be aware that it is against YT's terms of service to do what this channel's name appears to suggest.
It's not something I have done, nor would ever do.