Deployment Phase Schedule

PM Milestone Project Management Templates

PM Milestone Project Management Templates

Get Instant Access

Deployment is the final phase in the cyclic methodology. During this phase, the system is prepared to be handed over to the user.

Enter the following into the schedule:

Name

Start Date

Duration

Resources

Predecessors

99 (0)

Deployment

04/13/00

87

100 (1)

Beta Testing

04/13/00

101

Roll Out

04/13/00

100

102 (2)

Move site and server components to production server

04/14/00

1 day

Logistics[50%]

83,86,93,95,96

Name

Start Date

Duration

Resources

Predecessors

103

Determine roll out schedule

04/13/00

Management

Educator[33%], Logistics[50%], End Users [50%], Client

Management [50%]

59FS-20days

For the system to be prepared for handover, it is quite obvious that development must have been completed. However, as much of this phase is concerned with planning for the handover, there is no reason why it cannot start while development is still taking place: the design and functionality of the system are known, and the duration of development can be estimated. This is why the deployment and development phases overlap.

It is quite plain to see why there are so many predecessors for goal 102 - obviously, the components cannot be moved to the production server unless they are completed, tested and debugged.

Name

Start Date

Duration

Resources

Predecessors

104

Communicate roll out plan to users

04/18/00

10 days

Educator[25%], Logistics, Project Manager [50%]

103

105

Conduct User Training

04/18/00

10 days

Educator[25%]

103

106

Release internal PR

04/18/00

10 days

Component Manager 1, Developer 1a, Developer 1b, Component Manager 2, Developer 2a, Developer 2b, Component Manager 3, Developer 3a, Developer 3b

103

Name

Start Date

Duration

Resources

Predecessors

107

Rollout

Mon 05/08/00

Management,

Project Manager,

Educator,

Logistics,

Component

Manager 1,

Component

Manager 2,

Component

Manager 3

104,105,106, 112

The users will obviously need to know when they are going to get their system, so you must let them know the rollout schedule - this will also help them understand why they cannot have their system yesterday!

It is imperative that the users understand how to use the system before it goes live: not only will this save money in the long run, but it also means that the time taken for the system to become operative and efficient will be shortened.

It is also important to publicize the release of the system internally. Not only can this generate interest in the system, but it might also generate interest in the project team, meaning that (if the project is successful!) their skills are in demand.

The milestone for this step of the deployment phase is the actual handover of the system to the users, otherwise known as rollout. It is clear that this is dependent on all other goals preceding it being completed and all milestones reached.

Name

Start Date

Duration

Resources

Predecessors

108 (1)

Support

04/13/00

100

109 (2)

Determine what support resources are needed

04/13/00

4 days

Management [50%], Product Management [33%], Project Manager [75%]

57

Name

Start Date

Duration

Resources Predecessors

110

Make appropriate

Wed

5 days

Educator [25%], 109

staffing changes

04/19/00

End Users,

Client

Management,

Product

Management

[50%], Project

Manager [50%]

Although after rollout the project may have officially ended, it is by no means over. It is crucial that the users receive support and guidance in how to use the system, especially if it radically alters business processes or introduces totally new ways of doing things. This step ascertains what support the user will need and makes sure that there are people available to provide it. The level of resources needed relates directly to the documentation of Support Requirements that took place in the physical design stage of the design phase.

Name

Start Date

Duration

Resources

Predecessors

111

Determine method that users will attain support

Wed 04/26/00

3 days

Educator [33%], End Users, Client

Management, Product Management [75%], Project Manager [50%]

110

112

Determine support process

05/02/00

5 days

Educator, End Users, Client

Management, Product Management, Project Manager

111,104,105, 106

113

Support goes live

Mon 05/08/00

0 days

107SS,112

It is important to know how users will seek support: this could be by telephone, by email, over the Internet, or even by post(!). If it is decided that there will be one main way in which users seek support, most of the focus will be given to this; however, the other methods available should not be ignored.

It should also be determined how the process of support takes place - this could include, for example, the description of a hierarchy of support, where increasingly technical queries are passed up the hierarchy to people who are able to deal with them. This process can only be determined after user training has been carried out and the rollout plan communicated to them: before this point, it is unlikely that the users will realize that they may need support with the system.

This phase ends with another milestone - support goes live on the same day as rollout. The Project 98 schedule for the deployment phase will look as follows:

m

Microsoft Project - This is the schedule that works!

_|D| X|

@ File Edit View Insert Format Tools Project Window Help .Sjiij

Dia say ä % e ^ % # # | @ © | q & » -s ®

♦ ♦ « = ++ Arial - 8 - B I U

m m =■ All Tasks - V=

1

o

Task Name

Duration

Start

Finish

Predecessors

Resource Names

_

99

El Deployment

2H days

Thu 04fl]/00

Mon 05(53(00

IT

100

Beta Testing

10 days

Thu 04/13/00

Wed 04/26/00

Educator .Product Management

101

B Roll Out

1H days

Thu 04(27(00

Mon 05(22(00

100

102

Move site and server components to product

1 day

Thu 04/27/00

Thu 04/27/00

83,86,93,95,96

Logistics[50%]

103

Determine roll out schedule

3 days

Thu 04/27/00

Mon 05/01 /D0

59FS-20 days

Product Management[33%],Edi.

104

Communicate roll out plan to users

10 days

Tue 05/02/00

Mon 05/15/00

103

Educator[25%] .Logistics .Projec

K >

105

Conduct User Training

10 days

Tue 05/02/00

Mon 05/15/00

103

Educator[25%]

V

106

Release internal PR

10 days

Tue 05/02/00

Mon 05/15/00

103

Component Manager 1 .Develop

fT>

107

Rollout

0 days

Mon 05/22/00

Mon 05/22/00

104,1 05,106,112

Product Management .Project M

108

B Support

1H days

Thu 04(27(00

Mon 05(22(00

100

109

Determine what support resources are need

4 days

Thu 04/27/00

Tue 05/02/00

57

Educator[33%],End Users[50%

110

Make appropriate staffing changes

5 days

Wed 05/03/00

Tue 05/09/00

109

Educator[25%],End Users .Clien

111

Determine method that users will attain suppt

3 days

Wed 05/10/00

Fri 05/12/00

110

Educator[33%],End Users .Clien

112

Determine support process

5 days

Tue 05/16/00

Mon 05/22/00

111,1 04,105,106

Educator .End Users .Client Man

113

Support goes live

0 days

Mon 05/22/00

Mon 05/22/00

107SS.112

< I I -I

Ready_NUM_|

The Gantt chart for deployment should look like the following:

The Gantt chart for deployment should look like the following:

Was this article helpful?

0 0
Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment