Agile Project Management - Achieve more - Practical Advice - Agile Revolution
It is impossible to overstate the severe set of the challenges caused by the overly administrative linear development approach and specifically the waterfall methodology.
From:
Agile Project Management : Agile Revolution
Waterfall methodology is part of the Linear, scope driven life cycles family of approaches. As it is the manifestation of the command and control organization, it is highly prescriptive. Almost all organizations using the methodology have a similar set pf processes, mostly based on the PMBOK® (more on that later).
Agile is an approach for managing software product development according to the guidelines set in the Agile manifesto. There are several methods and processes for implementing the Agile approach.
..It is 2014 I think to myself, and still businesses believe that having a 110 page project delivery methodology is a prudent approach to plan engineering customer facing projects and products. Failure is written all over the pretty waterfall deployment approach and the numerous templates, work instructions, procedures, processes, decrees and change approval committees.
When I did introduce Agile concepts, I wasn’t surprised that most didn’t recognize the term. Indeed, while the software industry has been undergoing a paradigm shift; other industries’ projects managers and the respective project community, have been ignorant of the benefits imbedded in Agile approaches.....
...The heavy descriptive waterfall methodology they have concocted requires an upfront investment in feasibility assessment and the allocation of project resources to it. Agile approach, the Kanban method with some elements of Scrum, would be a much better solution to their feasibility phase ailments.
For them and for everyone else who thinks that Agile is limited to software I dedicate this guide....
Hence, Agile Project Management : Agile Revolution is for you – project manager, product manager, marketing manager, PMO team, EPMO leader, developer, waterfall traditionalist, VP of engineering, Agile proponent, general manager, consultant, or just someone who wishes to learn more on Agile and how it can be applied outside the software fron tend, client facing industry.
Disclaimer for Agile Project Management : Agile Revolution - in order to align our expectations about what this guide is and what it is not please read carefully the following:
If you’re familiar with the agile manifesto, the 12 principles of agile, how agile software development is unique compared with hardware and system development, how to lead a five-day agile in system and hardware resulting in Kanban agile approach, and how would an Agile system and hardware product development would look like, do not read this guide.
If you think that agile is set of processes and tools rather than a culture where collaboration among other things is paramount. As a result you consider agile to be only an environment with short bursts of development that last for two weeks, with estimated user stories, rather than an all engulfing different approach to development, do not read this book.
If you are convinced that waterfall command-and-control plan driven development is the only methodology and that you love filling in templates writing cumbersome processes, installing yet more - PLEASE don't buy this book.
