Workflow Detail: Manage the Scope of the System

Purpose

The purpose of this workflow detail is to:

• Define input to the selection of requirements that are to be included in the current iteration.
• Define the set of features and use cases (or scenarios) that represent some significant, central functionality.
• Define which attributes and traceabilities to maintain.

Although project scope should be managed continuously, the better understanding of system functionality obtained from identifying most actors, use cases, and Supplementary Specifications will allow the system analyst to apply priority, effort, cost, risk values etc., to requirements attributes more accurately, and enables the architect to identify the architecturally significant use cases. An input to Managing Scope not seen in other workflow details of the requirements workflow is the Iteration Plan, developed in parallel by project and development management. The Iteration Plan defines the number and frequency of iterations planned for the release. The scope of the project defined in Managing Scope will have a significant impact on the Iteration Plan as the highest risk elements within scope will be planned for early iterations. Other important outputs from Managing Scope include the initial iteration of the Software Architecture Document and a revised Vision that reflects system analysts and key stakeholders’ better understanding of system functionality and project resources.

How to Staff

The people involved in this workflow detail should all be members of the architecture team.

Work Guidelines

The architecture team will lead a session to discuss how to best prioritize the requirements.