EPM5700: Project Execution Plan for IT Centre Development Project

This project execution plan details the development of a new information technology centre in Australia, with an approved budget of $25 million plus an additional $15 million for the latest IT technology to support customer needs for the next five years. The plan outlines key assumptions, including project completion within 187 days and adherence to the approved budget. It employs an agile project methodology to mitigate risks and expedite project completion. The plan covers manual planning aspects such as a project calendar, work breakdown structure (WBS), organization breakdown structure (OBS), and responsibility assignment matrix (RAM), along with lists of tasks, durations, and their logical relationships. It also includes an execution programme, sub-contractor and labour schedules, bill of quantities, cost estimates, and a risk register. Computerized planning elements involve task lists, a project calendar, PDM diagram, Gantt chart, resource lists, cost and budget details, resource schedules, S-curve, resource histogram, and relevant reports for supporting the project execution plan. The project addresses various phases from initiation to closing, ensuring comprehensive management of resources, risks, and deliverables.

Running head: PROJECT MANAGEMENT
Project: Development of a new information technology centre
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Executive Summary
The project mainly reflects on the development of information technology centre in Australia.
It is identified that $25 million is mainly approved for the project exclusive of $15 million for
the latest IT technology. The time that is required for the development of IT centre will be
around 187 days. It is found that the main aim of building the IT centre is to provide the
facility of IT needs to the customers for the coming five years. It is identified that during the
development of IT centre the project manager faces number of challenges and issues which
needs to be resolved. In addition to this, the paper also reflects on the detailed schedule and
budget of the project.

2
PROJECT MANAGEMENT
Table of Contents
1. Project description..............................................................................................................4
2. List of assumptions................................................................................................................4
3.Planning methodology............................................................................................................4
4. Manual planning.....................................................................................................................4
4.1 Project calendar................................................................................................................4
4.2 Work breakdown Structure, organization breakdown structure and responsibility
assignment matrix..................................................................................................................5
4.3 Lists of tasks, durations and their logical relationship...................................................10
4.4 Execution programme....................................................................................................13
4.5 Sub-contractors and required labour schedule...............................................................14
4.6 Bill of quantities and cost estimates as per WBS...........................................................15
4.7 Develop a risk register for this development.................................................................17
5. Computerized planning........................................................................................................19
5.1 List of tasks and WBS....................................................................................................19
4.2 Project calendar..............................................................................................................20
4.3 PDM diagram and Gantt chart.......................................................................................21
Gantt chart............................................................................................................................22
4.4 List and cost of all resources..........................................................................................23
4.5 Cost and detail budget....................................................................................................24
4.6 Resource schedule..........................................................................................................25
4.7 S-curve...........................................................................................................................26
4.8 Histogram for resources.................................................................................................27
4.9 Relevant report for supporting PEP...............................................................................27
Bibliography.............................................................................................................................28

3
PROJECT MANAGEMENT
1. Project description
The paper mainly focuses on the development of a new information technology centre
in Australia. It is found that in order to develop the new information technology centre, the
approved budget is around $25 million. In addition to this, for the latest IT technology,
additional fund of around $15 million is mainly allocated to the project so that for the last
five years the IT centre can be able to support the IT needs of the customers quite effectively.
2. List of assumptions
The assumptions for the project include:
 The project will support IT needs for the next five years
 The development of the IT centre will be completed in 187 days
 The project will get finished within the budget that is approved.
3.Planning methodology
Agile project methodology is mainly selected for the development of the information
system technology centre. It is identified that agile project methodology is mainly selected in
this project for finishing the entire project effectively by taking advantage of automated
testing tools. It is found that with the help of the agile project methodology, the risks as well
as challenges that are associated with the project will be reduced. Moreover, the utilization of
agile project methodology helps in completing the project 37% faster than the average time
that is required.
4. Manual planning
4.1 Project calendar
Start date: Wed 06-06-18

4
PROJECT MANAGEMENT
Finish date: Thu 27-02-19
Weekends: Saturday and Sunday (holiday)
Public holidays: The public holidays are listed below:
Monday 11th June Queen’s birthday
Monday 1st October Labour day
Tuesday 25th December Christmas Day
Wednesday 26 December Boxing day
4.2 Work breakdown Structure, organization breakdown structure and responsibility
assignment matrix
Work breakdown structure
WBS Task Name
0 Development of new information technology centre
1 Project initiation phase
1.1 Analyzing various project requirements
1.2 Development of project plan
1.3 Project feasibility testing
1.4 Milestone 1: Completion of initiation phase
2 Project planning phase
2.1 Scheduling of project task
2.2 Resource estimation
2.3 Resource allocation
2.4 Development of communication plan
2.5 Allocating project team

5
PROJECT MANAGEMENT
2.6 Milestone 2: Completion of planning phase
3 Project designing phase
3.1 Creating blueprint
3.2 Assigning IT needs
3.3 Purchase of necessary equipment’s
3.4 Recruitment of software development team
3.5 Milestone 3: Completion of designing phase
4 Development phase
4.1 Assigning new hardware requirements
4.2 Assigning software requirements
4.3 Development of data warehouse
4.4 Development of network system
4.5 Security System application
4.6 Interconnection between developed overall information system
4.7 Milestone 4: Completion of execution phase
5 Testing Phase
5.1 Testing of the Hardware
5.2 Testing of the software
5.3 Data Warehouse Testing
5.4 Milestone 5: Completion of testing phase
6 Closing Phase
6.1 Post project review
6.2 Stakeholder sign off
6.3 Maintenance of the Data Warehouse

6
PROJECT MANAGEMENT
6.4 Milestone 6: Completion of closure phase'
Organization breakdown structure
Figure 1: Organizational breakdown Structure
(Source: Created by Author)
Responsibility matrix
Analyzing
various project
requirements
Project
manager
Sponsor Contractor Designer Tester Financial
managers
Supervisor
Development
of project plan
A, R I C

7
PROJECT MANAGEMENT
Project
feasibility testing
I C A, R
Scheduling of
project task
A, R I C
Resource
estimation
I C A, R
Resource
allocation
I C A, R
Development
of
communication
plan
A, R I C
Allocating
project team
A, R I C
Creating
blueprint
C I R, A
Assigning IT
needs
Purchase of
necessary
equipment’s
C I R, A
Recruitment of
software
development
team
C I R, A
Assigning new
hardware
C I R, A

8
PROJECT MANAGEMENT
requirements
Assigning
software
requirements
C I R, A
Development
of data
warehouse
C I R, A
Development
of network
system
C I R, A
Security
System
application
C I R, A
Interconnection
between
developed overall
information
system
C I R, A
Testing of the
Hardware
I A, R C
Testing of the
software
I A, R C
Data
Warehouse
Testing
I A, R C

9
PROJECT MANAGEMENT
Post project
review
A, R I C
Stakeholder
sign off
A, R I C
Maintenance of
the Data
Warehouse
A, R I C
4.3 Lists of tasks, durations and their logical relationship
WBS Task Name Duration Start Finish
0
Development of new information
technology centre
187 days
Wed 06-06-
18
Wed 27-02-
19
1 Project initiation phase 17 days
Wed 06-06-
18
Fri 29-06-18
1.1 Analyzing various project requirements 8 days
Wed 06-06-
18
Mon 18-06-
18
1.2 Development of project plan 4 days
Tue 19-06-
18
Fri 22-06-18
1.3 Project feasibility testing 5 days
Mon 25-06-
18
Fri 29-06-18
1.4
Milestone 1: Completion of initiation
phase
0 days Fri 29-06-18 Fri 29-06-18
2 Project planning phase 37 days
Mon 02-07-
18
Tue 21-08-
18
2.1 Scheduling of project task 4 days Mon 02-07- Thu 05-07-

10
PROJECT MANAGEMENT
18 18
2.2 Resource estimation 6 days Fri 06-07-18 Fri 13-07-18
2.3 Resource allocation 9 days
Mon 16-07-
18
Thu 26-07-
18
2.4 Development of communication plan 9 days Fri 27-07-18
Wed 08-08-
18
2.5 Allocating project team 9 days
Thu 09-08-
18
Tue 21-08-
18
2.6
Milestone 2: Completion of planning
phase
0 days
Tue 21-08-
18
Tue 21-08-
18
3 Project designing phase 40 days
Wed 22-08-
18
Wed 17-10-
18
3.1 Creating blueprint 7 days
Wed 22-08-
18
Thu 30-08-
18
3.2 Assigning IT needs 6 days Fri 31-08-18 Fri 07-09-18
3.3 Purchase of necessary equipment’s 7 days
Mon 10-09-
18
Tue 18-09-
18
3.4
Recruitment of software development
team
20 days
Wed 19-09-
18
Wed 17-10-
18
3.5
Milestone 3: Completion of designing
phase
0 days
Wed 17-10-
18
Wed 17-10-
18
4 Development phase 63 days
Thu 18-10-
18
Wed 16-01-
19
4.1 Assigning new hardware requirements 7 days Thu 18-10- Fri 26-10-18

11
PROJECT MANAGEMENT
18
4.2 Assigning software requirements 8 days
Mon 29-10-
18
Wed 07-11-
18
4.3 Development of data warehouse 20 days
Thu 08-11-
18
Wed 05-12-
18
4.4 Development of network system 10 days
Thu 06-12-
18
Wed 19-12-
18
4.5 Security System application 10 days
Thu 20-12-
18
Fri 04-01-19
4.6
Interconnection between developed
overall information system
8 days
Mon 07-01-
19
Wed 16-01-
19
4.7
Milestone 4: Completion of execution
phase
0 days
Wed 16-01-
19
Wed 16-01-
19
5 Testing Phase 19 days
Thu 17-01-
19
Tue 12-02-
19
5.1 Testing of the Hardware 7 days
Thu 17-01-
19
Fri 25-01-19
5.2 Testing of the software 7 days
Mon 28-01-
19
Tue 05-02-
19
5.3 Data Warehouse Testing 5 days
Wed 06-02-
19
Tue 12-02-
19
5.4
Milestone 5: Completion of testing
phase
0 days
Tue 12-02-
19
Tue 12-02-
19
6 Closing Phase 11 days Wed 13-02- Wed 27-02-