In the Power/Interest Grid, stakeholders with high interest but medium/low power (often called ‘Keep Satisfied’) should be kept adequately satisfied. They care about the outcome but cannot single-handedly derail the project. Regular updates and checking for concerns are appropriate to ensure they remain supportive without requiring intensive management.

A good analyst probes to understand the root need. The statement is a solution (a fast report). The analyst should ask ‘why’ to uncover the underlying business problem (e.g., ‘We need to serve customers on the phone without delay’). This ensures the true requirement is understood and may reveal alternative solutions.

Solution scope defines the capabilities, features, and processes of the solution itself. Business goals are part of the business need and problem statement, which are inputs to defining scope but are not contained within the solution scope. The other options (integrations, UI, and associated training) are typical components of what the solution will include or deliver.

Requirements validation ensures requirements and models are of sufficient quality. Identified defects should be corrected before sign-off to ensure the baseline is accurate. Re-circulating the corrected model for a final, focused review is a standard practice to gain formal confirmation that the errors have been properly addressed.

The core purpose of requirements traceability is to link requirements back to their source (business objectives, stakeholder needs) and forward to solution components. This allows for impact analysis of changes and, crucially, provides a mechanism to verify that the final delivered solution fulfills the original business needs it was meant to address.

Document Analysis is the systematic examination of existing materials (like system manuals, procedures, contracts) to extract requirements, identify gaps, or understand current state processes. It is the most direct and appropriate technique for deriving requirements from an existing document, as opposed to techniques that generate new ideas from stakeholders directly.

Mandatory requirements (also known as constraints or ‘must-haves’) define the minimum acceptable solution. If a solution fails to meet a true mandatory requirement, it is not viable, regardless of its score on other criteria. The analyst must disqualify it and focus evaluation on the remaining options that meet all mandatory conditions.

Requirements Life Cycle Management is concerned with managing requirements from inception to retirement. A core task within this knowledge area is ‘Assess Requirements Changes,’ which involves analyzing the impact of a proposed change on existing requirements, the solution scope, and stakeholders—exactly what is described in the scenario.

While reprioritization is normal in Agile, constant, disruptive shifts often indicate a lack of strategic direction. If the product owner has a clear vision and roadmap, priorities should shift in a more predictable, goal-oriented manner. The BA can help by facilitating conversations to define or clarify the product vision, which provides context for prioritization decisions.

In the Power/Interest Grid, stakeholders with high interest but medium/low power (often called ‘Keep Satisfied’) should be kept adequately satisfied. They care about the outcome but cannot single-handedly derail the project. Regular updates and checking for concerns are appropriate to ensure they remain supportive without requiring intensive management.0