Pmo201 Project Management: Development Of Assessment Answers
Project: Development of a new information technology centre
As the IT Project Manager of the project you are requested to submit a Project Execution Plan (PEP) for this development.
The group has to develop a project execution plan to manage the activities required to construct the IT Centre.
The tasks required include:
Answer:
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.
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.
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, 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.
Manual planning
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 |
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 |
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 |
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:
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 |
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 |
|
Communication 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 |
|
|
|
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 |
Sign off |
A, R |
I |
|
|
|
|
C |
Data warehouse maintenance |
A, R |
I |
|
|
|
|
C |
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 |
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 |
|
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 |
Closure phase |
10 days |
Mon 18-02-19 |
Fri 01-03-19 |
|
Reviewing project |
3 days |
Mon 18-02-19 |
Wed 20-02-19 |
30 |
Sign off |
3 days |
Thu 21-02-19 |
Mon 25-02-19 |
33 |
Data warehouse maintenance |
4 days |
Tue 26-02-19 |
Fri 01-03-19 |
34 |
Milestone 6: Completion of closure phase' |
0 days |
Fri 01-03-19 |
Fri 01-03-19 |
35 |
Execution programme
The entire execution programme for the development of the IT centre is provided in the table that is provided below:
WBS |
Task Name |
Duration |
3 |
Designing phase |
40 days |
3.1 |
Blueprint creation |
8 days |
3.2 |
Assigning IT needs |
7 days |
3.3 |
Necessary equipment’s purchase |
7 days |
3.4 |
Recruitment of development team |
20 days |
3.5 |
Milestone 3: Completion of designing phase |
0 days |
4 |
Development phase |
62 days |
4.1 |
Assigning new hardware |
7 days |
4.2 |
Assigning software requirements |
8 days |
4.3 |
Data warehouse development |
22 days |
4.4 |
Network system development |
9 days |
4.5 |
Application of security system |
9 days |
4.6 |
Creating connection between the systems |
8 days |
4.7 |
Milestone 4: Completion of development phase |
0 days |
5 |
Testing phase |
23 days |
5.1 |
Hardware testing |
8 days |
5.2 |
Software testing |
8 days |
5.3 |
Testing of data warehouse |
7 days |
5.4 |
Milestone 5: Completion of testing phase |
0 days |
Sub-contractors and required labour schedule
The sub-contractors as well as needed schedule of the labours are provided in the table below:
Name |
Start |
Finish |
Remaining Work |
Project Manager |
Mon 18-06-18 |
Fri 01-03-19 |
152 hrs. |
Project Sponsor |
Mon 18-02-19 |
Wed 20-02-19 |
24 hrs. |
Contractor |
Mon 02-07-18 |
Fri 07-12-18 |
16 hrs. |
Risk Manager |
Mon 28-01-19 |
Fri 15-02-19 |
120 hrs. |
Designer |
Mon 25-06-18 |
Fri 15-02-19 |
192 hrs. |
Tester |
Mon 25-06-18 |
Fri 15-02-19 |
176 hrs. |
Business Consultant |
Thu 20-12-18 |
Mon 25-02-19 |
80 hrs. |
Financial Manager |
Fri 06-07-18 |
Fri 07-12-18 |
16 hrs. |
Team Leaders |
Mon 16-07-18 |
Mon 10-09-18 |
16 hrs. |
Supervisor |
Mon 16-07-18 |
Wed 25-07-18 |
0 hrs. |
Bill of quantities and cost estimation
The bill of quantities and cost estimation as per the WBS is provided in the table below:
WBS |
Task Name |
Duration |
Cost |
0 |
Development of new information technology centre |
182 days |
$39,395,200.00 |
1 |
Initiation phase |
10 days |
$36,800.00 |
1.1 |
Project needs analysis |
7 days |
$14,000.00 |
1.2 |
Project plan development |
5 days |
$10,000.00 |
1.3 |
Feasibility analysis |
4 days |
$12,800.00 |
1.4 |
Milestone 1: Completion of initiation phase |
0 days |
$0.00 |
2 |
Planning phase |
38 days |
$73,360.00 |
2.1 |
Project task scheduling |
3 days |
$5,040.00 |
2.2 |
Estimation of project resources |
5 days |
$6,800.00 |
2.3 |
Allocation of resources |
8 days |
$19,200.00 |
2.4 |
Communication plan development |
9 days |
$29,520.00 |
2.5 |
Project team allocation |
10 days |
$12,800.00 |
2.6 |
Milestone 2: Completion of planning phase |
0 days |
$0.00 |
3 |
Designing phase |
40 days |
$58,480.00 |
3.1 |
Blueprint creation |
8 days |
$12,800.00 |
3.2 |
Assigning IT needs |
7 days |
$8,960.00 |
3.3 |
Necessary equipment’s purchase |
7 days |
$9,520.00 |
3.4 |
Recruitment of development team |
20 days |
$27,200.00 |
3.5 |
Milestone 3: Completion of designing phase |
0 days |
$0.00 |
4 |
Development phase |
62 days |
$27,110,240.00 |
4.1 |
Assigning new hardware |
7 days |
$8,000,000.00 |
4.2 |
Assigning software requirements |
8 days |
$7,000,000.00 |
4.3 |
Data warehouse development |
22 days |
$66,880.00 |
4.4 |
Network system development |
9 days |
$12,000,000.00 |
4.5 |
Application of security system |
9 days |
$27,360.00 |
4.6 |
Creating connection between the systems |
8 days |
$16,000.00 |
4.7 |
Milestone 4: Completion of development phase |
0 days |
$0.00 |
5 |
Testing phase |
23 days |
$12,087,200.00 |
5.1 |
Hardware testing |
8 days |
$12,012,800.00 |
5.2 |
Software testing |
8 days |
$39,680.00 |
5.3 |
Testing of data warehouse |
7 days |
$34,720.00 |
5.4 |
Milestone 5: Completion of testing phase |
0 days |
$0.00 |
6 |
Closure phase |
10 days |
$29,120.00 |
6.1 |
Reviewing project |
3 days |
$10,800.00 |
6.2 |
Sign off |
3 days |
$10,320.00 |
6.3 |
Data warehouse maintenance |
4 days |
$8,000.00 |
6.4 |
Milestone 6: Completion of closure phase' |
0 days |
$0.00 |
Risk register
Risk |
Description |
Impact |
Probability |
Mitigation measures |
Inappropriate estimation of budget |
It is identified that due to inappropriate budget estimate it is very much difficult to finish the entire project successfully. |
High |
High |
It is very much necessary to utilized earned value analysis in order to track the budget successfully. |
Lack of proper resources |
Due to inappropriate resources within the project, it is very much difficult to complete the development of the IT centre within the expected time and budget. |
High |
Medium |
It is very much necessary to analyze the resources properly for the project. |
Inappropriate management |
Due to inappropriate management of project it is quite tough to finish the entire project within the expected budget and time |
Medium |
Medium |
It is very much necessary to utilize proper management strategies for managing the project effectively. |
Technical issues |
The technical problem that occurs due to inappropriate connection as well as problems in data warehouse causes lot of challenges for the project manager. |
High |
High |
It is necessary to undertake testing after the development phase of the project. |
Lack of experience |
Due to lack of proper experience, it is very much difficult for the project manager to properly finish the project |
Medium |
Medium |
It is quite necessary to hire workers for the project who are very much experienced for avoiding such issues. |
Computerized planning
Lists of tasks and WBS
Figure 2: Lists of tasks and schedule
(Source: Created by Author)
Project calendar
Figure 3: Project calendar
(Source: Created by Author)
PDM diagram and Gantt chart
PDM diagram
Gantt chart
Figure 5: Gantt chart
(Source: Created by Author)
Lists and cost of resources
Figure 6: Resource cost
(Source: Created by Author)
Cost and detail budget
Figure 6: Detailed budget
(Source: Created by Author)
Resource schedule
Figure 6: Resource schedule
(Source: Created by Author)
S-curve
Figure 7: S curve
(Source: Created by Author)
Histogram for resources
Figure 8: Resource Histogram
(Source: Created by Author)
Relevant report for supporting PEP
Figure 8: Resource cost overview
(Source: Created by Author)
Bibliography
Badewi, A., 2016. The impact of project management (PM) and benefits management (BM) practices on project success: Towards developing a project benefits governance framework. International Journal of Project Management, 34(4), pp.761-778.
Conforto, E.C., Salum, F., Amaral, D.C., da Silva, S.L. and de Almeida, L.F.M., 2014. Can agile project management be adopted by industries other than software development?. Project Management Journal, 45(3), pp.21-34.
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology and project success in different project governance contexts. International Journal of Project Management, 33(6), pp.1377-1392.
Kerzner, H., 2017. Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.
Svejvig, P. and 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), pp.278-290.
Kucharska, W. and Kowalczyk, R., 2016. Trust, Collaborative Culture and Tacit Knowledge Sharing in Project Management–a Relationship Model.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A.M.E. and Villanueva, P., 2014. Project risk management methodology for small firms. International journal of project management, 32(2), pp.327-340.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), pp.202-217.
Sánchez, M.A., 2015. Integrating sustainability issues into project management. Journal of Cleaner Production, 96, pp.319-330.roject Management, 33(4), pp.772-783.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Todorovi?, M.L., Petrovi?, D.?., Mihi?, M.M., Obradovi?, V.L. and Bushuyev, S.D., 2015. Project success analysis framework: A knowledge-based approach in project management. International Journal of P
Too, E.G. and Weaver, P., 2014. The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), pp.1382-1394.
Buy Pmo201 Project Management: Development Of Assessment Answers Online
Talk to our expert to get the help with Pmo201 Project Management: Development Of Assessment Answers to complete your assessment on time and boost your grades now
The main aim/motive of the management assignment help services is to get connect with a greater number of students, and effectively help, and support them in getting completing their assignments the students also get find this a wonderful opportunity where they could effectively learn more about their topics, as the experts also have the best team members with them in which all the members effectively support each other to get complete their diploma assignments. They complete the assessments of the students in an appropriate manner and deliver them back to the students before the due date of the assignment so that the students could timely submit this, and can score higher marks. The experts of the assignment help services at urgenthomework.com are so much skilled, capable, talented, and experienced in their field of programming homework help writing assignments, so, for this, they can effectively write the best economics assignment help services.