Development of a New Information Technology Centre: Project Plan

This project execution plan details the development of a new Information Technology Centre in Australia, with an approved budget of $25 million and an additional $15 million for IT technology. The project, spanning 187 days, utilizes the Agile project methodology to manage risks and challenges effectively. The plan encompasses a detailed project calendar, organizational breakdown structure, responsibility matrix, and a comprehensive execution program including a Gantt chart, WBS, resource schedule, cost estimates, and risk management strategies. The project's scope includes the development of both the IT centre facilities and IT support, with key assumptions around project duration, budget adherence, and IT support for five years. The project team's responsibilities are clearly defined across various phases, from project design to post-project review, with a focus on delivering the IT centre within the allocated resources and timeframe. The plan includes a detailed breakdown of tasks, durations, and resource allocation, supported by visual aids such as a network diagram and S-curve, to ensure efficient project execution and successful completion.

Development of a new information
technology centre

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.

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.

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

Project calendar
• Start date: Wed 06-06-18
• 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

Organizational breakdown structure

Responsibility Matrix
Analyzing various project
requirements
Project manager Sponsor Contractor Designer Tester Financial managers Supervisor
Development of project plan A, R I C
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

Responsibility Matrix Contd.
Recruitment of software
development team
C I R, A
Assigning new hardware
requirements
C I R, A
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

Responsibility Matrix Contd.
Testing of the Hardware I A, R C
Testing of the software I A, R C
Data Warehouse Testing
I A, R C
Post project review A, R I C
Stakeholder sign off A, R I C
Maintenance of the Data
Warehouse
A, R I C

Execution programme
Task Name Duration Start Finish
Project designing phase 40 days Tue 21-08-18 Mon 15-10-18
Creating blueprint 7 days Tue 21-08-18 Wed 29-08-18
Assigning IT needs 6 days Thu 30-08-18 Thu 06-09-18
Purchase of necessary equipment’s 7 days Fri 07-09-18 Mon 17-09-18
Recruitment of software development team 20 days Tue 18-09-18 Mon 15-10-18
Development phase 63 days Tue 16-10-18 Thu 10-01-19
Assigning new hardware requirements 7 days Tue 16-10-18 Wed 24-10-18
Assigning software requirements 8 days Thu 25-10-18 Mon 05-11-18
Development of data warehouse 20 days Tue 06-11-18 Mon 03-12-18
Development of network system 10 days Tue 04-12-18 Mon 17-12-18
Security System application 10 days Tue 18-12-18 Mon 31-12-18
Interconnection between developed overall
information system
8 days Tue 01-01-19 Thu 10-01-19

Sub-contractors and required labour
schedule
Resource Name Type Max. Units Std. Rate Ovt. Rate
Project Sponsor Work 100% $200.00/hr $0.00/hr
Contractor Work 100% $210.00/hr $0.00/hr
Risk Manager Work 100% $220.00/hr $0.00/hr
Designer Work 100% $200.00/hr $0.00/hr
Analyst Work 100% $200.00/hr $0.00/hr
Business Consultant Work 100% $180.00/hr $0.00/hr
Financial Manager Work 100% $170.00/hr $0.00/hr
Team Leaders Work 100% $160.00/hr $0.00/hr

List of tasks and WBS

Network diagram

Gantt chart

Cost and detail budget

Resource Schedule

S-curve

Histogram for resources
Project
Manager
Project
Sponsor
Contractor Risk
Manager
Designer Tester Business
Consultant
Finacial
Manager
Team
Leaders Supervisor
0 hrs
50 hrs
100 hrs
150 hrs
200 hrs
250 hrs
300 hrs
350 hrs
400 hrs
450 hrs
Actual Work Remaining Work Baseline Work

Resource cost overview
Project
Manager
Project
Sponsor
Contractor Risk
Manager
Designer Tester Business
Consultant
Finacial
Manager
Team
Leaders
Supervisor
$0.00
$10,000.00
$20,000.00
$30,000.00
$40,000.00
$50,000.00
$60,000.00
$70,000.00
$80,000.00
$90,000.00

References
 Chih, Y. Y., & Zwikael, O. (2015). Project benefit management: A conceptual framework of
target benefit formulation. International Journal of Project Management, 33(2), 352-362.
Conforto, E. C., Salum, F., Amaral, D. C., da Silva, S. L., & de Almeida, L. F. M. (2014). Can
agile project management be adopted by industries other than software development?. Project
Management Journal, 45(3), 21-34.
Hornstein, H. A. (2015). The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2), 291-298.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project
risk management methodology for small firms. International journal of project
management, 32(2), 327-340.