A company must implement a new regulation. The government has specified the date when the regulation will be enforced but has only provided high-level information on the regulation's requirements. Therefore, changes in definitions are to be expected due to uncertainty.
Which life cycle should the project manager use for this project?
An iterative execution strategy is the most suitable for this project. Given the high-level nature of the requirements and the expected changes due to uncertainty, an iterative approach allows the project to adjust and refine the requirements gradually as more information becomes available. This strategy is effective in dealing with evolving requirements while working towards a fixed implementation date.
I would go with D. Because there is a already a date specified to enforce the regulation and also because the regulation requirements are only known at a very high level.
I believe B (iterative) is the best approach here. You are given a release date to meet the regulation (single delivery), but the scope is unclear, so you keep correcting the scope and iterating on it until it is correct or meets the law.
if the iteration is 2 weeks or 4 weeks, then who would review the increment to give feedback, we cant expect the government to bring clarity in 2 weeks or 4 weeks right? then it cant be iterative
Agile up to the date, then predictive
C. An agile execution strategy
A Hybrid Approach is often applied as follows: Predictive for clear/known parts and Adaptive for unclear part (uncertainty). With the given information in the Questions, we just know that "there is uncertainty", "a Date/Deadline is fixed". There is NO INFORMATION OR HINT regarding "Known parts" ==> Is there any other reason for option D????? ==> Should C best matched with the given information?
I found the hint and convincible reason myself for option D. It said "Company must implement REGULATION". Regulation requirement is a must, we must adhere to it => a hint of FIXED SCOPE. And Fixed Date => We cannot fully use Agile where SCOPE is not fixed. ==> We just can use some components of Agile to deal with uncertainty. ==> HYBRID Approach is best option now. (Really tricky question)
C an Agile makes sense here
the uncertanty brings the need of using agile aproach
Chose D. Partly because its government and they tend to be more waterfall type, but with the new unclear requirement, they can implement more agile up to a certain point. Second, since there is some guidance out there, prefer to be hybrid.
D. Since the scenario tell that its government regulation it should be predictive but since stated in scenario that changes might happen, approach should be embedded with agile. So hybrid (Predictive + Agile).
Since B and C are similar, i would choose D as answer.
D. A hybrid execution strategy
Agile olmalı çünkü en üst düzeyde gereksinimler belirli ve çoğu da sonradan belirlenecek.
I would go with C. As the date of enforcement is not directly related to any project dates. But changing requirements definitely calls for Agility
D is my answer
Hybrid
Answer is D. There is already a set and enforced date, but the requirements are subject to change.
Regulation is a predictive life cycle, and uncertain is Agile life cycle
la bonne reponse c'est: B d'apres le mindset PMI
I would go with B.
D. A hybrid execution strategy
In my opinion I believe the iterative approach (B) will best suit this situation considering the fact that they were provided high level info on the regulation and need immediate execution due to the importance of the regulationA company must implement a new regulation. The government has specified the date when the regulation will be enforced but has only provided high-level information on the regulation's requirements.
I would go with C. due to uncertainty
I believe option D is better. Option B assumes that regulatory details will constantly be released until the deadline.
Option B is correct Since the regulation’s details are still unclear, an iterative approach allows the team to refine their understanding and implementation in cycles as more guidance emerges. Others not suitable because : Predictive (A): Rigid for changing rules Agile (C): For customer products, not compliance Hybrid (D): Needs stable elements (none here)