Scope Modelling

Definition

Scope Modelling is a technique used to define the boundaries of analysis and the solution, making explicit what is included and excluded. It prevents scope creep by creating a shared, visible agreement on what the initiative covers. Common scope models include context diagrams, in-scope and out-of-scope lists, feature scope maps, and product scope boundaries.

Inputs

• Business objectives and the need or problem being addressed
• Stakeholder input on intended coverage
• Constraints, dependencies, and organizational boundaries
• Prior requirements documentation or initiative charter

Outputs

• A context diagram or scope boundary model
• An agreed in-scope and out-of-scope list
• A shared reference for evaluating change requests during delivery
• Inputs to requirements elicitation planning and estimation

When to Use

• Project initiation before requirements elicitation begins
• When multiple teams or systems are involved and boundaries are ambiguous
• During change control discussions to evaluate whether a request is in or out of scope
• When stakeholders have misaligned expectations about what the initiative will deliver

When Not to Use

• Very small, single-team initiatives where scope is obvious and agreed informally
• When scope is contractually fixed and no further definition is needed
• Late in delivery when scope has already been agreed and work is in progress