Best Practices and Methodology for Electronic Software Distribution and Operating System Provisioning in an On Demand Business

38 Best Practices & Methodology for Electronic Software Distribution & Operating System Provisioning

come to light during the detailed study and planning tasks. The scope of the

Estimated Preliminary Costs addresses:

򐂰 The estimated software costs to the client

򐂰 The estimated hardware costs to the client

򐂰 The estimated implementation and integration costs to the client

򐂰 The timing and order of installation based on a high-level implementation plan

򐂰 The estimated total costs of the system for software, hardware, and services

򐂰 All assumptions used in calculating the costs and schedule

The preliminary costing process is iterative throughout the selection phase and

will be finalized prior to the integration phase of the project.

The development of the Estimated Preliminary Costs can vary widely depending

on the scope and size of the project. The Estimated Preliminary Costs is usually

the initial cost document for the discussion, planning, and acquisition of the new

system. The original numbers will be approximates that are refined as the actual

requirements become known. Early in the Estimated Preliminary Costs task, the

Project Manager should meet with the Client Team Manager and appropriate

client financial personnel to identify and address the basis and purpose of the

numbers. Typically, these numbers are “list” prices from the vendors and illustrate

typical hardware, implementation and support costs. During the final definition

phase and negotiations, these numbers may change significantly.

Agreement

An agreement is the formal definition of the mutual commitments of the delivery

organization performing the service, and the sponsor or requestor of service, and

of a subcontractor and the delivery organization or of other parties, such as

co-contractors. There can be more than two parties to an agreement.

The structure and content of the agreement can vary markedly from project to

project. In particular, agreements with external sponsors and subcontractors are

usually very different from those with internal organizations.

Resources Assigned to Plan

Resources Assigned to Plan

is not a work product but a task to ensure that the

required resources are assigned to the project plan for executing a specified

Change Request.

2.4.6 Develop ESD preliminary deployment plan

The purpose of the Develop ESD preliminary deployment plan activity of the

ESD Change Request process is to review resources and change requirements

for the purpose of developing an initial plan, to develop building blocks of the

Chapter 2. Electronic Software Distribution Change Request process 39

ESD deployment plan, and then to develop an ESD deployment project plan,

which is specific to the approved ESD change order.

Tasks

The following tasks are performed during the Develop ESD Preliminary

Deployment Plan Activity:

򐂰 Reviewing resources and change requirements

This is performed by the Offering Architect and the Delivery Project Manager.

The purpose of this task is to review resource and change requirements, cost

estimates, resource availability and schedules and business information

related to the project management discipline for the purpose of developing an

initial plan.

򐂰 Building change-specific project work plans

This is performed by the Delivery Project Manager.

The purpose of this task is to develop building blocks of the ESD deployment

plan. It is based on the agreement with the client and the external inputs of

overall organizational breakdown structure, the project definition report from

the project’s sponsor. By following cost estimates, resource availability, and

schedules and business information related to the project management

discipline, the building blocks of an ESD deployment plan, including the

definitive cost estimates, are developed.

򐂰 Develop Change Specific ESD Deployment Plans

This is performed by the Offering Architect and the Delivery Project Manager.

The purpose of this task is to develop an ESD deployment plan that is specific

to the approved ESD change order.

Inputs and outputs

The Develop ESD Preliminary Deployment Plan activity of the ESD Change

Request Process may require input from any of the following external processes:

򐂰 Change order

򐂰 Estimated preliminary costs

򐂰 Solution recovery strategy

򐂰 Agreement

򐂰 Organizational breakdown structure

򐂰 Project definition