Project Management Practices and Metrics

This assignment delves into the multifaceted world of project management. It requires an examination of various project management methodologies, practices, and key performance indicators (KPIs). Students are expected to analyze how these elements contribute to successful project delivery, considering aspects like planning, scheduling, risk management, and monitoring. The emphasis lies on understanding the practical application of project management principles and their impact on project outcomes.

Running head: PROJECT MANAGEMENT
Topic- Project Management
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
1. Measuring the quality of the Software.........................................................................................3
2. Project planning.......................................................................................................................5
2.1 Project scope..........................................................................................................................5
2.2 Feasibility study.....................................................................................................................6
2.3 Risk analysis..........................................................................................................................8
2.4 Resource Planning...............................................................................................................15
2.5 Estimate cost and effort.......................................................................................................16
2.6 Project schedule...................................................................................................................18
3. Providing a plan for project maintenance..................................................................................21
3.1 Introduction..........................................................................................................................21
3.2 Objectives............................................................................................................................22
3.3 Scope....................................................................................................................................22
3.4 System details......................................................................................................................22
3.4.1 Support infrastructure...................................................................................................22
3.4.2 Support roles and responsibilities.................................................................................23
3.4.3 Standards.......................................................................................................................24
3.4.4 Performance monitoring...............................................................................................24
3.5. Issues tracking....................................................................................................................25
4. Discussion on improving the process........................................................................................26
References......................................................................................................................................28

2
PROJECT MANAGEMENT
1. Measuring the quality of the Software
It is identified that the main aim of the developers is to develop software of high quality
within specified budget as well as time. In order to achieve this, the software must be developed
according to both the performance as well as functional requirements, documents as well as
characteristics expected. The main aim that exists in the levels of the project is to measure both
defects as well as errors (Whyte et al., 2016). These measures are generally utilized for deriving
metrics that helps in providing an efficacy of both software control activities as well as quality
assurance. It is found that there are number of measures that help in measuring the quality of the
software including functionality as well as interoperability. It is generally observed that
correctness, integrity, usability as well as maintainability are considered as the valuable
indicators for the project team.
Reliability: The system as well as the software must have the ability of maintaining the
performance level under different conditions. It is identified that reliability is defined as the
capability of the software product to perform different functions under different stated conditions
for a specified time for performing number of operations (Torchiano, Vetro & Iuliano, 2017). It
is generally measured by utilizing man time between failures (MTBF) which is considered as the
average time between different successive failures. Similarly MTBF is abbreviated as Mean time
repair and it is considered as the average time that is taken for repairing the machine after failure
generally occurs. For calculating the mean time to failure we need to MTBF= MTIR+ MTIF
Correctness: The software must always work correctly and correctness can be defined as
the degree through which the software helps in performing specified functions. It is generally

3
PROJECT MANAGEMENT
measured with the help of KDLOC (McIntosh et al., 2014). For different quality assessments, it
is identified that the defects are generally counted over certain period of time.
Maintainability: The maintenance of software is considered as one of the most
expensive as well as time consuming activity. Maintainability is generally defined as one of the
ease that helps in modifying the errors for meeting the requirements for making future
maintenance easier and for adapting with the changed environment (Seiffert et al., 2014).
Software maintainability is generally assessed with the help of indirect measures like MTTC
(Mean Time to Change) that is illustrated as the time that is needed for analyzing the design
modifications, change request, testing, implementing changes as well as distributing changes to
all the users. It is generally observed that most of the programs that have lower MITC that are
quite easier for maintenance.
Integrity: It is identified that software integrity is considered as one of the important
factor that helps in software development. It is generally defined as the degree that helps in
controlling the unauthorized access of various software components (Zhu & Azar, 2015). In
order to measure the software integrity, it is quite important to utilize security as well as threat. It
is identified that that is generally considered as a probability of some attack whereas security is
defined as the probability of repelling an attack that occurs.
Usability: It is identified that software is quite easy to understand and quite easy to use
that is generally preferred by different users. Usability is generally referred as the capability of
the software that must be properly learned, used as well as understood on various specified
conditions (Banerjee, Banerjee & Murarka, 2014). Additionally, it is found that lack of
conformance must be avoided in order to measure the quality of the software. It is found that in

4
PROJECT MANAGEMENT
order to achieve proper quality of software, it is quite important to achieve proper quality of
implicit as well as explicit requirements.
Defect removal efficiency: It is also required for measuring the quality of the software.
It is found that quality metrics are found to be beneficial at both processes as well as project
level. Control activities as well as quality assurance which are generally applied within the
software development are quite responsible for detecting various types of errors that is generally
introduced within different phases of SDLC (Faustino et al., 2017). It is found that this ability is
generally helpful in detecting errors that is mainly measured with the help of proper DRE that is
mainly calculated with the help of proper equation i.e. DRE= E/ (E+D) where E reflects the
number of errors that are generally found before the delivery of the software to the user whereas
D reflects the defects that is found after the delivery of the software.
2. Project planning
2.1 Project scope
The scope of the project is divided into in-scope as well as out-scope.
In-scope: The project in-scope is as follows:
 To extend the current computer system
 Encouraging high quality contributors for contributing information
 To provide incentives to the contributors
 To reward participants as per the categories of incentives
Out-scope: The project out-scope are as follows:
 Programmes will not be undertaken for promoting the participation of the contributors

5
PROJECT MANAGEMENT
 Qualification of the contributors are not analyzed
2.2 Feasibility study
The feasibility study generally helps in determining whether the project is worth doing or
not. This procedure is mainly followed in order to make proper determination about the
feasibility study. Once the feasibility of the project is determined then the analyst can easily
precede with the project specifications. In this project, numbers of feasibility studies are
undertaken.
Technical feasibility: It is identified that the equipments as well as software that is used
for extending the computer system is appropriate and thus they can easily satisfy the various
needs of the company. The technical feasibility generally helps in centering existing hardware,
software for supporting the extension of the computer system (Kerzner, 2013). While measuring
the technical feasibility of the system, the configuration of the system is generally provided
much more importance than the actual hardware. It is identified that the configuration of the
computer system helps in giving complete picture about the various requirements for the
extension of the computer system.
Economic feasibility: Economic analysis is considered as one of the most effective
method for evaluating the effectiveness of the project. It is identified that cost benefit analysis is
mainly utilized in order to determine the savings as well as benefits that are mainly expected as
outcome from the project (Burke, 2013). If the benefit that is gained from the project helps in
overweighing the cost then proper decision about implementation as well as design is required to
be made in order to implement the system. The cost benefit analysis is provided below:-
Cost Benefit Analysis

6
PROJECT MANAGEMENT
Benefits of option Year 1 Year 2 Year 3 Year 4 Year 5
Reduction in staff cost
$15,000.0
0
$15,000.0
0
$15,000.0
0
$15,000.0
0
$15,000.0
0
contingency planning cost
$25,000.0
0
$25,000.0
0
$25,000.0
0
$25,000.0
0
$25,000.0
0
Increased customer satisfaction
$16,000.0
0
$16,000.0
0
$16,000.0
0
$16,000.0
0
$16,000.0
0
Increase productivity
$14,000.0
0
$14,000.0
0
$14,000.0
0
$14,000.0
0
$14,000.0
0
Savings on overpaid resources
$
10,000.00
$
10,000.00
$
10,000.00
$
10,000.00
$
10,000.00
Total Benefits
$
80,000
$
80,000
$
80,000
$
80,000
$
80,000
Costs of option Year 1 Year 2 Year 3 Year 4 Year 5
Recruitment cost
$15,000.0
0
$
-
$
-
$
-
$
-
Cost for encouraging
contributors
$25,000.0
0
$25,000.0
0
$25,000.0
0
$25,000.0
0
$25,000.0
0
Cost for extending the
computer system
$16,000.0
0
$16,000.0
0
$16,000.0
0
$16,000.0
0
$16,000.0
0
Budget related with incentives
$14,000.0
0
$14,000.0
0
$14,000.0
0
$14,000.0
0
$14,000.0
0
Maintenance costs
$
10,000.00
$
10,000.00
$
10,000.00
$
10,000.00
$
10,000.00
Total Costs
$
80,000
$
65,000
$
65,000
$
65,000
$
65,000
Net benefits/costs
$
-
$
15,000
$
15,000
$
15,000
$
15,000
Cumulative benefits/costs
$
-
$
15,000
$
30,000
$
45,000
$
60,000
Net benefits/cost (NPV @ 5%)
$
-
$
15,000
$
45,000
$
90,000
$
150,000
Cumulative NPV $0.00
$15,000.0
0
$60,000.0
0
$150,000.
00
$300,000.
00
Year 1 Year 2 Year 3 Year 4 Year 5
$-
$50,000
$100,000
$150,000
$200,000
$250,000
$300,000
Net benefits/cost (NPV @ 5%) Cumulative NPV

7
PROJECT MANAGEMENT
Break Even Period
2.392189
679
Operational feasibility: The operational feasibility assists in determining how
acceptable the operation of the computer system is in the organization XYZ. It is identified that
operational feasibility helps in ensuring that the users can easily use the system and the system
will be quite advantageous for enhancing the number of contributors (Leach, 2014). Proper error
messages are generally provided as a sign of mistakes within the computer system that is set up
so that they do not face any problem. In addition to this, proper guideline menu must be provided
to the user so that they can easily work.
2.3 Risk analysis
Risk Type of
risk
Risk
statement
Impact Probability Risk
exposure
Risk
mitigation
Improper
estimation
of budget
Negative
risk
If the
budget of
the project
is not
estimated
properly
then it will
be quite
difficult for
High Medium High it is quite
important to
analyze the
market cost
of the
equipment
as well as
other
resources in

8
PROJECT MANAGEMENT
the
managers of
the project
to complete
the
extension of
the
computer
system
properly
within the
estimated
time and
resources.
order to
estimate the
budget of
the project
properly so
that the
entire work
of extension
will be
completed
within the
specified
time .
Improper
estimation
of time
Negative
risk
If the
project
managers
are not
experienced
and they do
not have
proper
knowledge
Medium Medium Medium It is
identified
that it is
quite
important to
hire proper
skilled as
well
experienced

9
PROJECT MANAGEMENT
in the
specific
project then
the chances
of incorrect
estimation
of time is
quite high.
project
managers so
that they can
estimate the
time for
completing
the
extension of
the
computers
within the
XYZ
company
properly.
Improper
management
Negative
risk
If the
project is
not
maintained
properly
then it is
quite
difficult for
the project
Medium High High It is very
much
important
for the
project
managers to
arrange
meetings
with the

10
PROJECT MANAGEMENT
managers to
complete
the entire
project
within the
estimated
budget as
well as
time.
stakeholders
of the
project so
that the
project can
be managed
properly and
it will be
further
assists in
completing
the entire
project on
proper
budget as
well as time.
Poor
quality of
materials
Negative
risk
The
materials
that are
utilized for
extension of
the
computer
Medium Low Medium It is very
much
important to
utilize
proper
quality of
materials so

11
PROJECT MANAGEMENT
system
within XYZ
company
for
enhancing
the number
of
contributors
are
important.
Improper
quality of
material use
can create
number of
issues as
well as
challenges
in
completing
the project.
that the
work of
extension
does not get
obstructed
due to poor
quality of
materials.
Lack of
proper
Negative
risk
It is
identified
Medium Medium Medium It is very
much

12
PROJECT MANAGEMENT
resources that
insufficient
number of
resources
creates
number of
problems
within the
project. If
proper
number
resources
are not
present for
the project
then it is
quite
difficult to
complete
the task
properly the
time that is
estimated.
important to
analyze the
works of the
project
properly so
that the
resources
required for
completing
the project
successfully
within the
estimated
time can be
easily
identified.

13
PROJECT MANAGEMENT
Improper
security
Negative
risk
If proper
security is
not
provided
then
confidential
as well as
sensitive
information
can get
leaked
which
further can
create
number of
issues
including
losing of
personal
information,
financial
information
and more
High High Medium Proper
security
must be
provided so
that
unauthorized
user does
not enter and
stole the
private
information
and thus the
information
will remain
secured.

14
PROJECT MANAGEMENT
2.4 Resource Planning
The resource planning of the project mainly helps in identifying all the different
resources that are generally needed in order to complete the project successfully. In this project,
the resources that are required for completing the project activities are provided in the table
below. The below table not only illustrates the activities in which the resources involve but also
highlights the duration of the resources (Mir & Pinnington, 2014). The resource planning mainly
highlights types of labor needed, roles and responsibilities of each labor and the total amount of
time required by each of the labor.
Resource Name Work
Project manager 656 hrs
Developing business case 64 hrs
Establishing project charter 80 hrs
Creating project plan 88 hrs
Creating financial plan 96 hrs
Creating risk plan 80 hrs
Creating communication plan 88 hrs
Creating procurement plan 72 hrs
Contracting with suppliers 80 hrs
Stakeholder sign off 8 hrs
Project planner 760 hrs
Undertaking feasibility study 72 hrs
Appointing project team members 56 hrs
Creating resource plan 120 hrs
Creating quality plan 104 hrs
Creating acceptance plan 72 hrs
Establishing project charter 80 hrs
Creating project plan 88 hrs
Creating communication plan 88 hrs
Contracting with suppliers 80 hrs
Supervisor 576 hrs
Designing new system architecture 96 hrs

15
PROJECT MANAGEMENT
Outsourcing the system to cloud service 120 hrs
Installation of hardware 96 hrs
Software installation 112 hrs
Go live 120 hrs
Final report 16 hrs
Final project review 16 hrs
Technician 312 hrs
Data design 80 hrs
Outsourcing the system to cloud service 120 hrs
Software installation 112 hrs
Developer 344 hrs
Developing user interface 64 hrs
Data design 80 hrs
Training users 80 hrs
Go live 120 hrs
Technical analyst 712 hrs
Creating quality plan 104 hrs
Creating risk plan 80 hrs
Creating procurement plan 72 hrs
Developing user interface 64 hrs
Designing new system architecture 96 hrs
Installation of hardware 96 hrs
Training users 80 hrs
Go live 120 hrs
Resource manager 648 hrs
Undertaking feasibility study 72 hrs
Appointing project team members 56 hrs
Creating resource plan 120 hrs
Creating financial plan 96 hrs
Creating acceptance plan 72 hrs
Creating procurement plan 72 hrs
Contracting with suppliers 80 hrs
Training users 80 hrs
2.5 Estimate cost and effort
Cost estimation is defined as a method of approximation of the cost or project or
operation. It generally has a single total value and generally has identifiable component value.

16
PROJECT MANAGEMENT
The cost estimation of this project is generally provided in the table below. It is analyzed that the
entire cost that is needed for extending the computer system of the XYZ organization is around
$164,680. This amount is generally required for completing the activities of the project
successfully. The cost estimation of the project must be done in an accurate, reliable as well as
transparent method as the entire project of extension depends on this budget (Flyvbjerg, 2013). If
the project managers are unable to complete the entire project of extending the computer system
within the organization XYZ then number of financial issues related with the organization will
rise. Therefore it is very much important to utilize proper techniques for estimating the budget of
the project in order to make the project successful.
Task Name Cost
Extending computer system in XYZ
company $164,680.00
Initiation phase $20,000.00
Developing business case $3,200.00
Undertaking feasibility study $5,400.00
Establishing project charter $7,200.00
Appointing project team members $4,200.00
Milestone 1:Completion of project
planning phase $0.00
Planning phase $71,640.00
Creating project plan $7,920.00
Creating resource plan $9,000.00
Creating financial plan $8,160.00
Creating quality plan $7,800.00
Creating risk plan $6,800.00
Creating acceptance plan $5,400.00
Creating communication plan $7,920.00
Creating procurement plan $8,640.00
Contracting with suppliers $10,000.00
Milestone 2: Completion of project
planning phase $0.00
System design phase $29,800.00
Developing user interface $5,120.00
Data design $6,800.00
Designing new system architecture $7,680.00

17
PROJECT MANAGEMENT
Outsourcing the system to cloud
service $10,200.00
Milestone 3: Completion of system
design phase $0.00
Implementation phase $41,400.00
Installation of hardware $7,680.00
Software installation $9,520.00
Training users $9,200.00
Go live $15,000.00
Milestone 4: Completion of milestone
phase $0.00
Closure phase $1,840.00
Stakeholder sign off $400.00
Final report $720.00
Final project review $720.00
Milestone 5: Completion of closure
phase $0.00
2.6 Project schedule
Project schedule is required in order to organize as well as complete the entire project of
extending the computer system in XYZ Company in a timely, financially as well as quality
responsive manner. It is found that effective project scheduling assists in playing a significant
role in ensuring the success of the project. In order to keep the entire project on track, proper
realistic time frames as well as proper resources must be assigned appropriately for managing the
quality for decreasing the errors of the project (Heldman, 2015). This generally assists in
minimizing cost as well as enhancing customer satisfaction. It is identified that project
scheduling generally helps in impacting the entire finances of the project. It is identified that time
constraints generally needs project managers in order to schedule the resources of the project
quite effectively. In addition to this, it is identified that project scheduling assists in ensuring that
the activities of the project are completed in a proper quality manner before the next activity of
the project starts (Kerzner, 2017). By assuring that the quality mea sue of the project is helpful in

18
PROJECT MANAGEMENT
meeting various expectations of the contributors, it can be analyzed that the scheduling
procedure is appropriate. The table below shows the entire schedule that is generally created in
order to extend the computer system for the XYZ Company.
WBS Task Name Duration Start Finish Predecessors Resource
Names Cost
0
Extending
computer system
in XYZ company
62 days Wed
11/1/17
Thu
1/25/18 $164,680.00
1 Initiation
phase 24 days Wed
11/1/17
Mon
12/4/17 $20,000.00
1.1 Developing
business case 8 days Wed
11/1/17
Fri
11/10/17
Project
manager $3,200.00
1.2 Undertaking
feasibility study 9 days Mon
11/13/17
Thu
11/23/17 2
Project
planner,
Resource
manager
$5,400.00
1.3 Establishing
project charter 10 days Mon
11/13/17
Fri
11/24/17 2
Project
manager,
Project
planner
$7,200.00
1.4
Appointing
project team
members
7 days Fri
11/24/17
Mon
12/4/17 3
Project
planner,
Resource
manager
$4,200.00
1.5
Milestone
1:Completion of
project planning
phase
0 days Thu
11/23/17
Thu
11/23/17 3 $0.00
2 Planning phase 33 days Fri
11/24/17
Tue
1/9/18 $71,640.00
2.1 Creating
project plan 11 days Mon
11/27/17
Mon
12/11/17 4
Project
manager,
Project
planner
$7,920.00
2.2 Creating
resource plan 15 days Tue
12/5/17
Mon
12/25/17 5
Project
planner,
Resource
manager
$9,000.00
2.3 Creating
financial plan
12 days Fri
11/24/17
Mon
12/11/17
6 Project
manager,
Resource
$8,160.00

19
PROJECT MANAGEMENT
manager
2.4 Creating
quality plan 13 days Fri
11/24/17
Tue
12/12/17 6
Project
planner,
Technical
analyst
$7,800.00
2.5 Creating risk
plan 10 days Tue
12/12/17
Mon
12/25/17 8
Project
manager,
Technical
analyst
$6,800.00
2.6 Creating
acceptance plan 9 days Tue
12/12/17
Fri
12/22/17 8
Project
planner,
Resource
manager
$5,400.00
2.7
Creating
communication
plan
11 days Tue
12/26/17
Tue
1/9/18 9
Project
manager,
Project
planner
$7,920.00
2.8 Creating
procurement plan 9 days Tue
12/12/17
Fri
12/22/17 10
Project
manager,
Resource
manager,
Technical
analyst
$8,640.00
2.9 Contracting
with suppliers 10 days Tue
12/12/17
Mon
12/25/17 10
Project
manager,
Project
planner,
Resource
manager
$10,000.00
2.10
Milestone 2:
Completion of
project planning
phase
0 days Tue
12/12/17
Tue
12/12/17 11 $0.00
3 System design
phase 23 days Wed
12/13/17
Fri
1/12/18 $29,800.00
3.1 Developing
user interface 8 days Wed
12/13/17
Fri
12/22/17 11
Developer,
Technical
analyst
$5,120.00
3.2 Data design 10 days Tue
12/26/17
Mon
1/8/18 12 Developer,
Technician $6,800.00
3.3
Designing
new system
architecture
12 days Mon
12/25/17
Tue
1/9/18 13
Supervisor,
Technical
analyst
$7,680.00
3.4 Outsourcing
the system to
15 days Mon
12/25/17
Fri
1/12/18
13 Supervisor,
Technician
$10,200.00

20
PROJECT MANAGEMENT
cloud service
3.5
Milestone 3:
Completion of
system design
phase
0 days Tue
1/9/18
Tue
1/9/18 14 Developer,
Technician $0.00
4 Implementation
phase
24 days Mon
12/25/17
Thu
1/25/18 $41,400.00
4.1 Installation of
hardware 12 days Wed
1/10/18
Thu
1/25/18 14
Supervisor,
Technical
analyst
$7,680.00
4.2 Software
installation 14 days Mon
12/25/17
Thu
1/11/18 15 Supervisor,
Technician $9,520.00
4.3 Training users 10 days Mon
12/25/17
Fri
1/5/18 15
Developer,
Resource
manager,
Technical
analyst
$9,200.00
4.4 Go live 15 days Tue
12/26/17
Mon
1/15/18 16
Developer,
Supervisor,
Technical
analyst
$15,000.00
4.5
Milestone 4:
Completion of
milestone phase
0 days Mon
12/25/17
Mon
12/25/17 16 $0.00
5 Closure phase 25 days Wed
12/13/17
Tue
1/16/18 $1,840.00
5.1 Stakeholder
sign off 1 day Wed
12/13/17
Wed
12/13/17 17 Project
manager $400.00
5.2 Final report 2 days Mon
1/15/18
Tue
1/16/18 18 Supervisor $720.00
5.3 Final project
review 2 days Mon
12/25/17
Tue
12/26/17 19 Supervisor $720.00
5.4
Milestone 5:
Completion of
closure phase
0 days Mon
1/8/18
Mon
1/8/18 20 $0.00

21
PROJECT MANAGEMENT
3. Providing a plan for project maintenance
3.1 Introduction
The company “XYZ” wants to extend its current computer system in order to provide
incentives in the form of reward to the contributor who generally participates to provide their
latest information about the technology trends on the website of XYZ. The project mainly deals
with the extension of the current computer system of the company. During this project it is quite
important to follow proper maintenance plan so that the project can be completed successfully
within the estimated time as well as budget. It is required to be performed in order to repair the
existing faults or problems in the project that can obstruct the extension of the computer system
3.2 Objectives
The objectives of the maintenance plan are as follows:
 To prevent problems that can create issues for the project
 To maintain the resources as well as requirements of the project
 To repair existing faults associated with the project
3.3 Scope
The scopes of the project are as follows:
 To ensure that the systems are running properly
 Performing and testing backup
 Monitor of extended computer system
 Ensuring contingency planning for the disaster recovery
 Maintaining performance measurements, system logs as well as statistics.

22
PROJECT MANAGEMENT
3.4 System details
3.4.1 Support infrastructure
The supporting infrastructures are as follows:
Software installation: Proper software is installed within the systems that act as a
supporting infrastructure for the project to go live. Software installation must be done correctly
so that it must have proper positive outcome.
Designing architecture: The architecture for extension of the current computer system
must be done properly so that the organization can prove the reward for participation easily
(White, 2016).
Training: Proper training must be provided so that the team members can work well and
can able to support the project in going live.
Security: Proper security measures must be taken so that confidential as well as sensitive
information can be kept secured.
3.4.2 Support roles and responsibilities
The maintenance plan can be supported by performing several activities that are as
follows:
Ensure that the extension of the system is done properly: The role of the maintenance
team is to ensure that the current computer system which is extended must be done in a proper
way so that the XYZ Company can provide rewards on the basis of participation to the
contributors.

23
PROJECT MANAGEMENT
Ensures that the system is working appropriately: The maintenance team takes the
responsibility for monitoring that the current computer system is working properly and both the
contributors as well as the company is not facing any issue (Laporte, O'Connor & Fanmuy,
2013).
Reviews problems or issues associated with project: The issues or problems that are
associated with the project or the computer system must be reviewed by the maintenance team so
that the problems can be solved easily.
Provide technical guidance for proper performance of the system: Proper technical
guidance must be provided so that the system can be maintained properly and their performance
is also proper.
3.4.3 Standards
The standards that are followed in the project are elaborated below:
Time reporting responsibilities: Each team member is generally responsible of
completing a weekly status report for using proper standard format for the different reports that
are available.
Team member responsibilities: The time that is spent on the project must be recorded
on the time sheets (Campbell & Reyes-Picknell, 2015). All the hour must be recorded as per the
accounting change number that is generally assigned by the project office as project accounting
standards and procedures are followed.

24
PROJECT MANAGEMENT
Revising project plan: The team leaders are generally responsible of providing
appropriate details about the project plan as well as changes. It generally comprises of all the
different project resources and helps in reflecting the different standards of the project.
3.4.4 Performance monitoring
The performance can be monitored by utilizing certain techniques that are elaborated
below:
Assessing achievements: It is quite important to assess the achievements or the potential
of achieving different financial, technical as well as economic goals as well as objectives of the
project.
Determine the nature and form of actions: It is quite important to determine the nature
as well as form of various corrective actions that are generally needed for achieving the goals
and for monitoring different performance indicators (Motawa & Almarshad, 2013).
Assist in defining different performance measures: Different types of performance
measure must be defined for replacing the ineffective policies or strategies.
3.5. Issues tracking
The issues can be logged, tracked as well as dealt properly by using methods that are as
follows:
Issue resolution: Issue resolution is defined as a process that helps in recording as well
as handling event or problems that generally threatens the success of the project.

25
PROJECT MANAGEMENT
Recording project issues: The identified issue must be recorded within the issue log and
after then it is decided who owns it and who is accountable for managing the various issues
(Siewiorek & Swarz, 2017).
Managing project issues: The issues of the project must be managed by the project
manager so that it does not obstruct the success of the project.
4. Discussion on improving the process
The process of project maintenance can be improved by utilizing the methods that are as
follows:
Identification of the requirement for change: The first step for improving the
procedure is to identify the need for change. It is identified that one of the useful way of
discovering various types of improvement is by conducting proper process audit. The audit
report helps in prioritizing the area of procedure reporting that will be quite useful in analyzing
as well as indentifying the requirement for the process change.
Analyzing current processes: Once the procedure is decided then one can improve the
need for analyzing the current process (Cooper, 2016). Regardless, of proper tool one can select
analysis for improving the current processes. Proper process must be analyzed and then used in
order to improve the procedure of the project.
Obtaining current commitment and support: The third step of process improvement is
to solicit the commitment off senior management. This is considered as one of the most
important element for the success of the project (Walker, 2015). It is identified that at his step, it
is quite important to present the changes and their impacts properly. It is quite important for the

26
PROJECT MANAGEMENT
management to understand the necessity of the need for the change for ensuring that they will
support proper recommendations.
Creation of proper improvement strategy: With the help of process analysis phase, it
is quite important to develop proper strategy (Pearce et al., 2017). It is recommended that proper
steps in the process must be improved for analyze type of resource as well as financial
implications. It is identified that proper improvement objectives must be created for
recommending realistic as well as measurable objectives that will generally align with the overall
strategic goals of the project.