Riad AlhammoudProject management| LanganAbu Dhabi, United Arab Emirates
I read about plan driven vs. Change driven projects in pmbok and it is not very clear for me the difference, could I have the elaboration please? Saving Changes...
Sort By:
Alyne Padilla LynchSr Business Process Analyst| Communications and Finance IndustrySacramento, Ca, United States
Hi Riad. Below is a link to an article published on PMI a few years back. Around mid-point, the writer goes into details on predictive (plan-driven), iterative and adaptive (change-driven) project life cycle.
this sounds like a distinction between a predictive or waterfall type lifecycle vs. an adaptive or agile one to me. In the former we do "big heavy planning/requirements/design" up front and expect change to be the exception rather than the rule. In the latter, we do high-level planning up front and then use a rolling wave planning approach which enables us to incorporate changes which is in our customer's best interests.
Kiron
Kiron Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
In a plan-driven approach, you whole focus is on keeping the plan up to date and executing what's in the plan.
In a change-driven approach, your focus is on doing the minimum amount of planning and setting up the environment to quickly react and adapt to changes in priority, scope and resources. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Is not clear because at the end both does not exist. That was widly popularized when business analyst role was created by the IIBA. Here the description I wrote for the IIBA when it was defined (I proposed to include the graphic in the new PMBOK I created at this time but the PMI do not accept):
Plan-driven approaches focus on minimizing up-front uncertainty and ensuring that the solution is fully defined before implementation begins in order to maximize control and minimize risk. These approaches tend to be preferred in situations where requirements
can effectively be defined in advance of implementation, the risk of an incorrect
implementation is unacceptably high, or when managing stakeholder interactions presents significant challenges. The authority to approve requirements typically rests with selected stakeholders and the project sponsor. The project sponsor will have the final
authority to approve solution requirements, but it is common for sponsors to insist that other stakeholders grant their approval before the sponsor will. Waterfall methods of software development and business process re-engineering initiatives are typical examples of plan-driven approaches.
Change-driven approaches focus on rapid delivery of business value in short iterations in return for acceptance of a higher degree of uncertainty regarding the overall delivery
of the solution. These approaches tend to be preferred when taking an exploratory approach to finding the best solution or for incremental improvement of an existing solution. The authority to approve requirements usually rests with a single individual, who is an active participant in the team’s daily activities—others may advise or be informed but may not withhold consent, and the approval process must be completed within a strict time limit. Agile methods of software development, as well as continuous
improvement projects, are typical examples of change-driven approaches.
The performance of this task is dependent on where the selected approach falls on this spectrum. The descriptions below touch on the ends of the spectrum, and hybrid approaches may combine aspects of both. Similar considerations must be taken into account whether the business analyst is selecting or tailoring the approach. Saving Changes...
