Developing a New IT Centre in Australia: A Project Management Plan

Verified

Added on  2023/06/10

|30
|3327
|280
Project
AI Summary
This project focuses on the development of a new information technology centre in Australia with a budget of $25 million, plus an additional $15 million for IT technology. It outlines the assumptions made during the project, including the expectation that the centre will support all IT needs for the coming years, the project will be completed in approximately 182 days, and the allocated budget will be sufficient. The project utilizes the agile project management methodology to ensure timely completion and to mitigate potential issues. The manual planning section details the project calendar, work breakdown structure (WBS), organizational breakdown structure (OBS), responsibility assignment matrix (RAM), lists of tasks with durations and logical relationships, an execution programme, sub-contractor and labour schedules, bill of quantities and cost estimation, and a risk register. Computerized planning includes task lists, WBS, a project calendar, PDM diagram, Gantt chart, resource lists and costs, a detailed budget, resource schedule, S-curve, and resource histograms, providing a comprehensive overview of the project's planning and execution phases.
Document Page
Running head: PROJECT MANAGEMENT
Project: Development of a new information technology centre
Name of the Student
Name of the University
Author’s Note
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1
PROJECT MANAGEMENT
Table of Contents
1. Project description..................................................................................................................3
2. List of assumption..................................................................................................................3
3. Planning methodology...........................................................................................................3
4. Manual planning.....................................................................................................................4
4.1 Project calendar................................................................................................................4
4.2 WBS, OBS, and RAM.....................................................................................................4
4.3 Lists of tasks, durations and their logical relationships.................................................10
4.4 Execution programme....................................................................................................13
4.5 Sub-contractors and required labour schedule...............................................................14
4.6 Bill of quantities and cost estimation.............................................................................15
4.7 Risk register...................................................................................................................17
5. Computerized planning........................................................................................................20
5.1 Lists of tasks and WBS..................................................................................................20
5.2 Project calendar..............................................................................................................21
5.3 PDM diagram and Gantt chart.......................................................................................22
5.4 Lists and cost of resources.............................................................................................24
5.5 Cost and detail budget....................................................................................................25
5.6 Resource schedule..........................................................................................................26
5.7 S-curve...........................................................................................................................27
5.8 Histogram for resources.................................................................................................28
5. 9 Relevant report for supporting PEP..............................................................................28
Bibliography.............................................................................................................................29
Document Page
2
PROJECT MANAGEMENT
1. Project description
The project reflects on the development in Australia. It is found that for developing
the centre of information technology, the amount of budget that was approved is $25 million
and additionally $15 million was also provided for utilizing latest IT technology within the
data centre. This is generally done so that the data centre can successfully support the IT
requirements of the clients quite effectively.
2. List of assumption
The list of assumptions that are generally made while developing the IT centre in
Australia are listed below:
The IT centre must be developed in such a way that it will support all the IT needs for
the next coming years
The time that will be needed for finishing the development of the IT centre will be
around 182 days
The amount of budget that is approved will be enough for successful completion of
the entire project.
3. Planning methodology
It is identified that in order to develop the information technology centre, agile
project management methodology is mainly utilized within the project. Agile methodology is
used for developing the information technology centre so that the entire development can get
finished within the time that is expected by utilizing the advantage of Automated tools during
the testing phase of the project. Agile project methodology is very much advantageous in
comparison to other methodologies as with the help of agile methodology, the challenges as
well as issues that are mainly related with the project can successfully get reduced. Moreover,
Document Page
3
PROJECT MANAGEMENT
it is found that the use of agile methodology is quite useful in finishing the entire project
faster as compared to the time that is expected earlier.
4. Manual planning
4.1 Project calendar
Project start date: The initial or starting date of the project will be around 18-06-18
Project end date: The end date of the project will be on 01-03-2019.
Weekends: Saturday as well as Sundays are weekends and considered as holiday for all the
employees.
Public holiday list: The list of public holidays is listed in the table that is provided below:
Monday 11th June Queen’s birthday
Monday 1st October Labour day
Tuesday 25th December Christmas Day
Wednesday 26 December Boxing day
4.2 WBS, OBS, and RAM
Work breakdown Structure (WBS)
Work breakdown structure is one of the deliverable related breakdown of project
activities into key deliverables that generally assists in organizing the entire work or activities
of the team that is required to be performed for successful completion of the project into
number of manageable sections. The WBS for the project is provided in the table below:
WBS Task Name
0
Development of new information technology
centre
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
4
PROJECT MANAGEMENT
1 Initiation phase
1.1 Project needs analysis
1.2 Project plan development
1.3 Feasibility analysis
1.4
Milestone 1: Completion of initiation
phase
2 Planning phase
2.1 Project task scheduling
2.2 Estimation of project resources
2.3 Allocation of resources
2.4 Communication plan development
2.5 Project team allocation
2.6
Milestone 2: Completion of planning
phase
3 Designing phase
3.1 Blueprint creation
3.2 Assigning IT needs
3.3 Necessary equipment purchase
3.4 Recruitment of development team
3.5
Milestone 3: Completion of designing
phase
4 Development phase
4.1 Assigning new hardware
4.2 Assigning software requirements
Document Page
5
PROJECT MANAGEMENT
4.3 Data warehouse development
4.4 Network system development
4.5 Application of security system
4.6 Creating connection between the systems
4.7
Milestone 4: Completion of development
phase
5 Testing phase
5.1 Hardware testing
5.2 Software testing
5.3 Testing of data warehouse
5.4 Milestone 5: Completion of testing phase
6 Closure phase
6.1 Reviewing project
6.2 Sign off
6.3 Data warehouse maintenance
6.4 Milestone 6: Completion of closure phase'
Organizational breakdown structure (OBS)
Organizational breakdown structure is one of the model of hierarchy that assists in
illustrating the entire framework of the organization to plan resources as well as for managing
the time and cost that is associated with the project. The organizational structure for the
project “development of new information technology centre” is provided below:
Document Page
6
PROJECT MANAGEMENT
Figure 1: OBS
(Source: Created by Author)
Responsibility assignment matrix
Responsibility assignment matrix is considered as one of the key component that
assists in finishing the entire project successfully. It assists in identifying the role of each of
the persons who are involved within the project and for what they are accountable within the
project. The RACI stands for responsibility, accountability, consulted and responsible.
Project
manager
Sponsor Contractor Designer Tester Financial
managers
Supervisor
Project needs
analysis
A, R I C
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7
PROJECT MANAGEMENT
Project plan
development
A, R I C
Feasibility
analysis
I C A, R
Project task
scheduling
A, R I C
Estimation of
project resources
I C A, R
Allocation of
resources
I C A, R
Communicati
on plan
development
A, R I C
Project team
allocation
A, R I C
Blueprint
creation
C I R, A
Assigning IT
needs
Necessary
equipment
purchase
C I R, A
Recruitment
of development
team
C I R, A
Document Page
8
PROJECT MANAGEMENT
Assigning
new hardware
C I R, A
Assigning
software
requirements
C I R, A
Data
warehouse
development
C I R, A
Network
system
development
C I R, A
Application
of security
system
C I R, A
Creating
connection
between the
systems
C I R, A
Hardware
testing
I A, R C
Software
testing
I A, R C
Testing of
data warehouse
I A, R C
Reviewing
project
A, R I C
Document Page
9
PROJECT MANAGEMENT
Sign off A, R I C
Data
warehouse
maintenance
A, R I C
4.3 Lists of tasks, durations and their logical relationships
The tasks, durations as well as their logical relationships is reflected in the table that is
provided below:
Task Name Duration Start Finish Predecessors
Development of new information
technology centre
182 days Mon 18-06-18
Fri 01-
03-19
Initiation phase 10 days Mon 18-06-18
Fri 29-
06-18
Project needs analysis 7 days Mon 18-06-18
Tue 26-
06-18
Project plan development 5 days Tue 19-06-18
Wed 27-
06-18
2
Feasibility analysis 4 days Mon 25-06-18
Thu 28-
06-18
3
Milestone 1: Completion of
initiation phase
0 days Fri 29-06-18
Fri 29-06-
18
4
Planning phase 38 days Mon 02-07-18
Wed 22-
08-18
Project task scheduling 3 days Mon 02-07-18
Wed 04-
07-18
4
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
10
PROJECT MANAGEMENT
Estimation of project resources 5 days Fri 06-07-18
Thu 12-
07-18
7
Allocation of resources 8 days Mon 16-07-18
Wed 25-
07-18
8
Communication plan development 9 days Fri 27-07-18
Wed 08-
08-18
9
Project team allocation 10 days Thu 09-08-18
Wed 22-
08-18
10
Milestone 2: Completion of
planning phase
0 days Tue 21-08-18
Tue 21-
08-18
11
Designing phase 40 days Wed 22-08-18
Wed 17-
10-18
Blueprint creation 8 days Wed 22-08-18
Fri 31-08-
18
11
Assigning IT needs 7 days Fri 31-08-18
Mon 10-
09-18
14
Necessary equipment purchase 7 days Mon 10-09-18
Tue 18-
09-18
15
Recruitment of development team 20 days Wed 19-09-18
Wed 17-
10-18
16
Milestone 3: Completion of
designing phase
0 days Wed 17-10-18
Wed 17-
10-18
17
Development phase 62 days Thu 18-10-18
Tue 15-
01-19
Document Page
11
PROJECT MANAGEMENT
Assigning new hardware 7 days Thu 18-10-18
Fri 26-10-
18
17
Assigning software requirements 8 days Mon 29-10-18
Wed 07-
11-18
20
Data warehouse development 22 days Thu 08-11-18
Fri 07-12-
18
21
Network system development 9 days Thu 06-12-18
Tue 18-
12-18
22
Application of security system 9 days Thu 20-12-18
Thu 03-
01-19
23
Creating connection between the
systems
8 days Fri 04-01-19
Tue 15-
01-19
24
Milestone 4: Completion of
development phase
0 days Tue 15-01-19
Tue 15-
01-19
25
Testing phase 23 days Wed 16-01-19
Fri 15-
02-19
Hardware testing 8 days Wed 16-01-19
Fri 25-01-
19
25
Software testing 8 days Mon 28-01-19
Wed 06-
02-19
28
Testing of data warehouse 7 days Thu 07-02-19
Fri 15-02-
19
29
Milestone 5: Completion of
testing phase
0 days Fri 15-02-19
Fri 15-02-
19
30
chevron_up_icon
1 out of 30
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]