Business Issue or Requirement Scoping

To successfully address business issues requires an approach that ensures that all details related to the needs are clearly defined, the scope is fully understood by all, a common language is used, and most importantly everyone is on the same page and has the same level of understanding in terms of scope and deliverables.

Any confusion at this stage will almost certainly cause costs overrun, and mismatch in delivery.

We have a tried and test approach to gathering requirements and scoping the extent of work.

We approach this task by establishing a ‘Process Inventory’, and by defining a ‘common language of process’ to describe the issue and/or requirement.

This we provide in a Statement of Work document deliverable which then provides a common project vocabulary and reference through the life of the project.

The deliverables includes:

• Defining what a process means in your business context, and how many you have within scope.
• Clarifying each process by level of abstraction from Organisation, Department, Function, Process to Procedure of work by naming and sequencing them.
• Providing a brief one-line purpose statement (what the process is designed to do), including the start and end points of the process.
• Define the organisational positions involved in the process (names of key people).
• Identifying any key IT systems in the process.
• Identify which processes are in scope, and in what order they should be analysed.
• Estimation of effort, approach and cost to analyse and provide recommendations.