Project Requirements Process R069

Blog: Biz-Performance, David Brown

R069 – Agree Initial Enterprise Business Model

DEFINITION

Consolidate, agree and sign off the results from the project modelling workshops.

SUMMARY

Conduct a quality review of the base enterprise business model. Present the final model to the project sponsor and key management and obtain their approval. Ensure that proper control and maintenance procedures are in place.

PATH PLANNING GUIDANCE

This process is normal practice in a Project Model approach.

DEPENDENCIES

Prerequisites (Finish-Finish):

Create and maintain enterprise business model (R065)
Conduct initial process-modelling workshops (R068)

Dependent procedures (Finish-Finish):

System Vision: functions data, volumes, performance, scope, objectives, boundaries / interfaces, technical goals, timescales (R070)
Identify requirements (R100)
Select business processes from reference model (D354)
Gap Analysis – existing systems v. requirements (R120)
Gap Analysis – requirements v. target solution (R125)

RECEIVABLES

Base enterprise business model

DELIVERABLES

Agreement to model

TOOLS

(none)

DETAILED DESCRIPTION OF TASKS

Review the base enterprise business model to ensure that it meets specifications for further project development. This should include:

appropriate textual and graphical views and documentation
conversion of customer transactions to standard and format suitable for the target package (if any)
customer specific requirements and interfaces
future company-internal processes
standard and clear navigation between sub-models.

Once the internal quality review has been conducted, present the initial business model to the project sponsor and key management to obtain their sign-off.

Ensure that the appropriate measures have been put in place to maintain the business models.