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.
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.
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.
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 |
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.4 |
Milestone 6: Completion of closure phase’ |
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 |
||||
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 |
||||
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 |
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-18 |
Thu 05-07-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-18 |
Fri 26-10-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-19 |
Wed 27-02-19 |
6.1 |
Post project review |
2 days |
Wed 13-02-19 |
Thu 14-02-19 |
6.2 |
Stakeholder sign off |
4 days |
Fri 15-02-19 |
Wed 20-02-19 |
6.3 |
Maintenance of the Data Warehouse |
5 days |
Thu 21-02-19 |
Wed 27-02-19 |
6.4 |
Milestone 6: Completion of closure phase’ |
0 days |
Wed 27-02-19 |
Wed 27-02-19 |
The execution programme of the project mainly includes activities that are provided in the table below:
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 |
Testing Phase |
19 days |
Fri 11-01-19 |
Wed 06-02-19 |
Testing of the Hardware |
7 days |
Fri 11-01-19 |
Mon 21-01-19 |
Testing of the software |
7 days |
Tue 22-01-19 |
Wed 30-01-19 |
Data Warehouse Testing |
5 days |
Thu 31-01-19 |
Wed 06-02-19 |
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 |
Supervisor |
Work |
100% |
$140.00/hr |
$0.00/hr |
WBS |
Task Name |
Duration |
Cost |
0 |
Development of new information technology centre |
187 days |
$39,360,880.00 |
1 |
Project initiation phase |
17 days |
$40,000.00 |
1.1 |
Analyzing various project requirements |
8 days |
$16,000.00 |
1.2 |
Development of project plan |
4 days |
$8,000.00 |
1.3 |
Project feasibility testing |
5 days |
$16,000.00 |
1.4 |
Milestone 1: Completion of initiation phase |
0 days |
$0.00 |
2 |
Project planning phase |
37 days |
$77,520.00 |
2.1 |
Scheduling of project task |
4 days |
$6,720.00 |
2.2 |
Resource estimation |
6 days |
$8,160.00 |
2.3 |
Resource allocation |
9 days |
$21,600.00 |
2.4 |
Development of communication plan |
9 days |
$29,520.00 |
2.5 |
Allocating project team |
9 days |
$11,520.00 |
2.6 |
Milestone 2: Completion of planning phase |
0 days |
$0.00 |
3 |
Project designing phase |
40 days |
$55,600.00 |
3.1 |
Creating blueprint |
7 days |
$11,200.00 |
3.2 |
Assigning IT needs |
6 days |
$7,680.00 |
3.3 |
Purchase of necessary equipment’s |
7 days |
$9,520.00 |
3.4 |
Recruitment of software development team |
20 days |
$27,200.00 |
3.5 |
Milestone 3: Completion of designing phase |
0 days |
$0.00 |
4 |
Development phase |
63 days |
$27,107,200.00 |
4.1 |
Assigning new hardware requirements |
7 days |
$8,000,000.00 |
4.2 |
Assigning software requirements |
8 days |
$7,000,000.00 |
4.3 |
Development of data warehouse |
20 days |
$60,800.00 |
4.4 |
Development of network system |
10 days |
$12,000,000.00 |
4.5 |
Security System application |
10 days |
$30,400.00 |
4.6 |
Interconnection between developed overall information system |
8 days |
$16,000.00 |
4.7 |
Milestone 4: Completion of execution phase |
0 days |
$0.00 |
5 |
Testing Phase |
19 days |
$12,049,600.00 |
5.1 |
Testing of the Hardware |
7 days |
$12,011,200.00 |
5.2 |
Testing of the software |
7 days |
$22,400.00 |
5.3 |
Data Warehouse Testing |
5 days |
$16,000.00 |
5.4 |
Milestone 5: Completion of testing phase |
0 days |
$0.00 |
6 |
Closing Phase |
11 days |
$30,960.00 |
6.1 |
Post project review |
2 days |
$7,200.00 |
6.2 |
Stakeholder sign off |
4 days |
$13,760.00 |
6.3 |
Maintenance of the Data Warehouse |
5 days |
$10,000.00 |
6.4 |
Milestone 6: Completion of closure phase’ |
0 days |
$0.00 |
Risk |
Description |
Impact |
Probability |
Mitigation measures |
Improper budget estimation |
Due to improper budget estimation, financial issues occur within the project |
High |
High |
It is necessary to estimate the budget of the project effectively |
Lack of resources |
Due to lack resources, it became quite difficult to finish the project on time |
Medium |
Medium |
It is quite necessary to estimate the project resources effectively. |
Improper management |
Due to improper management, the project does not get finish on time. |
Medium |
Medium |
It is quite important to manage the project effectively as per the initial plan |
Improper scheduling |
Due to improper scheduling, the project can delay |
High |
High |
It is quite necessary to schedule the project effectively |
Lack of experienced workers |
Due to lack of experienced workers, it is quite difficult to finish the project on time. |
Medium |
Medium |
It is necessary to hire experienced project workers. |
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.
Srivannaboon, S., & Munkongsujarit, S. (2016, September). Project management and project portfolio management in open innovation: Literature review. In Management of Engineering and Technology (PICMET), 2016 Portland International Conference on (pp. 2002-2007). IEEE.
Svejvig, P., & Andersen, P. (2015). Rethinking project management: A structured literature review with a critical look at the brave new world. International Journal of Project Management, 33(2), 278-290.
Todorovi?, M. L., Petrovi?, D. ?., Mihi?, M. M., Obradovi?, V. L., & Bushuyev, S. D. (2015). Project success analysis framework: A knowledge-based approach in project management. International Journal of Project Management, 33(4), 772-783.
Too, E. G., & Weaver, P. (2014). The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), 1382-1394.