Why

This page is focused on project level processes, but our Consultants also have experience and work at corporate architectural level business processes and re-engineering.

This defines the area of change in Business terms, providing an end-to-end picture into which the System changes fit. It allows the Business to understand where the systems impact their jobs and processes and where they need to adapt.

This step, if carried out properly will identify areas of change in time for them to be planned and implemented effectively. This is vital to ensure the business readiness for the system when it is delivered.

This can act as the basis to identify if changes are additional to the scope agreed, or are amendments to it and have also provided a good basis around which third party contracts for services related to the systems can be based.

What

This requires end-to-end reviews of the Business Processes where there is any overlap with the project.

The business processes will be documented to meet the Projects standards e.g. using UML sytax, LSDM, SSADM. Use Cases and Activity diagrams can be provided as part of this task as an aid for gap analysis and User testing

How

This will be determined with you, but typically:

� Identify the main processes touched or created by the project

� Identify the stakeholders

� Work through the relevant end to end processes e.g. using facilitated workshops

� Identify steps and rules for the main processes

� Identify exception processing

� Identify actions, issues, risks

� Provide documentation (including Business Process models/diagrams e.g. Use Cases, Activity diagrams)

The changes identified through this process are reviewed to determine how they will be dealt with e.g. as a change to the business process/operation, an exception,
work around, system change (and in what time period/phase).