Overview

Purpose

The purpose of this section is to provide Project Directors and Project Managers a reference guide for the primary system functions necessary to Plan a project, which consists of the key activities:

1. Model Adoption:  The Project Director and/or Project Manager select the project delivery model (delivery model) most appropriate for their project.  This is an activity that is performed at the beginning of the project.
2. Model Tailoring: The delivery model can be further refined via the inclusion or exclusion of work products within the selected delivery model.  This activity is required to ensure the delivery model selected for the project is tailored to meet the needs and characteristics of an individual project.

This document is not intended to specify or make decisions as to which delivery model is most appropriate for a given project.  This decision should be made by the Project Director and/or Project Manager in consultation with relevant project governance forums.

Pre-Requisites

This document assumes the following has been setup and provisioned:

1. An Organisational Unit has already been created.  For this guide, an Organisational Unit has been setup and named “Training Management”
2. An Assurance Unit (ie Project) has already been created.  For this guide, a project has been setup and named “Project 1: Example Project”
3. Existing Delivery Models have been linked to the Organisational Unit within which the Assurance Unit (Project) has been created, including most recent version of:
   1. Certus3 Agile Model V1.0
   2. Certus3 Foundation Model V4.1
   3. <or your Organisation's own set of delivery models>
4. In this guide the “User” should be a Project Director and/or Project Manager that is tasked with performing the project model adoption and tailoring activity.

Expected Outcomes

By the end of this document, the reader will be able to complete the project initiation function of:

1. Selecting and adopting a delivery model for their project, and
2. Tailoring the delivery model to meet the specific needs and characteristics of their project

Model Adoption

Once logged into the system, the User is presented with three options from the SolutionAmp home screen:

1. Plan
2. Execute, and
3. Report

From the home screen the Plan option should be selected.

From the Plan menu, identify the Instance, Organisation Unit and Project for which the Model Adoption will be performed.  In this example (refer image below) the instance is “Training”, the organisation unit is “Training Management” and the project is “Project 1: Example Project”.

For “Project 1: Example Project” select “Options > Adopt Delivery Model”, shown below

Once selected, the User will be presented with all Delivery Models that are enabled for the organisation unit.  Delivery Models are identified by their Type, which is either Agile or Waterfall.  Note, delivery models that are hybrid are assigned a type of Waterfall. You will see the list of your Organisation's own set of delivery models if available.

The User can select any of the delivery models displayed on this screen.  In this example, Certus3 Foundation Model V4.1 will be selected.  Once selected, the user will be presented with the following screen.  To complete the model adoption, select “Ok”.

Delivery Model Tailoring

Once the system has completed “adopting” the delivery model for the project, the User will be presented with the option to Tailor, Revise, or Change the adopted delivery model, per the screen shown below.

A summary of these tailoring options follows:

1. Tailor: This option enables the User to customise their adopted delivery model to suit the needs and characteristics of their project.
2. Revise: This option enables the User to create a new revision of the adopted model.  The Revise option can be used when a delivery model has previously been tailored and needs to be refreshed and tailored again to meet the emerging needs of the project.
3. Change: This option enables the User to select a different delivery model.  It should be used if the initial model adopted by a project needs to be changed.

Once a delivery model has been selected and adopted for a project, the “Tailor” option will need to be selected to enable the delivery model to be further refined.  Once selected, the User will be presented with the solution domains and work products associated with the adopted delivery model.  By default, all work products are selected and included.  See below screen.

To list all work products for a particular domain, the user can select the “show / hide” button.  Once selected, all work products in that domain including the short description of each will be displayed, per below.

Each work product has additional information that defines it in greater detail.  The User can access this additional detail via the following options:

• Learn More: select this option to provide the detailed definition (long description) of each work product.
• Definition of Done: select this option to provide the detailed criteria that each work product must meet for it to be considered fully complete.  It will also provide the project phase in which the criteria are to be achieved.

Once the User has fully understood each work product, they will decide as to whether it should be included or excluded from the delivery model. If the User decides that a work product is not relevant to the project, it can be excluded by selecting the “include” toggle from this screen.  Refer below.

Once a work product has been excluded, the User is asked to acknowledge the risk associated with removing the work product, accept the consequences of that risk, and provide risk mitigations in place or justification for exclusion.  The exclusion note must be entered to provide the rationale and justification for the work product being excluded.

In this example, the work product is being excluded on the basis that “Operating Model” is not required.  The rationale for the exclusion is that the project is implementing a technical telecommunications upgrade which has no change to the current operating model.  Refer below example of how the User should provide justification of the exclusion.

Mandatory work products have the "include" button greyed out and not active, i.e. they cannot be deselected.

To complete the project tailoring activity the User must review all work products in all domains for the adopted delivery model.  As they are reviewed, any work products that are not required should be excluded ensuring that exclusion justification is entered as per above example.

Once the delivery model tailoring is complete for the project, the User returns to the main menu by selecting the Home icon in the top left of the screen.