Repairing the Tanks of Western Australian Site: Project Management Case Study

Verified

Added on  2023/06/07

|19
|2766
|470
AI Summary
This project management case study focuses on repairing the tanks of Western Australian Site. It covers the development of project budget, schedule, estimation of resources used, and comparison between methodologies. The required resources and their integration with the project schedule are also discussed. The methodology used is Agile project methodology. The project budget is assumed to be $104,360. The project schedule includes milestones and deliverables. The required resources include human, financial, and material resources.

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
Running head: PROJECT MANAGEMENT
Case study- Repairing the tanks of Western Australian Site
Name of the Student
Name of the University
Author’s Note

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
1PROJECT MANAGEMENT
Table of Contents
1. Development of project budget and assumptions that are made.................................................2
1.1 Project budget........................................................................................................................2
1.2 Assumptions for developing budget......................................................................................4
2. Schedule for the project...............................................................................................................4
2.1 Preparation of schedule with milestones and project deliverables........................................4
2.2 Discussion about the relative merits of the methods, tools and techniques...........................8
2.3 Comparison between tools, techniques and methodologies..................................................9
3. Estimation of resources used.....................................................................................................10
3.1 Resources that are required for the project..........................................................................10
3.2 Integration of resources with schedule................................................................................11
3.3 Critical path.........................................................................................................................15
3.4 Tools and techniques...........................................................................................................16
Bibliography..................................................................................................................................17
Document Page
2PROJECT MANAGEMENT
1. Development of project budget and assumptions that are made
1.1 Project budget
The amount of money which is generally needed for repairing the Western Australia site
tank is assumed to be around $104,360. The detailed budget of the project which is required for
executing each of the phase of the project is provided in the table below:
WBS Task Name Cost
0 Repairing the tanks of Western Australian Site $104,360.00
1 Project initiation phase $7,200.00
1.1 Analyzing the issues $1,120.00
1.2 Conducting feasibility analysis $2,400.00
1.3 Developing charter $1,440.00
1.4 Recruitment team members $1,280.00
1.5 Reviewing project initiation $960.00
1.6 Milestone 1:Completion of initiation phase review $0.00
2 Project planning phase $19,560.00
2.1 Development of project plan $2,400.00
2.2 Resource plan development $1,680.00
2.3 Financial plan development $2,240.00
2.4 Checking quality $6,400.00
2.5 Acceptance plan development $6,840.00
2.6 Milestone 2: Completion of project planning phase $0.00
Document Page
3PROJECT MANAGEMENT
3 Project execution phase $74,080.00
3.1 Development of agreement between stakeholders $5,600.00
3.2 Settling external issues $5,200.00
3.3 Developing agreement $6,000.00
3.4 Preparatory work completion $4,160.00
3.5 Creating strategies that for stopping leakage $4,800.00
3.6 Developing strategies for resolving challenges $4,160.00
3.7 Undertaking project work $4,400.00
3.8 Completion of project repairing $4,160.00
3.9 Different project activities adjustment $3,360.00
3.10 Tank repairing $10,400.00
3.11 Analyzing work which is completed $9,600.00
3.12 Closing different project issues $12,240.00
3.13 Milestone 3:Project repair completion $0.00
4 Project closure $3,520.00
4.1 Project review $1,120.00
4.2 Final reporting completion $1,440.00
4.3 Project documentation $960.00
4.4 Milestone 4: Completion of project documentation $0.00

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4PROJECT MANAGEMENT
1.2 Assumptions for developing budget
The assumptions that are generally made by the project manager before developing the
project budget are mainly elaborated below:
Time of the project will not exceed: An assumption about project time is made and
according to which the project will be completed within the time that is expected and as a result
the budget of the project will not increase.
Absence of scope creep: The project manager assumes that the project will be completed
as per the project scope and there will be no changes within the scope and therefore the assumed
budget will be enough for repairing the tanks of WA site.
No extra resources needed: The project manager make an assumption before
developing the budget for the project that all the activities of the project will be completed by
utilizing the provided resources and thus there will be no need of extra resources within the
project.
2. Schedule for the project
2.1 Preparation of schedule with milestones and project deliverables
The project schedule that is mainly developed for repairing the tanks are mainly
provided below: It is identified that the schedule of the project mainly includes the deliverables
as well as milestones of the project. The project schedule is given below:
WBS Task Name Duration Start Finish
0
Repairing the tanks of Western Australian
Site
86 days Mon 9/3/18
Mon
12/31/18
Document Page
5PROJECT MANAGEMENT
1 Project initiation phase 15 days Mon 9/3/18 Fri 9/21/18
1.1 Analyzing the issues 4 days Mon 9/3/18 Thu 9/6/18
1.2 Conducting feasibility analysis 5 days Fri 9/7/18 Thu 9/13/18
1.3 Developing charter 3 days Fri 9/14/18 Tue 9/18/18
1.4 Recruitment team members 4 days Fri 9/14/18
Wed
9/19/18
1.5 Reviewing project initiation 3 days
Wed
9/19/18
Fri 9/21/18
1.6
Milestone 1:Completion of initiation
phase review
0 days
Wed
9/19/18
Wed
9/19/18
2 Project planning phase 21 days
Mon
9/24/18
Mon
10/22/18
2.1 Development of project plan 5 days
Mon
9/24/18
Fri 9/28/18
2.2 Resource plan development 6 days
Mon
10/1/18
Mon
10/8/18
2.3 Financial plan development 7 days
Mon
10/1/18
Tue 10/9/18
2.4 Checking quality 8 days Tue 10/9/18
Thu
10/18/18
2.5 Acceptance plan development 9 days
Wed
10/10/18
Mon
10/22/18
Document Page
6PROJECT MANAGEMENT
2.6
Milestone 2: Completion of project
planning phase
0 days Tue 10/9/18 Tue 10/9/18
3 Project execution phase 43 days
Tue
10/23/18
Thu
12/20/18
3.1
Development of agreement between
stakeholders
14 days
Tue
10/23/18
Fri 11/9/18
3.2 Settling external issues 13 days
Tue
10/23/18
Thu 11/8/18
3.3 Developing agreement 15 days
Mon
11/12/18
Fri 11/30/18
3.4 Preparatory work completion 13 days
Mon
11/12/18
Wed
11/28/18
3.5
Creating strategies that for stopping
leakage
12 days Fri 11/9/18
Mon
11/26/18
3.6
Developing strategies for resolving
challenges
13 days Fri 11/9/18
Tue
11/27/18
3.7 Undertaking project work 11 days
Mon
12/3/18
Mon
12/17/18
3.8 Completion of project repairing 13 days
Mon
12/3/18
Wed
12/19/18
3.9 Different project activities adjustment 12 days
Thu
11/29/18
Fri 12/14/18
3.10 Tank repairing 13 days Tue Thu

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7PROJECT MANAGEMENT
11/27/18 12/13/18
3.11 Analyzing work which is completed 12 days
Wed
11/28/18
Thu
12/13/18
3.12 Closing different project issues 17 days
Wed
11/28/18
Thu
12/20/18
3.13 Milestone 3:Project repair completion 0 days
Mon
12/17/18
Mon
12/17/18
4 Project closure 7 days
Fri
12/21/18
Mon
12/31/18
4.1 Project review 4 days Fri 12/21/18
Wed
12/26/18
4.2 Final reporting completion 3 days
Thu
12/27/18
Mon
12/31/18
4.3 Project documentation 2 days
Thu
12/27/18
Fri 12/28/18
4.4
Milestone 4: Completion of project
documentation
0 days
Wed
12/26/18
Wed
12/26/18
Document Page
8PROJECT MANAGEMENT
2.2 Discussion about the relative merits of the methods, tools and techniques
Methodology that is used
Agile project methodology is mainly used in this project for repairing the tank of Western
Australian Site. Agile methodology is used in this project as with the help of this methodology,
the entire project is broken into smaller tasks so that the tasks or activities of the project can be
managed effectively. Additionally, it is analyzed that this methodology is helpful in reducing the
time as well as assists in managing the project quite effectively.
Merits of tools and techniques
It is found that project schedule is mainly used for the project and the advantages of
utilizing this tool within this project is reflected below:
Cost: The cost that is associated with the project will generally be reflected with the help
of the schedule. In addition to this, it is found that the project schedule assists in giving idea
about the budget for completing each project step.
Tracking: The project schedule assists in giving chance of tracking the project related
activities for ensuring whether the project gets completed or not.
Assists in giving idea: It is found that the project schedule provides proper overview
about the project related activities so that the entire project of repairing the can be completed
effectively.
Document Page
9PROJECT MANAGEMENT
2.3 Comparison between tools, techniques and methodologies
Proper comparison between project methodologies is provided in the below table:
Agile methodology Waterfall methodology
Agile project methodology helps in
managing the project time for ensuring that
the entire project will get finished within the
provided time.
Waterfall methodology does not assists in
managing time but they manages and
resolve project risks.
With the help of agile project methodology
the project stakeholders can be able to make
the required changes continuously.
This methodology helps in proper task
distribution so that proper quality of project
tasks can be maintained.
The comparison between project schedule and WBS is given below:
Schedule Work breakdown structure
With the help of project schedule, the tasks
and activities of the project can be
successfully tracked.
WBS assists in breaking the tasks into
number of activities that can be effectively
managed.
The schedule of the project helps in
reflecting the needed budget for the project.
It is considered to be one of the groundwork
for the development of project budget.

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10PROJECT MANAGEMENT
3. Estimation of resources used
3.1 Resources that are required for the project
The resources which are required for the tank repairing are illustrated below:
Human resources: The required human resources for tank repairing are:
Project manager
Contractor
Site planner
Project planner
Supervisor
Financial resources: The required amount of money for the project of Western Australian
Site will be around $04,360.
Material resources: The requires material for the project are as follows:
Mobile resources scaffolding
Steel anchors
Cranes
Stainless steel flow valve
Steel coatings
Document Page
11PROJECT MANAGEMENT
3.2 Integration of resources with schedule
The table that is provided below reflects the integration of resources with the project
schedule.
WBS Task Name Duration Start Finish Resource Names
0
Repairing the tanks
of Western
Australian Site
86 days Mon 9/3/18 Mon 12/31/18
1
Project initiation
phase
15 days Mon 9/3/18 Fri 9/21/18
1.1
Analyzing the
issues
4 days Mon 9/3/18 Thu 9/6/18 Project planner
1.2
Conducting
feasibility analysis
5 days Fri 9/7/18 Thu 9/13/18 Project manager
1.3
Developing
charter
3 days Fri 9/14/18 Tue 9/18/18 Project manager
1.4
Recruitment team
members
4 days Fri 9/14/18 Wed 9/19/18 Site planner
1.5
Reviewing
project initiation
3 days Wed 9/19/18 Fri 9/21/18 Site planner
1.6 Milestone
1:Completion of
initiation phase
0 days Wed 9/19/18 Wed 9/19/18
Document Page
12PROJECT MANAGEMENT
review
2
Project planning
phase
21 days Mon 9/24/18 Mon 10/22/18
2.1
Development of
project plan
5 days Mon 9/24/18 Fri 9/28/18 Project manager
2.2
Resource plan
development
6 days Mon 10/1/18 Mon 10/8/18 Project planner
2.3
Financial plan
development
7 days Mon 10/1/18 Tue 10/9/18 Business analyst
2.4 Checking quality 8 days Tue 10/9/18 Thu 10/18/18
Project manager,
Business analyst
2.5
Acceptance plan
development
9 days Wed 10/10/18 Mon 10/22/18
Project manager, Project
planner
2.6
Milestone 2:
Completion of
project planning
phase
0 days Tue 10/9/18 Tue 10/9/18
Project manager, Project
planner
3
Project execution
phase
43 days Tue 10/23/18 Thu 12/20/18
3.1
Development of
agreement between
stakeholders
14 days Tue 10/23/18 Fri 11/9/18 Contractor
3.2 Settling external 13 days Tue 10/23/18 Thu 11/8/18 Supervisor

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
13PROJECT MANAGEMENT
issues
3.3
Developing
agreement
15 days Mon 11/12/18 Fri 11/30/18 Contractor
3.4
Preparatory work
completion
13 days Mon 11/12/18 Wed 11/28/18 Site planner
3.5
Creating
strategies that for
stopping leakage
12 days Fri 11/9/18 Mon 11/26/18 Supervisor
3.6
Developing
strategies for
resolving challenges
13 days Fri 11/9/18 Tue 11/27/18 Site planner
3.7
Undertaking
project work
11 days Mon 12/3/18 Mon 12/17/18 Contractor
3.8
Completion of
project repairing
13 days Mon 12/3/18 Wed 12/19/18 Site planner
3.9
Different project
activities adjustment
12 days Thu 11/29/18 Fri 12/14/18 Project planner
3.10 Tank repairing 13 days Tue 11/27/18 Thu 12/13/18 Contractor, Supervisor
3.11
Analyzing work
which is completed
12 days Wed 11/28/18 Thu 12/13/18 Contractor, Supervisor
3.12
Closing different
project issues
17 days Wed 11/28/18 Thu 12/20/18 Contractor, Site planner
Document Page
14PROJECT MANAGEMENT
3.13
Milestone
3:Project repair
completion
0 days Mon 12/17/18 Mon 12/17/18
4 Project closure 7 days Fri 12/21/18 Mon 12/31/18
4.1 Project review 4 days Fri 12/21/18 Wed 12/26/18 Project planner
4.2
Final reporting
completion
3 days Thu 12/27/18 Mon 12/31/18 Project manager
4.3
Project
documentation
2 days Thu 12/27/18 Fri 12/28/18 Project manager
4.4
Milestone 4:
Completion of
project
documentation
0 days Wed 12/26/18 Wed 12/26/18 Project planner
Document Page
15PROJECT MANAGEMENT
3.3 Critical path
The critical path of the project is provided below:
Figure 1: Critical Path
(Source: Created by Author)

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
16PROJECT MANAGEMENT
3.4 Tools and techniques
It is found that that in this project, analogous estimation tool is used for the purpose of
resource estimation. This method or technique of resource estimation is used for estimating the
needed resources for the project as it is identified that this technique of resource estimation is
quite beneficial for lowering the project cost by making proper reflection on the schedule of the
project. In spite of the advantages and benefits that is provided by this technique it is analyzed
that this technique is not always useful for estimating the resources as it does not always assist in
providing proper as well as accurate results.
Document Page
17PROJECT MANAGEMENT
Bibliography
Braglia, M., & Frosolini, M. (2014). An integrated approach to implement project management
information systems within the extended enterprise. International Journal of Project
Management, 32(1), 18-29.
Cagliano, A. C., Grimaldi, S., & Rafele, C. (2015). Choosing project risk management
techniques. A theoretical framework. Journal of Risk Research, 18(2), 232-248.
Conforto, E. C., Amaral, D. C., da Silva, S. L., Di Felippo, A., & Kamikawachi, D. S. L. (2016).
The agility construct on project management theory. International Journal of Project
Management, 34(4), 660-674.
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.
Costantino, F., Di Gravio, G., & Nonino, F. (2015). Project selection in project portfolio
management: An artificial neural network model based on critical success
factors. International Journal of Project Management, 33(8), 1744-1754.
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.
Joslin, R., & 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), 1377-1392.
Document Page
18PROJECT MANAGEMENT
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.
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking
project management performance and project success. International journal of project
management, 32(2), 202-217.
Riol, H., & Thuillier, D. (2015). Project management for academic research projects: balancing
structure and flexibility. International Journal of Project Organisation and
Management, 7(3), 251-269.
Takey, S. M., & de Carvalho, M. M. (2015). Competency mapping in project management: An
action research study in an engineering company. International Journal of Project
Management, 33(4), 784-796.
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.
1 out of 19
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]