This situation introduces technical uncertainty. In agile, such scenarios are best addressed byspikesorincremental implementationandearly feedback. ThePMI Agile Practice Guide (Section 5.2 Spikes and Experimentation)suggests that uncertain work should be prototyped, tested early, and shown during sprint reviews for feedback and learning.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution)recommends testing high-risk integrations early and iteratively, rather than over-planning.
Option Dis correct: developing, testing, and demonstrating early minimizes risk and aligns with agile principles.
Option Aleans toward waterfall-style planning and over-documentation.
Option Bincorrectly assumes non-functional requirements are less valuable—they’re critical in many systems.
Option Cmay delay necessary architectural work and increase risk.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit