Project Management and Risk Mitigation
VerifiedAdded on 2020/03/28
|21
|3326
|318
AI Summary
This assignment analyzes the importance of effective project management, particularly focusing on risk identification and mitigation. It examines the impact of poor project management practices and highlights the value of a robust risk management framework. The provided articles discuss the relationship between project success and effective project management execution, as well as methods for measuring performance and achieving successful outcomes. A closure checklist outlines key project milestones and stakeholder responsibilities, while a MOV (Measures of Value) analysis identifies the system's potential impact on financial, strategic, customer, social, and operational aspects.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: PROJECT MANAGEMENT
Case Study-RAILS Rostering System
Name of the Student
Name of the University
Author’s Note
Case Study-RAILS Rostering System
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.
1
PROJECT MANAGEMENT
Table of Contents
1. Project overview.....................................................................................................................3
2. Measurable Organizational Value..........................................................................................3
2.1 Area of Impact..................................................................................................................3
2.2 Project plan value.............................................................................................................4
2.3 Involvement of the stakeholders in the project plan........................................................4
2.4 Appropriate metric and timeframe...................................................................................4
3. Scope management plan.........................................................................................................6
3.1 Detailed scope of the project............................................................................................6
3.2 List of resources...............................................................................................................7
4. Project schedule and WBS.....................................................................................................8
4.1 Project schedule...............................................................................................................8
4.2 WBS...............................................................................................................................12
4.3 Milestone of the project plan..........................................................................................13
. Project risk analysis and plan.................................................................................................13
5.1 Project assumption.........................................................................................................13
5.2 risk assessment...............................................................................................................13
6. Quality management plan....................................................................................................17
6.1 Philosophy for delivering a quality system to the client................................................17
6.2 Quality issues.................................................................................................................17
Bibliography.............................................................................................................................19
Appendices...............................................................................................................................21
Appendix 1: Annotated bibliography...................................................................................21
Appendix 2: Closure checklist.............................................................................................22
Appendix 3: MOV................................................................................................................23
PROJECT MANAGEMENT
Table of Contents
1. Project overview.....................................................................................................................3
2. Measurable Organizational Value..........................................................................................3
2.1 Area of Impact..................................................................................................................3
2.2 Project plan value.............................................................................................................4
2.3 Involvement of the stakeholders in the project plan........................................................4
2.4 Appropriate metric and timeframe...................................................................................4
3. Scope management plan.........................................................................................................6
3.1 Detailed scope of the project............................................................................................6
3.2 List of resources...............................................................................................................7
4. Project schedule and WBS.....................................................................................................8
4.1 Project schedule...............................................................................................................8
4.2 WBS...............................................................................................................................12
4.3 Milestone of the project plan..........................................................................................13
. Project risk analysis and plan.................................................................................................13
5.1 Project assumption.........................................................................................................13
5.2 risk assessment...............................................................................................................13
6. Quality management plan....................................................................................................17
6.1 Philosophy for delivering a quality system to the client................................................17
6.2 Quality issues.................................................................................................................17
Bibliography.............................................................................................................................19
Appendices...............................................................................................................................21
Appendix 1: Annotated bibliography...................................................................................21
Appendix 2: Closure checklist.............................................................................................22
Appendix 3: MOV................................................................................................................23
2
PROJECT MANAGEMENT
1. Project overview
The organization “Riverina Agricultural and lifestyle show” was established in the
year 2000. It is identified that with time, show was expanding its business. As the show was
dependent on the volunteers, with the expansion in the business, they want proper system for
handling the volunteers properly. As a result the business wants to develop rostering system
that not only assists in handling volunteers but also helps in in reducing the response time.
The paper mainly focuses on measurable organizational goal, scope management
plan, schedule and Gantt chart. It is identified that the paper also focuses on quality
management plan as well as risk management plan.
2. Measurable Organizational Value
2.1 Area of Impact
The impact areas include:
Financial: The money which is invested by the organization provides appropriate
return of profit for the business.
Strategy: The developed system tracks the volunteers by the show by utilizing
specific information which is stored within the system.
Customer: The system that is developed assists in resolving different types of
questions or request which are raised by the clients or the customers.
Social: The procedure of communication became easier with the help of the system
development.
PROJECT MANAGEMENT
1. Project overview
The organization “Riverina Agricultural and lifestyle show” was established in the
year 2000. It is identified that with time, show was expanding its business. As the show was
dependent on the volunteers, with the expansion in the business, they want proper system for
handling the volunteers properly. As a result the business wants to develop rostering system
that not only assists in handling volunteers but also helps in in reducing the response time.
The paper mainly focuses on measurable organizational goal, scope management
plan, schedule and Gantt chart. It is identified that the paper also focuses on quality
management plan as well as risk management plan.
2. Measurable Organizational Value
2.1 Area of Impact
The impact areas include:
Financial: The money which is invested by the organization provides appropriate
return of profit for the business.
Strategy: The developed system tracks the volunteers by the show by utilizing
specific information which is stored within the system.
Customer: The system that is developed assists in resolving different types of
questions or request which are raised by the clients or the customers.
Social: The procedure of communication became easier with the help of the system
development.
3
PROJECT MANAGEMENT
Keep satisfied
CEO of Globex
Manage closely
Project team
Monitor
Volunteers of
the show
Keep informed
Staff of RAIILS
Staffs of the Show
S
Interest
Power
Operational: The operation cost of the business reduced with the development of the
system.
2.2 Project plan value
The values of project plan are as follows:
Better: The development of rostering system is very much beneficial as it helps in
providing proper facility to both the customers as well as volunteers.
Cheaper: Due to the development of the system,, the budget that is spent by the
organization on resources reduces.
Faster: The system assists in minimizing the response time and as a result both
customers as well as volunteers can communicate quite faster.
2.3 Involvement of the stakeholders in the project plan
The involvements of the stakeholder’s project plan are as follows:
2.4 Appropriate metric and timeframe
Rank Impact Metrics Timeframe
PROJECT MANAGEMENT
Keep satisfied
CEO of Globex
Manage closely
Project team
Monitor
Volunteers of
the show
Keep informed
Staff of RAIILS
Staffs of the Show
S
Interest
Power
Operational: The operation cost of the business reduced with the development of the
system.
2.2 Project plan value
The values of project plan are as follows:
Better: The development of rostering system is very much beneficial as it helps in
providing proper facility to both the customers as well as volunteers.
Cheaper: Due to the development of the system,, the budget that is spent by the
organization on resources reduces.
Faster: The system assists in minimizing the response time and as a result both
customers as well as volunteers can communicate quite faster.
2.3 Involvement of the stakeholders in the project plan
The involvements of the stakeholder’s project plan are as follows:
2.4 Appropriate metric and timeframe
Rank Impact Metrics Timeframe
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
4
PROJECT MANAGEMENT
1 Operational The operation cost of
the business reduced
with the development
of the system.
2 months
2 Customer The system that is
developed assists in
resolving different
types of questions or
request which are
raised by the clients
or the customers
1 month
3 Strategy The developed
system tracks the
volunteers by the
show by utilizing
specific information
which is stored
within the system.
2 months
4 Financial The money which is
invested by the
organization provides
appropriate return of
profit for the
business.
3 months
PROJECT MANAGEMENT
1 Operational The operation cost of
the business reduced
with the development
of the system.
2 months
2 Customer The system that is
developed assists in
resolving different
types of questions or
request which are
raised by the clients
or the customers
1 month
3 Strategy The developed
system tracks the
volunteers by the
show by utilizing
specific information
which is stored
within the system.
2 months
4 Financial The money which is
invested by the
organization provides
appropriate return of
profit for the
business.
3 months
5
PROJECT MANAGEMENT
5 Social The procedure of
communication
became easier with
the help of the system
development.
2 months
3. Scope management plan
3.1 Detailed scope of the project
Requirements: The rostering system is mainly needed by the show as they want to
handle the volunteers so that the show can be managed properly. In addition to this, the
system is also needed for speeding the organizational operation.
In scope and out scope:
In scope: The in-scope of the project includes:
Development of proper and effective rostering system in order to handle the
volunteers
Documents associated with non-functional as well as functional requirement are
properly created.
Different types of personal as well as professional detail are incorporated within the
system about the volunteers.
Out scope: The out score of the project include:
Appropriate security of information is not providing.
The workers are not trained
PROJECT MANAGEMENT
5 Social The procedure of
communication
became easier with
the help of the system
development.
2 months
3. Scope management plan
3.1 Detailed scope of the project
Requirements: The rostering system is mainly needed by the show as they want to
handle the volunteers so that the show can be managed properly. In addition to this, the
system is also needed for speeding the organizational operation.
In scope and out scope:
In scope: The in-scope of the project includes:
Development of proper and effective rostering system in order to handle the
volunteers
Documents associated with non-functional as well as functional requirement are
properly created.
Different types of personal as well as professional detail are incorporated within the
system about the volunteers.
Out scope: The out score of the project include:
Appropriate security of information is not providing.
The workers are not trained
6
PROJECT MANAGEMENT
Deliverables: The project deliverables include:
Development phase documentation
Project requirement documentation
Planning as well as testing system
Procedure development for verification of scope
Scope verification procedure: It is reflected by the acceptance criteria that various
demands and requirements of the customers are properly met. It also elaborates that the
system is quite useful in minimizing response time which is quite beneficial for both the
volunteers as well as the customers.
3.2 List of resources
The various types of resources include:
Human resources: The required human resources are as follows:
System analyst
Project manager
Executive sponsor
Risk manager
System tester
Requirement analyst
Material resources: The various types of material resources which are required in the
project are as follows:
Secondary storage
CPU
Display adapter
PROJECT MANAGEMENT
Deliverables: The project deliverables include:
Development phase documentation
Project requirement documentation
Planning as well as testing system
Procedure development for verification of scope
Scope verification procedure: It is reflected by the acceptance criteria that various
demands and requirements of the customers are properly met. It also elaborates that the
system is quite useful in minimizing response time which is quite beneficial for both the
volunteers as well as the customers.
3.2 List of resources
The various types of resources include:
Human resources: The required human resources are as follows:
System analyst
Project manager
Executive sponsor
Risk manager
System tester
Requirement analyst
Material resources: The various types of material resources which are required in the
project are as follows:
Secondary storage
CPU
Display adapter
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
7
PROJECT MANAGEMENT
Operating system
4. Project schedule and WBS
4.1 Project schedule
WBS Task Name Duration Start Finish
0 RAILS Rostering System 163 days
Tue 26-09-
17
Thu 10-05-
18
1
Conceptualization and project
initialization
29 days
Tue 26-09-
17
Fri 03-11-
17
1.1
Project charter and plan
development
11 days
Tue 26-09-
17
Tue 10-10-
17
1.1.1 Identification of requirements 3 days
Tue 26-09-
17
Thu 28-09-
17
1.1.2 Determining project specification 4 days Fri 29-09-17
Wed 04-10-
17
1.1.3 Meeting plan of the project 4 days
Thu 05-10-
17
Tue 10-10-
17
1.2 Vendor appointment 18 days
Wed 11-10-
17
Fri 03-11-
17
1.2.1 Identification of vendors 4 days
Wed 11-10-
17
Mon 16-10-
17
1.2.2 Determining vendor's capability 5 days
Tue 17-10-
17
Mon 23-10-
17
1.2.3 Planning of budget 5 days Tue 24-10- Mon 30-10-
PROJECT MANAGEMENT
Operating system
4. Project schedule and WBS
4.1 Project schedule
WBS Task Name Duration Start Finish
0 RAILS Rostering System 163 days
Tue 26-09-
17
Thu 10-05-
18
1
Conceptualization and project
initialization
29 days
Tue 26-09-
17
Fri 03-11-
17
1.1
Project charter and plan
development
11 days
Tue 26-09-
17
Tue 10-10-
17
1.1.1 Identification of requirements 3 days
Tue 26-09-
17
Thu 28-09-
17
1.1.2 Determining project specification 4 days Fri 29-09-17
Wed 04-10-
17
1.1.3 Meeting plan of the project 4 days
Thu 05-10-
17
Tue 10-10-
17
1.2 Vendor appointment 18 days
Wed 11-10-
17
Fri 03-11-
17
1.2.1 Identification of vendors 4 days
Wed 11-10-
17
Mon 16-10-
17
1.2.2 Determining vendor's capability 5 days
Tue 17-10-
17
Mon 23-10-
17
1.2.3 Planning of budget 5 days Tue 24-10- Mon 30-10-
8
PROJECT MANAGEMENT
17 17
1.2.4 Time scheduling 4 days
Tue 31-10-
17
Fri 03-11-
17
1.2.5
Milestone: Initialization as well as
conceptualization completion
0 days Fri 03-11-17
Fri 03-11-
17
2 Rostering system design phase 22 days
Mon 06-11-
17
Tue 05-12-
17
2.1 Improvement of labour management 4 days
Mon 06-11-
17
Thu 09-11-
17
2.2 improvement of procedure installation 5 days Fri 10-11-17
Thu 16-11-
17
2.3 Building initiation 6 days Fri 17-11-17
Fri 24-11-
17
2.4
Understanding the requirements of
milestones
7 days
Mon 27-11-
17
Tue 05-12-
17
2.5
Milestone: Rostering system design
phase completion
0 days
Tue 05-12-
17
Tue 05-12-
17
3
Rostering system implementation
system
36 days
Wed 06-12-
17
Wed 24-
01-18
3.1 System implementation 10 days
Wed 06-12-
17
Tue 19-12-
17
3.2 Implementation phase modification 8 days
Wed 20-12-
17
Fri 29-12-
17
3.3 Reviewing requirements 9 days Mon 01-01- Thu 11-01-
PROJECT MANAGEMENT
17 17
1.2.4 Time scheduling 4 days
Tue 31-10-
17
Fri 03-11-
17
1.2.5
Milestone: Initialization as well as
conceptualization completion
0 days Fri 03-11-17
Fri 03-11-
17
2 Rostering system design phase 22 days
Mon 06-11-
17
Tue 05-12-
17
2.1 Improvement of labour management 4 days
Mon 06-11-
17
Thu 09-11-
17
2.2 improvement of procedure installation 5 days Fri 10-11-17
Thu 16-11-
17
2.3 Building initiation 6 days Fri 17-11-17
Fri 24-11-
17
2.4
Understanding the requirements of
milestones
7 days
Mon 27-11-
17
Tue 05-12-
17
2.5
Milestone: Rostering system design
phase completion
0 days
Tue 05-12-
17
Tue 05-12-
17
3
Rostering system implementation
system
36 days
Wed 06-12-
17
Wed 24-
01-18
3.1 System implementation 10 days
Wed 06-12-
17
Tue 19-12-
17
3.2 Implementation phase modification 8 days
Wed 20-12-
17
Fri 29-12-
17
3.3 Reviewing requirements 9 days Mon 01-01- Thu 11-01-
9
PROJECT MANAGEMENT
18 18
3.4 Verification of equipments 9 days Fri 12-01-18
Wed 24-01-
18
3.5
Milestone: Rostering system
implementation system completion
0 days
Wed 24-01-
18
Wed 24-
01-18
4 Testing phase 39 days
Thu 25-01-
18
Tue 20-03-
18
4.1 Testing phase initiation 5 days
Thu 25-01-
18
Wed 31-01-
18
4.2 Test plan reporting 34 days
Thu 01-02-
18
Tue 20-03-
18
4.2.1 Test plan reviewing 8 days
Thu 01-02-
18
Mon 12-02-
18
4.2.2 Carrying out entire plan 7 days
Tue 13-02-
18
Wed 21-02-
18
4.2.3 Analyzing test plan 9 days
Thu 22-02-
18
Tue 06-03-
18
4.2.4 Presentation of test result 10 days
Wed 07-03-
18
Tue 20-03-
18
4.2.5 Milestone: Sign off the test result 0 days
Tue 20-03-
18
Tue 20-03-
18
5 Risk management phase 33 days
Wed 21-03-
18
Fri 04-05-
18
5.1 Risk possibility recognition 5 days Wed 21-03- Tue 27-03-
PROJECT MANAGEMENT
18 18
3.4 Verification of equipments 9 days Fri 12-01-18
Wed 24-01-
18
3.5
Milestone: Rostering system
implementation system completion
0 days
Wed 24-01-
18
Wed 24-
01-18
4 Testing phase 39 days
Thu 25-01-
18
Tue 20-03-
18
4.1 Testing phase initiation 5 days
Thu 25-01-
18
Wed 31-01-
18
4.2 Test plan reporting 34 days
Thu 01-02-
18
Tue 20-03-
18
4.2.1 Test plan reviewing 8 days
Thu 01-02-
18
Mon 12-02-
18
4.2.2 Carrying out entire plan 7 days
Tue 13-02-
18
Wed 21-02-
18
4.2.3 Analyzing test plan 9 days
Thu 22-02-
18
Tue 06-03-
18
4.2.4 Presentation of test result 10 days
Wed 07-03-
18
Tue 20-03-
18
4.2.5 Milestone: Sign off the test result 0 days
Tue 20-03-
18
Tue 20-03-
18
5 Risk management phase 33 days
Wed 21-03-
18
Fri 04-05-
18
5.1 Risk possibility recognition 5 days Wed 21-03- Tue 27-03-
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
10
PROJECT MANAGEMENT
18 18
5.2 Addressing risk 7 days
Wed 28-03-
18
Thu 05-04-
18
5.3 Mitigation plan 6 days Fri 06-04-18
Fri 13-04-
18
5.4 Risk register 7 days
Mon 16-04-
18
Tue 24-04-
18
5.5 Reviewing risk impact 8 days
Wed 25-04-
18
Fri 04-05-
18
5.6
Milestone: Sign off the risk plan
document
0 days Fri 04-05-18
Fri 04-05-
18
6 Close project phase 4 days
Mon 07-05-
18
Thu 10-05-
18
6.1 Project success evaluation 2 days
Mon 07-05-
18
Tue 08-05-
18
6.2 Review of final project 2 days
Wed 09-05-
18
Thu 10-05-
18
6.3
Milestone: Sign off the final
completion document
0 days
Thu 10-05-
18
Thu 10-05-
18
PROJECT MANAGEMENT
18 18
5.2 Addressing risk 7 days
Wed 28-03-
18
Thu 05-04-
18
5.3 Mitigation plan 6 days Fri 06-04-18
Fri 13-04-
18
5.4 Risk register 7 days
Mon 16-04-
18
Tue 24-04-
18
5.5 Reviewing risk impact 8 days
Wed 25-04-
18
Fri 04-05-
18
5.6
Milestone: Sign off the risk plan
document
0 days Fri 04-05-18
Fri 04-05-
18
6 Close project phase 4 days
Mon 07-05-
18
Thu 10-05-
18
6.1 Project success evaluation 2 days
Mon 07-05-
18
Tue 08-05-
18
6.2 Review of final project 2 days
Wed 09-05-
18
Thu 10-05-
18
6.3
Milestone: Sign off the final
completion document
0 days
Thu 10-05-
18
Thu 10-05-
18
11
PROJECT MANAGEMENT
Figure 1: Gantt chart
(Source: Created by Author)
PROJECT MANAGEMENT
Figure 1: Gantt chart
(Source: Created by Author)
12
PROJECT MANAGEMENT
4.2 WBS
RAILS Rostering System
Conceptuliation and
project initialization
Project charter and plan
development
Identification of
requirements
Determining proect
specification
Meeting plan of the
project
Vendor appointment
Identification of
vendors
Determining
vendor's capability
Planning of budget
Time schedulling
Milestone:
Initialization as well as
conceptualization
completion
Rostering system design
phase
Improvement of
labour management
improvement of
procedure
installation
Building initiation
Understanding the
requirements of
milestones
Milestione:
Rostering system
design phase
completion
Rostering system
implementatation system
System
implemenattion
Implemenattion
phase modification
Reviewing
requirements
Verfication of
equipments
Milestone:
Rostering system
implementation
system completion
Testing phase
Testing phase
initiation Test plan reporting
Test plan review ing
Carring out etire
plan
Analyzing test plan
Presentation of test
result
Milestone: Signn off
the test result
Risk management phase
Risk possibility
recognition
Addressing riisk
Mitigation plan
Risk register
Reviewing risk
imapct
Milestone: Sign off
the risk plan
document
Close project phase
Project success
evaluation
Review of final
project
Milestone: Sign off
the final completion
document
Figure 2: WBS
(Source: Created by Author)
4.3 Milestone of the project plan
WBS Task Name Expected date
1. Initialization as well as conceptualization completion Fri 03-11-17
2. Rostering system design phase completion Tue 05-12-17
3. Rostering system implementation system completion Wed 24-01-18
4. Sign off the test result Tue 20-03-18
5. Sign off the risk plan document Fri 04-05-18
6. Sign off the final completion document Thu 10-05-18
PROJECT MANAGEMENT
4.2 WBS
RAILS Rostering System
Conceptuliation and
project initialization
Project charter and plan
development
Identification of
requirements
Determining proect
specification
Meeting plan of the
project
Vendor appointment
Identification of
vendors
Determining
vendor's capability
Planning of budget
Time schedulling
Milestone:
Initialization as well as
conceptualization
completion
Rostering system design
phase
Improvement of
labour management
improvement of
procedure
installation
Building initiation
Understanding the
requirements of
milestones
Milestione:
Rostering system
design phase
completion
Rostering system
implementatation system
System
implemenattion
Implemenattion
phase modification
Reviewing
requirements
Verfication of
equipments
Milestone:
Rostering system
implementation
system completion
Testing phase
Testing phase
initiation Test plan reporting
Test plan review ing
Carring out etire
plan
Analyzing test plan
Presentation of test
result
Milestone: Signn off
the test result
Risk management phase
Risk possibility
recognition
Addressing riisk
Mitigation plan
Risk register
Reviewing risk
imapct
Milestone: Sign off
the risk plan
document
Close project phase
Project success
evaluation
Review of final
project
Milestone: Sign off
the final completion
document
Figure 2: WBS
(Source: Created by Author)
4.3 Milestone of the project plan
WBS Task Name Expected date
1. Initialization as well as conceptualization completion Fri 03-11-17
2. Rostering system design phase completion Tue 05-12-17
3. Rostering system implementation system completion Wed 24-01-18
4. Sign off the test result Tue 20-03-18
5. Sign off the risk plan document Fri 04-05-18
6. Sign off the final completion document Thu 10-05-18
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
13
PROJECT MANAGEMENT
. Project risk analysis and plan
5.1 Project assumption
` The assumptions that are made include:
Budget: The budget which is required for rostering system development is accurately
estimated.
Time: The time which is required for rostering system development is accurately
estimated.
Resources: The resources that are needed in order to complete the development of the
system successfully are correctly estimated.
5.2 risk assessment
N
o.
Ra
nk
Risk Descri
ption
Categ
ory
Root
Cause
Potenti
al
Respo
nses
Risk
Owne
r
Proba
bility
Imp
act
Stat
us
R
4
4
1 In
effectiv
e
budget
assump
tion
Due to
ineffect
ive
budget
estimati
on the
organiz
ation
will
Finan
cials
risk
Due to
inappro
priate
knowle
dge
about
the
needs
as well
The
project
manage
r must
analyze
the
require
ments
of the
Finan
cials
mana
ger
Mediu
m
High Will
be
mitig
ated
in 2
mont
hs.
PROJECT MANAGEMENT
. Project risk analysis and plan
5.1 Project assumption
` The assumptions that are made include:
Budget: The budget which is required for rostering system development is accurately
estimated.
Time: The time which is required for rostering system development is accurately
estimated.
Resources: The resources that are needed in order to complete the development of the
system successfully are correctly estimated.
5.2 risk assessment
N
o.
Ra
nk
Risk Descri
ption
Categ
ory
Root
Cause
Potenti
al
Respo
nses
Risk
Owne
r
Proba
bility
Imp
act
Stat
us
R
4
4
1 In
effectiv
e
budget
assump
tion
Due to
ineffect
ive
budget
estimati
on the
organiz
ation
will
Finan
cials
risk
Due to
inappro
priate
knowle
dge
about
the
needs
as well
The
project
manage
r must
analyze
the
require
ments
of the
Finan
cials
mana
ger
Mediu
m
High Will
be
mitig
ated
in 2
mont
hs.
14
PROJECT MANAGEMENT
face
number
of
financia
l
challen
ges.
as
require
ments
of the
project
project
properl
y.
R
1
9
2 Ineffect
ive
schedul
ing
The
workers
ace
difficult
y in
complet
ing the
project
due to
ineffect
ive
schedul
ing.
Sched
uling
risk
Improp
er
knowle
dge
about
the
phases
of
system
develop
ment
This
can be
resolve
d if the
project
manage
rs have
proper
knowle
dge
about
project
phases.
Proje
ct
mana
ger
Mediu
m
Med
ium
Will
be
mitig
ated
in 1
mont
h
R
8
3
Utilizat
ion of
poor
quality
Due to
the use
of poor
quality
of
Projec
t risk
In
order to
save
budget
of the
Proper
quality
of
materia
l must
Proje
ct
mana
ger
High High Will
be
mitig
ated
in 2
PROJECT MANAGEMENT
face
number
of
financia
l
challen
ges.
as
require
ments
of the
project
project
properl
y.
R
1
9
2 Ineffect
ive
schedul
ing
The
workers
ace
difficult
y in
complet
ing the
project
due to
ineffect
ive
schedul
ing.
Sched
uling
risk
Improp
er
knowle
dge
about
the
phases
of
system
develop
ment
This
can be
resolve
d if the
project
manage
rs have
proper
knowle
dge
about
project
phases.
Proje
ct
mana
ger
Mediu
m
Med
ium
Will
be
mitig
ated
in 1
mont
h
R
8
3
Utilizat
ion of
poor
quality
Due to
the use
of poor
quality
of
Projec
t risk
In
order to
save
budget
of the
Proper
quality
of
materia
l must
Proje
ct
mana
ger
High High Will
be
mitig
ated
in 2
15
PROJECT MANAGEMENT
of
materia
l
materia
ls the
project
manage
rs faces
number
of
technic
al
challen
ges
project be
utilized
in the
project
for
avoidin
g
technic
al issue
mont
hs
R
3
2
4 Inappro
priate
manage
ment
Due to
improp
er time
manage
ment
number
of
project
related
issues
occurs.
Projec
t risk
Due to
improp
er
knowle
dge
about
the
project.
The
project
manage
rs must
be
hired
after
testing
their
project
manage
ment
knowle
dge
Proje
ct
mana
ger
Mediu
m
Med
ium
Will
be
set
up in
2
mont
hs
PROJECT MANAGEMENT
of
materia
l
materia
ls the
project
manage
rs faces
number
of
technic
al
challen
ges
project be
utilized
in the
project
for
avoidin
g
technic
al issue
mont
hs
R
3
2
4 Inappro
priate
manage
ment
Due to
improp
er time
manage
ment
number
of
project
related
issues
occurs.
Projec
t risk
Due to
improp
er
knowle
dge
about
the
project.
The
project
manage
rs must
be
hired
after
testing
their
project
manage
ment
knowle
dge
Proje
ct
mana
ger
Mediu
m
Med
ium
Will
be
set
up in
2
mont
hs
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
16
PROJECT MANAGEMENT
R
2
8
5 Improp
er
installat
ion of
the
system
Inappro
priate
installat
ion of
the
system
arises
umber
of
technic
al
challen
ges
Projec
t risk
Due to
improp
er
knowle
dge of
the
system
develop
ed
about
system
installat
ion
System
develo
ped
must be
hired
with
appropr
iate
knowle
dge
Syste
m
Devel
oper
Mediu
m
High Will
be
mitig
ated
in 3
mont
hs.
6. Quality management plan
6.1 Philosophy for delivering a quality system to the client
For delivering effective as well as appropriate quality based services, it is identified
that that are there are number of elements that are veer much advantageous. The elements are
service culture, customer experience as well as employee engagement. It is found that
number f elements must be used in order to form appropriate service culture that mainly
include vision, mission, leadership as well as other organizational norms. The rostering
system which is proposed is quite effective I managing different volunteers of the show.
PROJECT MANAGEMENT
R
2
8
5 Improp
er
installat
ion of
the
system
Inappro
priate
installat
ion of
the
system
arises
umber
of
technic
al
challen
ges
Projec
t risk
Due to
improp
er
knowle
dge of
the
system
develop
ed
about
system
installat
ion
System
develo
ped
must be
hired
with
appropr
iate
knowle
dge
Syste
m
Devel
oper
Mediu
m
High Will
be
mitig
ated
in 3
mont
hs.
6. Quality management plan
6.1 Philosophy for delivering a quality system to the client
For delivering effective as well as appropriate quality based services, it is identified
that that are there are number of elements that are veer much advantageous. The elements are
service culture, customer experience as well as employee engagement. It is found that
number f elements must be used in order to form appropriate service culture that mainly
include vision, mission, leadership as well as other organizational norms. The rostering
system which is proposed is quite effective I managing different volunteers of the show.
17
PROJECT MANAGEMENT
6.2 Quality issues
Project Name:RALS Rostering System Project manager Name:
(<<Name of the Student>>)
Sl.No Quality related issues that
are possible
Mitigation
time
Method for
mitigation
Owner Status
1 The utilized materials are
of poor quality and as a
result numbers of technical
challenges are arising.
1month Inspection Project
manager
Open
2 The staffs of the show are
not trained properly and as a
result there are incapable of
working properly with the
new system.
1 months Inspection Project
manager
Open
3 The project report which are
created are considered as
poor quality as the report do
not elaborate much
information..
2 months Inspection project
manger
Open
It is identified that both verification as well as validation procedure are used for
reflecting the proposed system is beneficial.
Verification testing: The methodology of testing elaborates that each and every
demand of the customers are properly met due to development of the system.
PROJECT MANAGEMENT
6.2 Quality issues
Project Name:RALS Rostering System Project manager Name:
(<<Name of the Student>>)
Sl.No Quality related issues that
are possible
Mitigation
time
Method for
mitigation
Owner Status
1 The utilized materials are
of poor quality and as a
result numbers of technical
challenges are arising.
1month Inspection Project
manager
Open
2 The staffs of the show are
not trained properly and as a
result there are incapable of
working properly with the
new system.
1 months Inspection Project
manager
Open
3 The project report which are
created are considered as
poor quality as the report do
not elaborate much
information..
2 months Inspection project
manger
Open
It is identified that both verification as well as validation procedure are used for
reflecting the proposed system is beneficial.
Verification testing: The methodology of testing elaborates that each and every
demand of the customers are properly met due to development of the system.
18
PROJECT MANAGEMENT
Validation testing: Validation testing methodology is helpful in elaborating the
system quality which is proposed by Globex.
PROJECT MANAGEMENT
Validation testing: Validation testing methodology is helpful in elaborating the
system quality which is proposed by Globex.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
19
PROJECT MANAGEMENT
Bibliography
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
Cicmil, S., Cooke-Davies, T., Crawford, L., & Richardson, K. (2017, April). Exploring the
complexity of projects: Implications of complexity theory for project management
practice. Project Management Institute.
Hegazy, T. (2013). Computer-Based Construction Project Management: Pearson New
International Edition. Pearson Higher Ed.
Heldman, K. (2015). PMP project management professional exam deluxe study guide:
updated for the 2015 Exam. John Wiley & Sons.
Hwang, B. G., & Ng, W. J. (2013). Project management knowledge and skills for green
construction: Overcoming challenges. International Journal of Project
Management, 31(2), 272-284.
Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Larson, E. W., & Gray, C. (2013). Project Management: The Managerial Process with MS
Project. McGraw-Hill.
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.
PROJECT MANAGEMENT
Bibliography
Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.
Cicmil, S., Cooke-Davies, T., Crawford, L., & Richardson, K. (2017, April). Exploring the
complexity of projects: Implications of complexity theory for project management
practice. Project Management Institute.
Hegazy, T. (2013). Computer-Based Construction Project Management: Pearson New
International Edition. Pearson Higher Ed.
Heldman, K. (2015). PMP project management professional exam deluxe study guide:
updated for the 2015 Exam. John Wiley & Sons.
Hwang, B. G., & Ng, W. J. (2013). Project management knowledge and skills for green
construction: Overcoming challenges. International Journal of Project
Management, 31(2), 272-284.
Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
Larson, E. W., & Gray, C. (2013). Project Management: The Managerial Process with MS
Project. McGraw-Hill.
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.
20
PROJECT MANAGEMENT
Pemsel, S., & Wiewiora, A. (2013). Project management office a knowledge broker in
project-based organisations. International Journal of Project Management, 31(1), 31-
42.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
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.
Turner, R. (2016). Gower handbook of project management. Routledge.
Turner, R. (2016). Gower handbook of project management. Routledge.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Walker, A. (2015). Project management in construction. John Wiley & Sons.
PROJECT MANAGEMENT
Pemsel, S., & Wiewiora, A. (2013). Project management office a knowledge broker in
project-based organisations. International Journal of Project Management, 31(1), 31-
42.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
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.
Turner, R. (2016). Gower handbook of project management. Routledge.
Turner, R. (2016). Gower handbook of project management. Routledge.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Walker, A. (2015). Project management in construction. John Wiley & Sons.
1 out of 21
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.