Project Management Individual Assessment: DAM798, Level 7, Semester 1

Verified

Added on  2022/09/26

|18
|3026
|16
Project
AI Summary
Read More
tabler-icon-diamond-filled.svg

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
Running head: PROJECT MANAGEMENT
Project Management
Name of the Student:
Name of the University:
tabler-icon-diamond-filled.svg

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
Question 1..................................................................................................................................3
a) Network Diagram............................................................................................................3
b) Earliest start time (EST)..............................................................................................3
c) Latest start time (LST)....................................................................................................3
d) Earliest finish time (EFT)............................................................................................4
e) Latest finish time (LFT)..................................................................................................4
f) Slack time........................................................................................................................4
g) Critical path.................................................................................................................5
h) Critical path duration...................................................................................................5
Question 2..................................................................................................................................5
a) Bottom-up and top-down estimation...............................................................................5
b) Project budgeting process............................................................................................6
c) Earned Value Management.............................................................................................7
i) Planned value (PV) = Planned % complete * Project budget.....................................7
ii) Earned value (EV) = Actual % complete * project budget...........................................7
iii) Percentage spent in terms of total budget.....................................................................8
iv) Cost variance (CV).......................................................................................................8
v) Scheduled variance (SV)...............................................................................................8
vi) Cost performance index (CPI)......................................................................................8
vii) Schedule performance index (SPI)..............................................................................8
Document Page
2PROJECT MANAGEMENT
viii) Estimate at completion...............................................................................................8
ix) Variance at completion.................................................................................................8
x) Estimate to complete......................................................................................................9
d) Vendor selection..........................................................................................................9
Question 3................................................................................................................................10
i. Calculation of risk total.............................................................................................10
ii. Risk management impact versus probability chart................................................10
iii. Risk management...................................................................................................11
Question 4................................................................................................................................13
a) Evaluation of software tools used for planning and managing projects.......................13
b) Limitations of software tools for planning and managing projects...........................14
References................................................................................................................................15
Document Page
3PROJECT MANAGEMENT
Question 1
a) Network Diagram
Figure 1: Task Network Diagram
(Source: Created by author)
b) Earliest start time (EST)
Activit
y Time EST
(weeks)
A 4 0
B 8 0
C 6 8
D 10 14
E 8 14
F 6 24
G 7 24
H 5 31
c) Latest start time (LST)
Activit
y Time LST
(weeks)
A 4 4
B 8 0
C 6 8
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4PROJECT MANAGEMENT
D 10 14
E 8 16
F 6 25
G 7 24
H 5 31
d) Earliest finish time (EFT)
Activity Time EFT
(weeks)
A 4 4
B 8 8
C 6 14
D 10 24
E 8 22
F 6 30
G 7 31
H 5 36
e) Latest finish time (LFT)
Activity Time LFT
(weeks
)
A 4 8
B 8 8
C 6 14
D 10 24
E 8 24
F 6 31
G 7 31
H 5 36
f) Slack time
Activit
y
Time ES
T
EF
T
LS
T
LF
T
Slac
k
(week
s)
A 4 0 4 4 8 4
B 8 0 8 0 8 0
Document Page
5PROJECT MANAGEMENT
C 6 8 14 8 14 0
D 10 14 24 14 24 0
E 8 14 22 16 24 2
F 6 24 30 25 31 1
G 7 24 31 24 31 0
H 5 31 36 31 36 0
g) Critical path
Activit
y
Time ES
T
EF
T
LS
T
LF
T
Slac
k
Criticalit
y
(week
s)
A 4 0 4 4 8 4
B 8 0 8 0 8 0 **
C 6 8 14 8 14 0 **
D 10 14 24 14 24 0 **
E 8 14 22 16 24 2
F 6 24 30 25 31 1
G 7 24 31 24 31 0 **
H 5 31 36 31 36 0 **
h) Critical path duration
The critical path is = B-C-D-G-H = 8+6+10+7+5 = 36 weeks
Question 2
a) Bottom-up and top-down estimation
Bottom-up estimation is the low level within the business organization and it works
its way to determine the project budget. While the top-down estimation is started from
management level in addition it works for low level units.
The bottom-up estimation is provided with detailed cost estimation for each
individual project tasks to make project deliverables (Rauzana, 2018). On other hand, the top-
down estimation is helpful to estimate duration of the project deliverables.
Document Page
6PROJECT MANAGEMENT
Advantages and disadvantages of both cost estimation approaches:
Cost estimation
method
Advantages Disadvantages
Top-down
estimation
i. It takes less time as well as
effort to estimate the project
cost.
ii. It uses the holistic data from
the previous project to
identify possible unforeseen
project risks.
i. This cost estimation method
has lack of accuracy because
of eliminating of various
project details (Salari, Aria,
& Dehabadi, 2017).
ii. Support and entire business
is not realized benefit of the
business solutions.
Bottom-up
estimation
i. It leads to provide
greater accuracy of the
project cost (Rauzana,
2018).
ii. It provides accurate
project cost estimation
as includes expertise as
well as knowledge of
people to the cost
estimation work.
i. The organizational structure
recognized may change in
roll-out phase.
ii. A high level of project
requirements is required to
start project phases.
b) Project budgeting process
Contingency reserves
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
7PROJECT MANAGEMENT
It is important component of the project budgeting process as it is referred to amount
of quality of the project funds as well as financial resources compulsory to allocate at in
addition above designated approximation amount to reduce the risk of the cost overruns. It is
the cost added to project cost estimation by the project manager for some uncertain project
risks to manage recognized events (Brown et al., 2017). It is calculated by dividing total
overruns by entire associated business revenues provides the percentage to usage for the
contingency reserve.
Management reserves
The management reserves is important component in the budgeting process as the cost
reserve is used for managing unrecognized risks. It is a part of the project budgeting, but not
part of project cost baseline. It is not considered as estimated reserve, while it provides
figures as per the organizational rules and regulations. Mainly, it is calculated focused on
uncertainty of project work (Kim, 2018). When the management reserve is less, then there is
low level of the project uncertainty while if it is high, then the uncertainty is high. The project
manager is not responsible to control the management reserve, while the management is able
to do it.
c) Earned Value Management
Based on provided data,
Planned percentage complete = 70% and Actual % complete = 53%
The project budget = $20,500 and actual cost = $14,250.
i) Planned value (PV) = Planned % complete * Project budget
= 70% * $20,500 = $14,350, is the worth of work was planned to have been
completed by this status update.
Document Page
8PROJECT MANAGEMENT
ii) Earned value (EV) = Actual % complete * project budget
= 53% * $20,500 = $10,865, is the worth of work has been completed by this status
update.
iii) Percentage spent in terms of total budget
% of budget = [(Actual expenses – BAC) / BAC] * 100
= [($14,250 – $20,500) / $20,500] * 100 = 30.48%
iv) Cost variance (CV)
CV = EV – AC = $(10,865-14,250) = ($3,385), therefore the project is over the
budget of amount $3,385.
v) Scheduled variance (SV)
SV = EV- PV = = $(10,865-14,350) = ($3,485), therefore the project is behind the
schedule in $3,385.
vi) Cost performance index (CPI)
CPI = EV/ AC = $ (10,865/ 14,250) = 0.76, means the project is getting $0.76 worth
of value out of every $1 being spent.
vii) Schedule performance index (SPI)
SPI = EV/ PV = $ (10,865/ 14,350) = 0.75, means 75% rate slower the project is
progressing at compared to planned schedule.
viii) Estimate at completion
EAC = AC + (BAC – EV)
= $ 14,250 + $(20,500 – 10,865) = $23,885, the project is forecasted to cost.
Document Page
9PROJECT MANAGEMENT
ix) Variance at completion
VAC = BAC – EAC = $ (20,500 – 23,885) = ($3,385), the project is forecasted to be
over budget in $3,385.
x) Estimate to complete
ETC = (BAC – EV) / CPI = $(20,500 – 10,865) / 0.76 = $12,677.63, means the
estimated forecasted cost $23,885 to complete the project in $12,677.63.
d) Vendor selection
Based on the categorical analysis, Omnicron Ltd is required to select three vendors for
their procurement as well as delivery of the main project in supply chain project. As per my
point of view, this method is not suitable to select the vendor.
Constructing a weighted matrix is suitable for selection of the project vendor. The
vendor selection criteria are price, superiority, distribution, facility, social responsibility,
suitability, risk and agility (Dutta, Gwebu, & Wang, 2017). This method is not required for
weighting of each criteria and it is used as tool for exchanging with incompetent project
suppliers. It requires qualitative pairwise comparisons among the vendor selection criteria.
Disadvantages are that it does not support final selection of the vendor. There is a
strict proportion between the number of criteria for selection as well as number of the project
vendors (Duxbury & Haynie, 2018). This method is only limited to the quantitative criteria
for vendor selection.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10PROJECT MANAGEMENT
Question 3
a) Risk Management
i. Calculation of risk total
Risk
#
Identified risk factors Probability Impact Risk Total
(Probability *
Impact)
1 Communication misunderstandings 4.5 5.0 22.5
2 Cultural differences in work
expectations
4.5 4.0 18
3 Cultural perceptions 2.5 4.5 7
4 Multicultural team dynamics 4.0 3.5 15.75
5 Issues in virtual relationship
building
2.5 3.5 8.75
6 Time zone differences 3.5 2.5 8.75
7 Differences in technologies 2.5 2.0 5
Document Page
11PROJECT MANAGEMENT
ii. Risk management impact versus probability chart
0 1 2 3 4 5 6
0
1
2
3
4
5
6
R1
R2
R3
R4R5
R6
R7
Probability
Impact
Figure 2: Risk management impact versus probability chart
(Source: Created by author)
iii. Risk management
Risk # Identified risk factors Risk
categorization
Risk Management
1 Communication
misunderstandings
Avoid Project meeting among project
executive besides stakeholders
managed to interact the plan related
issues.
2 Cultural differences in work
expectations
Transfer In the workplace, there should need
to develop cultural self-awareness
for each of the project individuals so
that each team member should
respect other’s cultural background
(Ranković & Ivanović, 2018).
Accept
Mitigate
Transfer Avoid
Document Page
12PROJECT MANAGEMENT
3 Cultural perceptions Transfer Teamwork is required to have open
mind towards new project culture as
well as hold various team dynamics
on the shared teamwork.
4 Multicultural team
dynamics
Transfer It should require to minimize the
language barriers among the project
team members to ensure that there is
a mutual understanding among the
project members.
5 Issues in virtual relationship
building
Transfer It should require to schedule regular
project meetings and provide
detailed project deliverables in the
meeting (Hopkin, 2018).
6 Time zone differences Transfer There should require to create
reliable schedule so that each one
should available to do their work.
7 Differences in technologies Mitigate The team members are required to be
trained to handle various technical
works and equipment. Proper
planning and control of the
technological products and services
are required for the human benefits.
i. The project manager is not executing actual risk management plan as the project
sponsor mentioned that in the risk management plan document, it only shows the
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
13PROJECT MANAGEMENT
work breakdown structure, by the work packages of level 5 and it contains WBS
of nearly 100 risk events. The risks events are also not categorized in a proper
way. In presenting the project risks, the project management methodology is even
not provided with guidance leads to ineffective risk plan.
ii. The six steps to provide proper risk management plan are:
Risk planning: At this phase, the plan along with scope is to find out of the risk
management activities are to be allocated to the individuals.
Risk identification: It helps to classify the plan risks and avoids the plan risks
whenever possible (Ranković & Ivanović, 2018).
Qualitative risk analysis: It is based on judgement as well as experiences.
Quantitative risk analysis: It is determined by ranking the project risks by identifying
likelihood as well as impact of the project risks (Hopkin, 2018).
Risk response: Brainstorming session is conducted to gather data on both positive as
well as negative project risks. It is required to response to the project risks by mitigating,
transferring and avoiding it.
Risk monitoring and controlling: In the final stage, the plan risks are to be treated and
controlled.
Question 4
a) Evaluation of software tools
i. As a project management software, Jira is used by the project manager for assign
the plan tasks to end the project. It is a software tool used to view the project due
date and status report.
Document Page
14PROJECT MANAGEMENT
ii. Jira is used for project planning as well as management by the project IT teams.
Its workflow allows the users to control over project status and provide project
tracking information (Sajad et al., 2016). It can track time for each project tasks
that how much it is required to do the specific project tasks from its starting to its
ending. At the time to create the project tasks, creator assigns the project tasks
with estimated timeframe.
iii. Jira software tool is used to prioritize the project tasks efficiently, means which
task is important and is at high priority (Levin & Levin, 2019). Prioritization of
the project tasks help the project developer to finish the tasks in faster rate and in
provided deadline.
b) Limitations of software tools
i. The user interface of Jira is not user friendly, and it is one of the outcome of
being featured as heavy fit solution. It requires time to learn and familiar with
its usage effectively, therefore it is a time consuming process (Ortu et al.,
2016). When Jira is used for project planning, then the individual has lack of
using this software, would face lot of problems.
ii. There is lack of transparency at the time of sharing information with
development project team members. The developer requires time ti understand
assumptions behind project planning.
iii. Jira is not fit with the agile software development, as it disconnects with
people as well as makes the things more complicated. As it is difficult to use
for project planning, therefore it is confusing to be used for inexperienced
admin (Li, 2018). While the technical people love to use its complicated
configurations and use it.
Document Page
15PROJECT MANAGEMENT
iv.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
16PROJECT MANAGEMENT
References
Brown, J. L., Fisher, J. G., Peffer, S. A., & Sprinkle, G. B. (2017). The effect of budget
framing and budget-setting process on managerial reporting. Journal of Management
Accounting Research, 29(1), 31-44.
Dutta, D. K., Gwebu, K. L., & Wang, J. (2017). Strategy and vendor selection in IT
outsourcing: is there a method in the madness?. In Global sourcing of services:
Strategies, issues and challenges (pp. 451-477).
Duxbury, S. W., & Haynie, D. L. (2018). Building them up, breaking them down: Topology,
vendor selection patterns, and a digital drug market’s robustness to disruption. Social
Networks, 52, 238-250.
Hopkin, P. (2018). Fundamentals of risk management: understanding, evaluating and
implementing effective risk management. Kogan Page Publishers.
Kim, K. (2018). Using Real Options Analytics to Improve the Capital Budgeting Process
under Uncertainty.
Levin, S. P., & Levin, M. (2019). Managing Ideas, People, and Projects: Organizational
Tools and Strategies for Researchers. iScience.
Li, P. (2018). Jira Software Essentials: Plan, track, and release great applications with Jira
Software. Packt Publishing Ltd.
Ortu, M., Murgia, A., Destefanis, G., Tourani, P., Tonelli, R., Marchesi, M., & Adams, B.
(2016, May). The emotional side of software developers in JIRA. In 2016 IEEE/ACM
13th Working Conference on Mining Software Repositories (MSR) (pp. 480-483).
IEEE.
Document Page
17PROJECT MANAGEMENT
Ranković, N., & Ivanović, M. (2018, January). Risk Analysis Tools for Managing Software
Projects. In CEUR Workshop Proceedings.
Rauzana, A. (2018). Uncertainty variables on cost estimation in project construction. IOSR
Journal of Business and Management, 20(1), 80-86.
Sajad, M., Sadiq, M., Naveed, K., & Iqbal, M. S. (2016). Software Project Management:
Tools assessment, Comparison and suggestions for future development. International
Journal of Computer Science and Network Security (IJCSNS), 16(1), 31.
Salari, M., Aria, H. A., & Dehabadi, M. M. A. (2017). A new model for estimation of project
total cost in construction projects. IJIDS, 9(2), 128-143.
chevron_up_icon
1 out of 18
circle_padding
hide_on_mobile
zoom_out_icon
logo.png

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

Available 24*7 on WhatsApp / Email

[object Object]