CHAPTER 8: CHANGE
Agile says:
Agile expects changes and is geared to accept them where they have sufficient impact or benefit, until late in the development cycle.
PM4A says:
PM4A regards change as a problem and builds a big procedure to review them, involving the client in decisions about change.
The difference matters because …
If requirements are not fully known at the outset, a lot of time and effort can be used up by PM4A going through formal procedures. The less well-defined the requirements, the greater the threat of bringing a PM4A project to its knees.
PM4A’s Change chapter also covers version control, a subject not touched by Agile. Without version control, a project will soon get into serious problems, such as ‘Who has what?’, ‘Are ...
Get Adaptable Project Management – A combination of Agile and Project Management for All (PM4A) now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
