Create the scope of the solution and estimate the effort required to deliver the customer solution. The output of this assessment is an approved Scope statement document. You can use milestones for the implementation project to indicate when each business process is scheduled to be implemented.


Business analyst Business analyst Define project milestones Define project milestones You can define several implementation milestones for your implementation project. When you define the project scope, you can assign business processes to a specific project milestone. Thus, indicating when each business process is scheduled to be implemented. Procedure 1. Click Business process implementation. 2. Click the Milestones tab. 3. Click Add. 4. In the Milestone field, type a value. 5. In the Description field, type a value. 6. Close the page. Notes You can change the sequence in which the milestones are shown. To do so, click Move up or Move down. Start Start Run workshops to define and approve the scope statement Run workshops to define and approve the scope statement Run workshops with the customer, and other relevant parties, to determine the scope of the project and the effort required to realize the project. Use milestones in project? Use milestones in project? Define project scope Define project scope Define which business processes of the relevant solution are in or out of scope for the implementation project. One of these scenarios is applicable: No milestones defined Business processes can have these scope indicators: Not specified - No scoping is done for the business process.In scope - Either the business process itself or one of its child business processes is set to In scope.Out of scope - The business process is set to Out of scope. Milestones defined Business processes can have these scope indicators: Not specified - No scoping is done for the business process.[Milestone] - The business process is in scope for the milestone.In scope - No scoping is done for the business process itself. One of its child business processes is in scope for a milestone. Out of scope - The business process is set to Out of scope. Procedure 1. Click Business process implementation. 2. Click Define scope. 3. In the tree, select 'a node'. 4. Click In scope to open the drop dialog. 5. In the list, find and select the desired record. 6. Click OK. 7. Close the page. Notes Scope changes and related notes are stored in the change history of each business process. Publish scope statement Publish scope statement You can publish a document with the scope statement of a solution. For each milestone, only the business processes that are in scope are added to this document. You can configure the level of detail of the information that is added to the document. You can find and download the published document on the Business process file share workspace, on the Documents tab. Procedure 1. Click Business process implementation. 2. Click Publish. 3. Click Scope statement. 4. On the Publish Scope statement document dialog, define the required settings and click OK. Notes You can also publish a scope statement document from the Scope definition page. To do so, click Publish, Scope statement. On the Publish scope statement document dialog, you can define these settings: Language - If you have defined translations for the solution, select the language in which you want to publish the solution. The elements in your solution that are not translated into this language are published in the original language. You can only publish in another language if this language is defined for the solution itself. So, for example, all content of the solution is translated to a specific language. However, no translation for this language is defined for the solution itself. In this case, you cannot publish in this language.Include business strategy - If this check box is selected, the strategy, as defined for the solution, is added to the document. This includes: Mission statement, goals, and metrics.Include business process descriptions - If this check box is selected, for each business process that is added to the document, the description is also added to the document.Scope and gap summary - If this check box is selected, for each business process that is added to the document, information is given on its scope and gap categorization. For example: This process is out of scope, categorized as fit.Include version number - If this check box is selected, the version number of each element is added to the document.Include change history - If this check box is selected, the change history of each element is added to the document.Number of change history records - You can define the maximum number of change history records that is published for each element. For example, if you enter 3, only the latest three changes to the element are published. End End Publish scope statement? Publish scope statement? Yes No Yes No

Activities

Name Responsible Description

Define project milestones

Business analyst

You can define several implementation milestones for your implementation project. When you define the project scope, you can assign business processes to a specific project milestone. Thus, indicating when each business process is scheduled to be implemented.

Run workshops to define and approve the scope statement

Business analyst

Run workshops with the customer, and other relevant parties, to determine the scope of the project and the effort required to realize the project.

Define project scope

Business analyst

Define which business processes of the relevant solution are in or out of scope for the implementation project.

One of these scenarios is applicable:

  • No milestones defined
    Business processes can have these scope indicators:
    • Not specified - No scoping is done for the business process.
    • In scope - Either the business process itself or one of its child business processes is set to In scope.
    • Out of scope - The business process is set to Out of scope.
  • Milestones defined
    Business processes can have these scope indicators:
    • Not specified - No scoping is done for the business process.
    • [Milestone] - The business process is in scope for the milestone.
    • In scope - No scoping is done for the business process itself. One of its child business processes is in scope for a milestone.
    • Out of scope - The business process is set to Out of scope.

Publish scope statement

Business analyst

You can publish a document with the scope statement of a solution. For each milestone, only the business processes that are in scope are added to this document. You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

Provide feedback