Project Scoping Artefacts

Q2: What artefact will the project use for determining the scope of the project?

There are a variety of artefacts that Project teams use for project scoping – very similar in procedure but with characteristics that may be more suited to an particular project. They represent supported capability models, or existing services artefacts.

Value Chains: [Using Value Chains for Project Scoping]

A presentation of supported Business Processes grouped into function areas for insurance lines of business. Each Value Chain lists a partial subset of the recommended Insurance Process Model, decomposed into phases in the lifecycle of a business area, e.g. Claims management.

Project teams who will be Process modelling use the Value Chains to help them target the most useful high-level business processes supported in the Analysis Process Model.

Other: Existing Services and or data structures. [Project scoping for quickstart service design]

Existing Services, including the data used in the services, can provide a starting point for bottom-up service design, and a specific scope for the project. Project Teams taking a bottom-up approach may map to existing IPS Services and extend their model using IPS content, or may map only to the data definitions in the IPS Service models, and retain their existing service definitions.