Project Management and Risk Analysis

This assignment delves into the complexities of project management by examining the distinctions between projects and project management. It analyzes various aspects like stakeholder involvement, objectives, influences, and risk identification. Three articles provide insights into project management concepts, emphasizing the crucial role of risk assessment in ensuring project success. An appendix includes a closure checklist outlining tasks involved in a project's completion and a project evaluation framework highlighting the impact of the developed system on multiple areas such as customer satisfaction, strategy implementation, social communication, operational efficiency, and financial returns.

Running head: PROJECT MANAGEMENT
Case Study- RAILS Rostering System
Name of the Student
Name of the University
Authors Note

1
PROJECT MANAGEMENT
Table of Contents
1.Project overview...........................................................................................................................3
2.0 Measurable organizational value (MOV)..................................................................................3
2.1 Desired area of Impact...........................................................................................................3
2.2 Value of the project plan........................................................................................................4
2.3 Stakeholder involved in the project plan...............................................................................4
2.4 Appropriate timeframe and metric.........................................................................................5
3. Scope management plan..............................................................................................................6
3.1 Detailed scope of the project.................................................................................................6
3.2 List of resources.....................................................................................................................7
4. Project schedule and WBS...........................................................................................................9
4.1 Project schedule.....................................................................................................................9
4.2 WBS.....................................................................................................................................14
4.3 Milestone of the Project plan...............................................................................................14
5. Project risk analysis and plan....................................................................................................15
5.1 Project assumptions.............................................................................................................15
5.2 Risk Assessment..................................................................................................................16
6. Quality management plan..........................................................................................................20
6.1 Philosophy for delivering a quality system to the client......................................................20
6.2 Quality issues.......................................................................................................................20
Bibliography..................................................................................................................................23
Appendices:...................................................................................................................................25
Appendix 1: Annotated Bibliography........................................................................................25
Appendix 2: Closure checklist...................................................................................................26
Appendix 3: Project evaluation.................................................................................................28

2
PROJECT MANAGEMENT
1.Project overview
The paper mainly reflects on the show of Riverina Agricultural ad lifestyle which is
mainly arranged for displaying various types of agricultural events, lifestyle products as well as
local business. It is identified that with time, the show became famous and thus the organization
requires proper number of volunteers for managing the show. It is found that the manual
techniques that are utilized by the organization for managing the details of large number of
volunteers is not appropriate therefore the business Globex which is aligned with the show wants
to develop a rostering system.
In this paper, proper information about project schedule, budget, management plan as
well as resources are provided. It is identified that the paper also elaborates the challenges as
well as risks that the project faces while developing the rostering system of rails. Proper numbers
of recommendations are also provided for resolving the issues related with the project.
2.0 Measurable organizational value (MOV)
2.1 Desired area of Impact
The various desired impact areas includes:
Customer: It is identified that the developed system is quite helpful in mitigating
various types of queries which are raised by the people.
Strategy: It is found that the system is quite beneficial in tracking different kinds of
volunteer’s details for tracking them.

3
PROJECT MANAGEMENT
Social: The developed system is found to be advantageous for making the
communication with the clients much more effective.
Operational: The utilization of rostering system helps in storing significant details of
volunteers within the system which helps in making the organizational operation easier.
Financial:It is identified that the system of rostering which is developed by Globex
would be helpful in providing huge amount of return on the money that is invested by the
business.
2.2 Value of the project plan
The value of project plan is elaborated below:
Better: It is found that the development of the new system assist in providing proper
facility to the clients as well as to the volunteers. Moreover, the system is also helpful in
providing proper security to the information that is stored within the system.
Cheaper: The operation cost of the business generally reduces due to the use of the
newly developed rostering system.
Faster: The response time for both the customers and volunteers decreases due to the use
of the rostering system.
2.3 Stakeholder involved in the project plan
The stakeholders that are involved within the project include:

4
PROJECT MANAGEMENT
Keep satisfied
CEO
Manage closely
Project team
Monitor
Volunteers
Keep informed
Staffs
Interest
Power
2.4 Appropriate timeframe and metric
Rank Impact Metrics Timeframe
1 Operational The business operation
become less time
consuming due to the
use of the system
2 months
2 Strategy The important details of
the volunteers are
generally tracked with
the of the newly
developed system
1 month
3 Customer The response time
minimizes due to the
2 months

5
PROJECT MANAGEMENT
utilization of the
rostering system
4 Social The interaction between
volunteers and
customers improves
with the utilization of
rostering system
3 months
5. Financial The cost of operation
gets reduced by 20% by
the system utilization.
5 months
3. Scope management plan
3.1 Detailed scope of the project
The detailed scope of the project is elaborated below:
Requirements: It is identified that RAILS rostering system is generally required for
entering significant details of the volunteers who are mainly involved with the show of RAIL. It
is identified that the proposed system is quite capable in tracking the volunteers with the help of
the details provided.
In scope and out scope:
In scope:The in scope of the project includes:
 Development of RAIL rostering system for the business of Globex

6
PROJECT MANAGEMENT
 Helps in incorporating details of the volunteers including qualification details,
personal details as well as additional other details
 Assists in documenting both functional as well as non-functional project
requirements
 To complete the project within time period of 244 days
Out scope: The out scope of the project includes:
 System maintenance related with service quality as well as data security is not
provided
 Training is not provided to the workers of Globex
Deliverables: The project deliverables include:
 For testing the system, proper test plan of the report must be made
 Documenting the entire development phase
 Documenting the budget plan
 Creating the document of training
 Scope verification procedure
 Providing proper report on system requirements
Scope verification procedure: The acceptance criteria of the system are quite helpful in
meeting various requirements as well as needs of the client. It also assists in minimizing the
response time for giving proper solution to various queries.
3.2 List of resources
The various types of resources include:

7
PROJECT MANAGEMENT
Material resources: The various types of technical requirements for completing the
project successfully including operating system, secondary storage, display adapter, CPU and
more.
Human resources: The persons who are generally needed for completing the project
properly within time include project manager, system developer, system analyst, business
analyst, system ester, project sponsor as well as investment manager.
Resource
Name
Type
Material
Label
Initials
Grou
p
Max.
Units
Std.
Rate
Ovt.
Rate
Cost/Use
Accrue
At
Base
Calendar
Developer Work D 100% $80.00/hr $0.00/hr $0.00 Prorated Standard
System
analyst
Work S 100% $90.00/hr $0.00/hr $0.00 Prorated Standard
Accountant Work A 100% $85.00/hr $0.00/hr $0.00 Prorated Standard
Project
manager
Work P 100% $90.00/hr $0.00/hr $0.00 Prorated Standard
Tester Work T 100% $70.00/hr $0.00/hr $0.00 Prorated Standard
Executive
sponsor
Work E 100% $75.00/hr $0.00/hr $0.00 Prorated Standard
Requirement
analyst
Work R 100% $65.00/hr $0.00/hr $0.00 Prorated Standard
Risk
manager
Work R 100% $70.00/hr $0.00/hr $0.00 Prorated Standard

8
PROJECT MANAGEMENT
4. Project schedule and WBS
4.1 Project schedule
Task Name Duration Start Finish Resource Names
RAILS Rostering System 244 days Mon 9/25/17 Thu 8/30/18
Specification determination 23 days Mon 9/25/17 Wed 10/25/17
Undertaking feasibility study
for the different manual system
6 days Mon 9/25/17 Mon 10/2/17
Project manager,
Requirement
analyst
Business needs identification 6 days Tue 10/3/17 Tue 10/10/17
Requirement
analyst
Creation of SRS document 7 days
Wed
10/11/17
Thu 10/19/17
Project manager,
Requirement
analyst
Meeting arrangement 4 days Fri 10/20/17 Wed 10/25/17 Project manager
Milestone: completion of
specification determination
0 days
Wed
10/25/17
Wed 10/25/17
Development team selection 38 days
Thu
10/26/17
Mon 12/18/17
Development of vendor
selection
11 days Thu 10/26/17 Thu 11/9/17
Accountant,
Project manager
Checking development history
of the vendors
12 days Fri 11/10/17 Mon 11/27/17 Executive
sponsor, Project

9
PROJECT MANAGEMENT
manager
Development task scheduling 7 days Tue 11/28/17 Wed 12/6/17
Developer, Project
manager
Budget planning for
development
8 days Thu 12/7/17 Mon 12/18/17
Accountant,
Executive
sponsor, Project
manager
Milestone: completion of
team selection
0 days
Mon
12/18/17
Mon 12/18/17
Designing phase 69 days Tue 12/19/17 Fri 3/23/18
Module improvement for
volunteer management
21 days Tue 12/19/17 Tue 1/16/18
Developer, Project
manager
First prototype development 17 days Wed 1/17/18 Thu 2/8/18 Developer
Improvement within new
system installation
15 days Fri 2/9/18 Thu 3/1/18
Developer, Project
manager
Determining the needs of the
system
16 days Fri 3/2/18 Fri 3/23/18
Project manager,
System analyst
Milestone: Completion of
design phase
0 days Fri 3/23/18 Fri 3/23/18
System implementation system 33 days Mon 3/26/18 Wed 5/9/18
Different business objectives
development
13 days Mon 3/26/18 Wed 4/11/18 Developer,
Requirement

10
PROJECT MANAGEMENT
analyst
Amendments within the part of
the system that is implemented
12 days Thu 4/12/18 Fri 4/27/18
Developer, Project
manager
Using compatible software and
hardware
8 days Mon 4/30/18 Wed 5/9/18
Accountant,
Project manager,
System analyst
Milestone: Completion of
system implementation system
0 days Wed 5/9/18 Wed 5/9/18
Testing phase 26 days Thu 5/10/18 Thu 6/14/18
Identifying test cases as well as
test plan
7 days Thu 5/10/18 Fri 5/18/18 Tester
Testing the developed system 8 days Mon 5/21/18 Wed 5/30/18
Project manager,
Tester
Information system analysis
from the data
9 days Thu 5/31/18 Tue 6/12/18
Executive
sponsor, Project
manager
Results documentation 2 days Wed 6/13/18 Thu 6/14/18 Project manager
Milestone: acceptance of the
test results by client
0 days Thu 6/14/18 Thu 6/14/18
Risk management phase 30 days Fri 6/15/18 Thu 7/26/18
Assessment as well as risk
identification
11 days Fri 6/15/18 Fri 6/29/18
Project manager,
Risk manager
Presenting risks impact 7 days Mon 7/2/18 Tue 7/10/18 Risk manager

11
PROJECT MANAGEMENT
Risks mitigation 8 days Wed 7/11/18 Fri 7/20/18
Project manager,
System analyst
Impact of the risk registering 4 days Mon 7/23/18 Thu 7/26/18
Project manager,
Risk manager
Milestone: Acceptance of the
risk document by the client
0 days Thu 7/26/18 Thu 7/26/18
Closure of the project 25 days Fri 7/27/18 Thu 8/30/18
Evaluating rostering system
functions
13 days Fri 7/27/18 Tue 8/14/18
Executive
sponsor, Project
manager
Final developed product roll
out
12 days Wed 8/15/18 Thu 8/30/18 Project manager
Milestone: Completion of
closure phase of the project
0 days Thu 8/30/18 Thu 8/30/18

12
PROJECT MANAGEMENT
Figure 1: Gantt chart
(Source: Created by author)

13
PROJECT MANAGEMENT
4.2 WBS
RAILS Rostering System
Specification
determination
Undertaking
feasiability study for
the different manual
system
Business needs
identification
Creation of SRS
document
Meeting
arrangement
Milestone:
completion of
specification
determination
Development team
selection
Development of
vendor selection
Checking
development history
of the vendors
Development task
schedulling
Budget planning for
development
Milestone:
completion of team
selection
Designining phase
Module
improvement for
volunteer
management
First prototype
development
Improvement within
new system
installation
Determining thw
needs of the system
Milestone:
Completion of
design phase
System implementation
system
Different business
objectives
development
Ammendments within
the part of the system
that is implemented
Using compatible
software and
hardware
Milestone:
Completion of
system
implemenatation
system
Testing phase
Identifying test cases
as well as test plan
Testing the
developed system
Information system
analysis from the
data
Results
documentation
Milestone:
acceptance of the
test results by client
Risk management phase
Assesment as well as
risk identification
Presennting risks
imapct
Risks mitigation
Impcat of the risk
registering
Milestone:
Accepetance of the
risk document by the
client
Closure of the project
Evaluating rostering
system functions
Final developed
product roll out
Milestone: Completion
of closure phase of
the project
Figure 2: Work Breakdown Structure
(Source: Created by author)
4.3 Milestone of the Project plan
WBS Task Name Expected Date
0 RALS Rostering System Fri 9/23/16
1 Completion of specification determination Wed 10/25/17
2 Completion of team selection Mon 12/18/17
3 Completion of design phase Fri 3/23/18
4 Completion of system implementation system Wed 5/9/18

14
PROJECT MANAGEMENT
5 Acceptance of the risk document by the client Thu 7/26/18
6 Completion of closure phase of the project Thu 8/30/18
5. Project risk analysis and plan
5.1 Project assumptions
The various types of assumptions that are generally made are as follows:
Time: The project manager estimated the entire time that is needed for completing all
the activities of the project for developing the rostering system of RAILS. The estimated time
that is needed for completing the project is around 244 days.
Budget: The project manager estimates the budget that is required for executing various
project activities. It is found that the estimated budget is around $400,000. It is identified that
that $298.040 will be required for completing the activities and $200, 00 will be required for
other material as well as additional resources.
Resources: The project manager assumes the various project resources, which will be
generally needed for developing the RAILS restoring system. It is found that an assumption of
the project resources helps in giving proper overview about the needs of the budget.

15
PROJECT MANAGEMENT
5.2 Risk Assessment
No
.
Ran
k
Risk Descripti
on
Catego
ry
Root
Cause
Triggers Potential
Responses
Risk
Owner
Probabili
ty
Impac
t
Stat
us
R4
4
1 Failure of
the
system
If the
system is
not
installed
properly
within the
business
then it
will create
number of
risks as
well as
challenges
Technic
al risk
Due to
lack of
proper
knowledg
e of the
system
developer,
the
installatio
n is not
done
properly
The
system is
not
installed by
taking
proper time
that is
needed
The
system
should be
installed
properly.
Project
manage
r
Medium High Set
up in
1
week
R1
9
2 Improper
estimation
of budget
The
assumed
budget by
the
project
manager
is not
accurate
Financi
al risk
They
assume
that the
budget is
not
accurate
as the
project
managers
Budget
related
issues
occurs due
to improper
market
analysis
Proper
budget
estimation
must be
done by
analyzing
the market
effectively.
Financ
ial
manage
r
Medium High Set
up in
3
week
s

16
PROJECT MANAGEMENT
are not
much
experienc
ed and
they do
not
analyze
the
market
effectivel
y.
R8 3 Improper
schedulin
g
The
project
manager
does not
understan
d the
project
objectives
and goals
properly
and thus
the
schedule
created by
Project
risk
The
schedulin
g related
risk
mainly
occurs
due to
presence
of
improper
amount of
informati
on about
the
Improper
understandi
ng of
project
creates
scheduling
risk
The project
manager
must
analyze as
well as
determine
the
requiremen
ts of the
project by
understandi
ng it
Project
manage
r
Medium High Set
up in
2
week

17
PROJECT MANAGEMENT
them is
not
accurate.
client’s
requireme
nt.
R3
2
4 Improper
managem
ent
Improper
managem
ent of the
project
activities
creates
number of
challenges
Project
risk
It mainly
occurs
due to
improper
experienc
e of
managers.
Improper
experience
of the
project
managers
leads to
ineffective
manageme
nt of
project
The
project
managers
must
manage the
project by
following
proper
strategist as
well as
methods
Project
manage
rs
Medium High Set
up in
1
week
R2
8
5 Resources Improper
use of
project
resources
Resour
ce risk
Improper
use of
resources
due to
proper
experienc
e
Proper
techniques
for
resource
manageme
nt are not
used
The
organizatio
n must
proper
experience
project
managers
Project
manage
r
Medium Mediu
m
Set
up in
1
week

18
PROJECT MANAGEMENT
Probability of
occurrence
Impact of occurrence
Very low Low Medium High Very high
Very low
Low
Medium Resource risk Technical risk
High Schedule risk Technical risk
Very high
Figure 3: Qualitative Risk Analysis
(Source: Created by author)

19
PROJECT MANAGEMENT
6. Quality management plan
6.1 Philosophy for delivering a quality system to the client
It is identified that there are number of key elements which are considered to be helpful in
delivering different types of quality based services to the customers including employee
engagement, service culture, quality of service as well as customer experience. It is found that the
various types of elements are mainly used for forming the service culture and the elements are
mission, leadership, vision as well as different types of organizational norms. The proposed system
is found to be quite effective engaging people of the organization. It is found that the quality of
service is depends on the strategic plan which is utilized by the organization for system installation
and for fulfilling different goals as well as objectives of the organization.
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 different types of
documents and reports that is
prepared after the completion of
each phase is not of appropriate
quality and does not provide
much information. Thus, the
staffs face difficulty in moving
2 moths Inspection Project
manager
Open

20
PROJECT MANAGEMENT
with the next phase of the project
due to presence of proper
information.
2 The software as well as
hardware materials that are
utilized for development of the
project is found to be of low
quality thus number of technical
challenge occur.
3 months Inspection Project
manager
Open
3 The staffs of the organization
are not much skilled and as a
result the work that are
completed by them is not of
appropriate quality and as a
result the project managers faces
little both problem while
installation of the system.
2 months Inspection project
manger
Open
It is analyzed that verification as well as validation testing are utilized in order to make sure
that the developed restoring system will be helpful in managing the volunteers.
Validation testing: Validation testing is mainly done for elaborating the quality of the
proposed system within the project development phase. This testing method is mainly utilized for
meeting various needs of the clients as well as businesses.

21
PROJECT MANAGEMENT
Verification testing: This testing method helps in elaborating the proposed system for
meeting various conditions as well as regulations of the system as well as organizations. It is
identified if all the criteria are fulfilled then the system will be installed by the business Globex.

22
PROJECT MANAGEMENT
Bibliography
Amrollahi, A., Ghapanchi, A. H., &Talaei-Khoei, A. (2014). Three decades of research on strategic
information system plan development.Communications of the Association for Information
Systems, 34(1), 84.
Braglia, M., &Frosolini, M. (2014).An integrated approach to implement project management
information systems within the extended enterprise.International Journal of Project
Management, 32(1), 18-29.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Galliers, R. D., &Leidner, D. E. (2014). Strategic information management: challenges and
strategies in managing information systems. Routledge.
Garton, C., & McCulloch, E. (2012). Fundamentals of Technology Project Management. MC
Press, LLC.
Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational excellence.pearson.
Hubicki, M. (2014). Risk Management Plan.
Kami, N. (2015). U.S. Patent No. 9,116,916. Washington, DC: U.S. Patent and Trademark Office.
Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-proofing
your project. AMACOM Div American Mgmt Assn.

23
PROJECT MANAGEMENT
Nanda, V. (2016). Quality management system handbook for product development companies.CRC
Press.
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.
Schwalbe, K. (2015). Information technology project management.Cengage Learning.
Stark, J. (2015). Product lifecycle management.In Product Lifecycle Management (pp. 1-
29).Springer International Publishing.
Tornabene, C., Hussain, M. M., Crowe, T., Cohen, N., & Panzer, J. (2012).U.S. Patent No.
8,103,729. Washington, DC: U.S. Patent and Trademark Office.
Verburg, R. M., Bosch-Sijtsema, P., &Vartiainen, M. (2013).Getting it done: Critical success
factors for project managers in virtual work settings.International Journal of Project
Management, 31(1), 68-79.
Verzuh, E. (2015). The fast forward MBA in project management.John Wiley & Sons.

24
PROJECT MANAGEMENT
Appendices:
Appendix 1: Annotated Bibliography
Article 1: Otieno, F. A. O. (2000, November). The roles of monitoring and evaluation in
projects. In 2 nd International Conference on Construction in Developing Countries: Challenges
facing the construction industry in developing countries (pp. 15-17).
The paper mainly focuses on the “roles of monitoring and evaluation in projects”.
According to Otieno (2000),there are number of project which are associated with third world
countries that fails due to number of reasons that include lack of understanding of the need for
evaluation as well as monitoring. The author highlights the significance of project monitoring and
evaluation for ensuring proper as well as successful completion of the project. The paper also
outlines some of the common constraints that help in impeding ways that is helpful in overcoming
the problem. In addition to this, it is found that monitoring is one of the tools that is considered for
continuous assessment of project or program in context to the implementation schedule. On the
other hand, evaluation is a procedure that helps in determining the effectiveness, relevancy,
sustainability as well as impact of activities in the light of project performance.
Article 2: Munns, A. K., & Bjeirmi, B. F. (1996). The role of project management in achieving
project success. International journal of project management, 14(2), 81-87.
The paper mainly reflects on the role of project management in achieving success.
According to Munns and Bjeirmi (1996), the role of various types of project management technique
for implementing projects successfully is widely established in various areas which include
planning as well as control of cost, time as well as quality. It is identified that that in spite of this,

25
PROJECT MANAGEMENT
the difference that exist between project as well as project management is less than precise. The
author mainly aims to determine the overlap that generally exists between the definition of project
as well as project management for discussing how the confusion between both the terms affects the
relationship. The author also identifies the people who mainly involves with the project as well as
project management together with their expectations, objectives as well as influences. In addition to
this, it also helps in demonstrating better appreciation of the distinction between project as well as
project management for bringing higher possibility of project success.
Article 3: Anca, U., Cezar, B., & Adrian, U. (2015, November). Risk Identification in Project
Management. In International Conference on Economic Sciences and Business
Administration (Vol. 2, No. 1, pp. 259-266). Spiru Haret University.
The paper mainly focuses on risk identification in project manager. It is identified that
project risk is defined as one of the uncertain event that either have appositive or negative impact
on one or more objectives of the project (Anca, Cezar & Adrian, 2015). Various conditions of risks
generally include different aspects of the project or organization that helps in contributing within
the project, which is considered as a practice of immature project management, competing projects,
lack of integrated management systems as well as dependency on various external participants. It is
identified that risk identification is one of the basic step in managing various project risks.
Appendix 2: Closure checklist
Task Name Stakeholder
Signature
Undertaking feasibility study for the
different manual system
Project manager,
Requirement analyst