Agile Project Management: Agile Revolution, Beyond Software Limits
A Practical Guide to Implementing Agile Outside Software Development (Agile Business Leadership, Book 4)
Failed to add items
Add to Cart failed.
Add to Wish List failed.
Remove from wish list failed.
Follow podcast failed
Unfollow podcast failed
Buy Now for $9.34
No default payment method selected.
We are sorry. We are not allowed to sell this product with the selected payment method
-
Narrated by:
-
Barbara H. Scott
-
Written by:
-
Michael Nir
About this listen
Agile Project Management - Achieve More - Practical Advice - Agile Revolution
It is impossible to overstate the severe set of 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 lifecycles 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 of 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 planning 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, project managers, and the respective project community have been ignorant of the benefits embedded 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....
©2014 Sapir Consulting (P)2015 Sapir Consulting