A member of the development team is working on a prioritized non-functional requirement involving integrating with a 3rd party system. This integration has not been done before on the project. What…

Question

Options

• ADevelop and document a detailed architectural design, peer review with the development team,
• BDevelop the functional requirements of the solution first before any non-functional requirement, as
• CDiscuss the integration requirement with the product owner and negotiate it to be lower on the
• DDevelop and test the implementation approach and demonstrate it at the next sprint review to

• A
  8% (4)
• B
  18% (9)
• C
  4% (2)
• D
  69% (34)

Explanation

When a team encounters a novel integration that has never been done before, the agile approach is to treat it as an uncertainty that requires exploration - often called a 'spike.' Option D is correct because developing and testing the implementation approach (a proof of concept) and then demonstrating it at the next sprint review validates feasibility early, reduces risk, and provides the team and stakeholders with concrete evidence before committing fully. Option A is too waterfall-style (detailed upfront architectural design). Option B contradicts agile values - non-functional requirements are legitimate and already prioritized. Option C would override a prioritization decision that the product owner has already made.

No community discussion yet for this question.