PMP Practice: Determine risk management options

In a hybrid project where predictive and agile workstreams must integrate, risk management requires tailoring approaches to respect both methodologies while maintaining project viability. The scenario presents a genuine integration risk with valid concerns from both sides: the compliance architect correctly identifies that premature development could create costly rework affecting regulatory timelines, while the team recognizes that delaying technical validation creates its own risk of discovering integration failures too late. The project manager's role is to facilitate a solution that addresses the technical risk without forcing one methodology to completely override the other. Creating a lightweight integration test allows technical validation to occur early while respecting the need for formal specifications. This collaborative approach leverages agile's bias toward early experimentation while maintaining predictive governance where regulations require it. The closing fact that both workstreams are on critical paths and contingency is already being consumed makes finding a middle path essential rather than accepting delays or uncontrolled rework. Updating both the risk register and sprint backlog ensures both workstreams remain coordinated.

**Why not B:** Pausing agile sprints to wait for complete predictive specifications defeats the purpose of a hybrid approach and creates its own risk by preventing early user feedback on the UI, which the product owner has identified as critical for adoption. This choice inappropriately applies predictive thinking to the entire project rather than managing the integration point between methodologies.

**Why not C:** Proceeding with full parallel work while accepting potential rework is particularly problematic given the scenario's closing facts: both workstreams are on critical paths and 15% of contingency is already used. The compliance architect's warning about three-month delays from rework is specific and credible. Accepting this level of rework risk without attempting to mitigate it first represents poor risk management when a collaborative solution is available.

**Why not D:** Escalating immediately skips the project manager's responsibility to facilitate solutions when methodological conflicts arise in hybrid projects. The scenario does not indicate that Dakota lacks authority to coordinate between workstreams or that the decision requires sponsor-level tradeoffs. Escalation would be appropriate if the teams cannot reach agreement after facilitation, but the PM should attempt collaborative problem-solving first. This choice represents premature escalation, a common PM misjudgment.