ICT Project Management: RALS Ticketing System Development Project

This project report details the development of a RALS ticketing system, covering various aspects of ICT project management. The report begins with an analysis of the Measurable Organisational Value (MOV) and defines the project's scope, outlining requirements, deliverables, and acceptance cr...Read More

ICT Project Management
RALS Roistering Project

Table of Contents
Part One: MOV - Measurable Organisational Value.................................................................3
Part Two: Define Scope and produce a Scope Management Plan.............................................4
Part Three: Project Plan.............................................................................................................7
Part Four: Risk Analysis and Management Plan for RALS.....................................................13
Part 5: Quality Management Plan............................................................................................18
Part 6: Project Closure.............................................................................................................18
a. Annotated Bibliography...................................................................................................18
Closure checklist......................................................................................................................19
Bibliography.............................................................................................................................21

Part One: MOV - Measurable Organisational Value
The customer strategies operational social and financial are the desired areas of the impact for
RALS ticketing system development project. All these factors are discussed below:-
Area of
impact
Description Ranking
Financial In this it mainly discussed about money related frame works that
mainly clarified as the operations of procedures to have the
improvement by co-ordinating both the advancement of operations
and the suggestion of consummation.
1st
Customer Customers are the part of the frame work range that mainly raise
different type of questions created by general population in addition
to both the frame work and task organized by RALS.
2nd
Operational The operational technique discussed about the security shaping of
different functions as well as the reconciliation of procedure for
doing the adjustment of the concerned project.
3rd
Strategy Strategy mainly characterized to effect the operation of the RALS by
creating various enhanced and successful operations.
4th
Social The operational technique that mainly suggested building up the
security of different operations and the combination of its
procedures.
5th
 Cheaper: - RALS task mainly helps to deal with data of solitary data base and also
helps to diminish the cost of data frame work administrations.

 Do more:-The frame work uses in RALS incorporates data and also helps to create
different intelligent technique of association.
Rank Impact Metrics Time frame
1. Financial Revenue, money, profit era 6 months
2. Customer Numbers of client returns to the
association for their better administration
procedures.
2 months
3. Operational Minimum consumption of time required to
finish all hierarchical operations.
2 months
4. Strategy All volunteers get followed due to the
proper utilization of the frame work
formed by RALS.
1 month
5. Social Volunteers have the capacity to get
connected with all clients
3 months
Part Two: Define Scope and produce a Scope Management Plan
Scope Definition: - The RALS ticketing system advancement helps to build up all operational
changes of Globex for volunteers and clients data with the help of the created frame work.
Requirement: - All project requirements include required materials and proper project team
for doing the development of all operational procedures.
Resource Name Type
Budgeter Work

Computer Devices Material
Documenter Work
IT Engineer Work
Network Components Material
Planner Work
Project Manager Work
Storage Material
System Analyst Work
Tester Work
Wireless routers Material
In scope and out scope of the project :- The in scope items of RALS venture of prepared for
doing all operations of undertaking and the improvements of RALS ticketing system,
increase of effectiveness of the data administration about volunteers , key advancement and
helping for operations .
The out scope items of the RALS projects include up keeping exercises preparation of
labours, accumulation of materials in Globex.
Deliverables of the project: - Some of the deliverables of this RALS roistering project are
listed below:-
1. Resource allocation plan and project plan
2. Scope verification plan.
3. Project documentation including charter documentation and initiation plan.
4. Implementation plan system design.

5. Accumulation of test results
Acceptance criteria:-
Check list items Checked
Advancement of project plan 
Improvised resource allocation plan 
Closure of Project documentation including
charter documentation and initiation plan.

Feasible system design 
Well organized system design 
Expected Test results 
Resources List:
Resource Name Type Initials Std. Rate
Budgeter Work B $60.00/hr
Computer Devices Material C $1,740.00
Documenter Work D $60.00/hr
IT Engineer Work I $95.00/hr
Network Components Material N $970.00
Planner Work P $60.00/hr

Project Manager Work PM $100.00/hr
Storage Material S $2,320.00
System Analyst Work SA $90.00/hr
Tester Work T $85.00/hr
Wireless routers Material W $870.00
Part Three: Project Plan
WBS Task Name Duration Start Finish Predecessors Resource Names Cost
0
Developing
Ticketing
System for
RALS
140
days
Mon
10/2/17
Fri
4/13/18 $99,980.00
1 Initial Phase 17 days Mon
10/2/17
Tue
10/24/17 $11,360.00
1.1
Analysis of
the project
feasibility
3 days Mon
10/2/17
Wed
10/4/17 Project Manager $2,400.00
1.2 Requirement
Analysis 5 days Thu
10/5/17
Wed
10/11/17 2 Project Manager $4,000.00
1.3
Making
Initiation
documents
4 days Thu
10/12/17
Tue
10/17/17 3 Documenter $1,920.00
1.4 Charter
documentation 3 days Wed
10/18/17
Fri
10/20/17 4 Documenter $1,440.00
1.5
Project
Meetings are
held
1 day Mon
10/23/17
Mon
10/23/17 5 Project Manager $800.00

1.6 Signing off
the documents 1 day Tue
10/24/17
Tue
10/24/17 6 Project Manager $800.00
M1 Initial Phase
is completed 0 days Tue
10/24/17
Tue
10/24/17 7 $0.00
2 Resource
Accumulation 19 days Wed
10/25/17
Mon
11/20/17 $9,120.00
2.1
Client's
requirement is
analyzed
5 days Wed
10/25/17
Tue
10/31/17 8 Budgeter $2,400.00
2.2 Project team
is selected 7 days Wed
11/1/17
Thu
11/9/17 10 Planner $3,360.00
2.3
Budget for
the project is
developed
4 days Fri
11/10/17
Wed
11/15/17 11 Budgeter $1,920.00
2.4
Outsourcing
of the project
materials
3 days Thu
11/16/17
Mon
11/20/17 12 Budgeter $1,440.00
M2
Accumulatio
n of the
resources
0 days Mon
11/20/17
Mon
11/20/17 13 $0.00
3 Plan Phase 10 days Tue
11/21/17
Mon
12/4/17 $5,760.00
3.1
Plan
methodology is
selected
2 days Tue
11/21/17
Wed
11/22/17 14 Planner $960.00
3.2
Outline for
the plan is
developed
5 days Thu
11/23/17
Wed
11/29/17 16 Planner $2,400.00
3.3 Review of
the plan 3 days Thu
11/30/17
Mon
12/4/17 17 Project Manager $2,400.00
M3 Plan is
completed 0 days Mon
12/4/17
Mon
12/4/17 18 $0.00
4 Design Phase 16 days Tue
12/5/17
Tue
12/26/17 $11,520.00
4.1
Design
Platform is
selected
1 day Tue
12/5/17
Tue
12/5/17 19 System Analyst $720.00

4.2
Outline for
the design is
developed
3 days Wed
12/6/17
Fri
12/8/17 21 System Analyst $2,160.00
4.3 Prototype is
developed 7 days Mon
12/11/17
Tue
12/19/17 22 System Analyst $5,040.00
4.4 Review of
the prototype 2 days Wed
12/20/17
Thu
12/21/17 23 System Analyst $1,440.00
4.5
Simulation of
the completed
design
3 days Fri
12/22/17
Tue
12/26/17 24 System Analyst $2,160.00
M4 Complete
design is formed 0 days Tue
12/26/17
Tue
12/26/17 25 $0.00
5 Implementatio
n Phase 52 days Wed
12/27/17
Thu
3/8/18 $45,420.00
5.1 Storage is
developed 10 days Wed
12/27/17
Tue
1/9/18 26 IT Engineer,
Storage[1] $9,920.00
5.2 Transfer of
the data 5 days Wed
1/10/18
Tue
1/16/18 28 IT Engineer $3,800.00
5.3
Design
analysis for the
ticket system
4 days Wed
1/17/18
Mon
1/22/18 29 IT Engineer $3,040.00
5.4 Development
of User interface 6 days Tue
1/23/18
Tue
1/30/18 30 IT Engineer $4,560.00
5.5
Coding and
programming is
done
12 days Wed
1/31/18
Thu
2/15/18 31 IT Engineer $9,120.00
5.6
Integration of
ticket system
with storage
8 days Fri
2/16/18
Tue
2/27/18 32 IT Engineer $6,080.00
5.7
Installing
hardware
components
7 days Wed
2/28/18
Thu
3/8/18 33
IT Engineer,
Computer
Devices[1],
Network
Components[1],
Wireless
routers[1]
$8,900.00

M5
New System
installed in
Globex
0 days Thu
3/8/18
Thu
3/8/18 34 $0.00
6 Testing Phase 20 days Fri
3/9/18
Thu
4/5/18 $13,600.00
6.1 Black box
testing 5 days Fri
3/9/18
Thu
3/15/18 35 Tester $3,400.00
6.2 UX testing 5 days Fri
3/16/18
Thu
3/22/18 37 Tester $3,400.00
6.3 Operations
and tested 5 days Fri
3/23/18
Thu
3/29/18 38 Tester $3,400.00
6.4 white box
testing 5 days Fri
3/30/18
Thu
4/5/18 39 Tester $3,400.00
M6
Results of
tests are
compiled
0 days Thu
4/5/18
Thu
4/5/18 40 $0.00
7 Documentatio
n Phase 6 days Fri
4/6/18
Fri
4/13/18 $3,200.00
7.1 Making final
documents 3 days Fri
4/6/18
Tue
4/10/18 41 Documenter $1,440.00
7.2 Review of
documents 2 days Wed
4/11/18
Thu
4/12/18 43 Documenter $960.00
7.3 Signing off
the documents 1 day Fri
4/13/18
Fri
4/13/18 44 Project Manager $800.00
M7 Project is
closed 0 days Fri
4/13/18
Fri
4/13/18 45 $0.00
Below is the Gantt chart of this project shown:

ID Task
Mode
WBS Task Name Duration Start Finish Predecess ors Resource Names Cost
0 0 Developing Ticketing
System for RALS
140 days Mon 10/2/17 Fri 4/13/18 $99,980.00
1 1 Initial Phase 17 days Mon 10/2/17 Tue 10/24/17 $11,360.00
2 1.1 Analysis of the project
feasibility
3 days Mon 10/2/17 Wed 10/4/17 Project
Manager
$2,400.00
3 1.2 Requirement Analysis 5 days Thu 10/5/17 Wed 10/11/17 2 Project Manager $4,000.00
4 1.3 Making Initiation documents4 days Thu 10/12/17 Tue 10/17/17 3 Documenter $1,920.00
5 1.4 Charter documentation 3 days Wed 10/18/17 Fri 10/20/17 4 Documenter $1,440.00
6 1.5 Project Meetings are held1 day Mon 10/23/17 Mon 10/23/17 5 Project Manager $800.00
7 1.6 Signing off the documents1 day Tue 10/24/17 Tue 10/24/17 6 Project Manager $800.00
8 M1 Initial Phase is completed0 days Tue 10/24/17 Tue 10/24/17 7 $0.00
9 2 Resource Accumulation 19 days Wed 10/25/17 Mon 11/20/17 $9,120.00
10 2.1 Client's requirement is
analyzed
5 days Wed 10/25/17 Tue 10/31/17 8 Budgeter $2,400.00
11 2.2 Project team is selected 7 days Wed 11/1/17 Thu 11/9/17 10 Planner $3,360.00
12 2.3 Budget for the project
is developed
4 days Fri 11/10/17 Wed 11/15/17 11 Budgeter $1,920.00
13 2.4 Outsourcing of the
project materials
3 days Thu 11/16/17 Mon 11/20/17 12 Budgeter $1,440.00
14 M2 Accumulation of the resources0 days Mon 11/20/17 Mon 11/20/17 13 $0.00
15 3 Plan Phase 10 days Tue 11/21/17 Mon 12/4/17 $5,760.00
16 3.1 Plan methodology is selected2 days Tue 11/21/17 Wed 11/22/17 14 Planner $960.00
17 3.2 Outline for the plan is
developed
5 days Thu 11/23/17 Wed 11/29/17 16 Planner $2,400.00
18 3.3 Review of the plan 3 days Thu 11/30/17 Mon 12/4/17 17 Project Manager $2,400.00
19 M3 Plan is completed 0 days Mon 12/4/17 Mon 12/4/17 18 $0.00
20 4 Design Phase 16 days Tue 12/5/17 Tue 12/26/17 $11,520.00
21 4.1 Design Platform is selected1 day Tue 12/5/17 Tue 12/5/17 19 System Analyst $720.00
22 4.2 Outline for the design
is developed
3 days Wed 12/6/17 Fri 12/8/17 21 System Analyst $2,160.00
23 4.3 Prototype is developed 7 days Mon 12/11/17 Tue 12/19/17 22 System Analyst $5,040.00
24 4.4 Review of the prototype2 days Wed 12/20/17 Thu 12/21/17 23 System Analyst $1,440.00
25 4.5 Simulation of the
completed design
3 days Fri 12/22/17 Tue 12/26/17 24 System Analyst $2,160.00
26 M4 Complete design is formed0 days Tue 12/26/17 Tue 12/26/17 25 $0.00
27 5 Implementation Phase 52 days Wed 12/27/17 Thu 3/8/18 $45,420.00
28 5.1 Storage is developed 10 days Wed 12/27/17 Tue 1/9/18 26 IT Engineer,Storage[1] $9,920.00
29 5.2 Transfer of the data 5 days Wed 1/10/18 Tue 1/16/18 28 IT Engineer $3,800.00
30 5.3 Design analysis for the
ticket system
4 days Wed 1/17/18 Mon 1/22/18 29 IT Engineer $3,040.00
31 5.4 Development of User
interface
6 days Tue 1/23/18 Tue 1/30/18 30 IT Engineer $4,560.00
32 5.5 Coding and
programming is done
12 days Wed 1/31/18 Thu 2/15/18 31 IT Engineer $9,120.00
33 5.6 Integration of ticket
system with storage
8 days Fri 2/16/18 Tue 2/27/18 32 IT Engineer $6,080.00
34 5.7 Installing hardware
components
7 days Wed 2/28/18 Thu 3/8/18 33 IT
Engineer,Computer
Devices[1],Network
$8,900.00
35 M5 New System installed
in Globex
0 days Thu 3/8/18 Thu 3/8/18 34 $0.00
36 6 Testing Phase 20 days Fri 3/9/18 Thu 4/5/18 $13,600.00
37 6.1 Black box testing 5 days Fri 3/9/18 Thu 3/15/18 35 Tester $3,400.00
38 6.2 UX testing 5 days Fri 3/16/18 Thu 3/22/18 37 Tester $3,400.00
39 6.3 Operations and tested 5 days Fri 3/23/18 Thu 3/29/18 38 Tester $3,400.00
40 6.4 white box testing 5 days Fri 3/30/18 Thu 4/5/18 39 Tester $3,400.00
41 M6 Results of tests are compiled0 days Thu 4/5/18 Thu 4/5/18 40 $0.00
42 7 Documentation Phase 6 days Fri 4/6/18 Fri 4/13/18 $3,200.00
43 7.1 Making final documents3 days Fri 4/6/18 Tue 4/10/18 41 Documenter $1,440.00
44 7.2 Review of documents 2 days Wed 4/11/18 Thu 4/12/18 43 Documenter $960.00
45 7.3 Signing off the documents1 day Fri 4/13/18 Fri 4/13/18 44 Project Manager $800.00
46 M7 Project is closed 0 days Fri 4/13/18 Fri 4/13/18 45 $0.00
Project Manager
Project Manager
Documenter
Documenter
Project Manager
Project Manager
10/24
Budgeter
Planner
Budgeter
Budgeter
11/20
Planner
Planner
Project Manager
12/4
System Analyst
System Analyst
System Analyst
System Analyst
System Analyst
12/26
IT Engineer,Storage[1]
IT Engineer
IT Engineer
IT Engineer
IT Engineer
IT Engineer
IT Engineer,Computer Devices[1],Network Comp
3/8
Tester
Tester
Tester
Tester
4/5
Documenter
Documenter
Project Manager
4/13
S T T S M W F
Aug 20, '17 Nov 19, '17 Feb 18, '18 May 20, '18
The work breakdown structure is shown below:

0
Developing Ticketing
System for RALS
1
Initial Phase
1.1
Analysis of the project
feasibility
1.2
Requirement Analysis
1.3
Making Initiation
documents
1.4
Charter documentation
1.5
Project Meetings are
held
1.6
Signing off the
documents
M1
Initial Phase is
completed
2
Resource Accumulation
2.1
Client's requirement is
analyzed
2.2
Project team is
selected
2.3
Budget for the project
is developed
2.4
Outsourcing of the
project materials
M2
Accumulation of the
resources
3
Plan Phase
3.1
Plan methodology is
selected
3.2
Outline for the plan is
developed
3.3
Review of the plan
M3
Plan is completed
4
Design Phase
4.1
Design Platform is
selected
4.2
Outline for the design
is developed
4.3
Prototype is developed
4.4
Review of the
prototype
4.5
Simulation of the
completed design
M4
Complete design is
formed
5
Implementation Phase
5.1
Storage is developed
5.2
Transfer of the data
5.3
Design analysis for the
ticket system
5.4
Development of User
interface
5.5
Coding and
programming is done
5.6
Integration of ticket
system with storage
5.7
Installing hardware
components
M5
New System installed
in Globex
6
Testing Phase
6.1
Black box testing
6.2
UX testing
6.3
Operations and tested
6.4
white box testing
M6
Results of tests are
compiled
7
Documentation Phase
7.1
Making final
documents
7.2
Review of documents
7.3
Signing off the
documents
M7
Project is closed
0
1
2345678
9
1011121314
15
16171819
20
212223242526
27
2829303132333435
36
3738394041
42
43444546
140 days 0%
10/2/17 4/13/18
17 days 0%
10/2/17 10/24/17
3 days 0%
10/2/17 10/4/17
5 days 0%
10/5/17 10/11/17
4 days 0%
10/12/17 10/17/17
3 days 0%
10/18/17 10/20/17
1 day 0%
10/23/17 10/23/17
1 day 0%
10/24/17 10/24/17
0 days 0%
10/24/17 10/24/17
19 days 0%
10/25/17 11/20/17
5 days 0%
10/25/17 10/31/17
7 days 0%
11/1/17 11/9/17
4 days 0%
11/10/17 11/15/17
3 days 0%
11/16/17 11/20/17
0 days 0%
11/20/17 11/20/17
10 days 0%
11/21/17 12/4/17
2 days 0%
11/21/17 11/22/17
5 days 0%
11/23/17 11/29/17
3 days 0%
11/30/17 12/4/17
0 days 0%
12/4/17 12/4/17
16 days 0%
12/5/17 12/26/17
1 day 0%
12/5/17 12/5/17
3 days 0%
12/6/17 12/8/17
7 days 0%
12/11/17 12/19/17
2 days 0%
12/20/17 12/21/17
3 days 0%
12/22/17 12/26/17
0 days 0%
12/26/17 12/26/17
52 days 0%
12/27/17 3/8/18
10 days 0%
12/27/17 1/9/18
5 days 0%
1/10/18 1/16/18
4 days 0%
1/17/18 1/22/18
6 days 0%
1/23/18 1/30/18
12 days 0%
1/31/18 2/15/18
8 days 0%
2/16/18 2/27/18
7 days 0%
2/28/18 3/8/18
0 days 0%
3/8/18 3/8/18
20 days 0%
3/9/18 4/5/18
5 days 0%
3/9/18 3/15/18
5 days 0%
3/16/18 3/22/18
5 days 0%
3/23/18 3/29/18
5 days 0%
3/30/18 4/5/18
0 days 0%
4/5/18 4/5/18
6 days 0%
4/6/18 4/13/18
3 days 0%
4/6/18 4/10/18
2 days 0%
4/11/18 4/12/18
1 day 0%
4/13/18 4/13/18
0 days 0%
4/13/18 4/13/18

Part Four: Risk Analysis and Management Plan for RALS
No. Ran
k
Risk Description Categor
y
Root Cause Triggers Potential
Responses
Risk
Owner
Probabilit
y
Impact Status
R44 1 Failure of
the system
If the
framework
isn't
introduced
properly
inside the
business
then it will
make
number of
dangers and
also
challenges
Technic
al risk
Because of
absence of
proper
learning of
the system
engineer, the
establishmen
t isn't done
appropriately
The
framework
isn't
introduced
by taking
reasonable
time that is
required
The system
should be
installed
properly.
Project
manager
Medium High Set up in 1
week
R19 2 Improper The Financia They expect Budget Proper Financi Medium High Set up in 3

estimation
of budget
expected
spending
plan by the
venture
supervisor
isn't exact
l risk that the
monetary
allowance
isn't precise
as the
venture
chiefs are
very little
experienced
and they
don't break
down the
market
adequately.
related issues
are taken
place
because of
inappropriate
market
analysis
budget
estimation is
needed to be
done by
doing
effective
market
analysis
al
manager
weeks
R8 3 Improper
scheduling
The
administrato
r does not
understand
Project
risk
All
scheduling
related risks
are mainly
In
appropriate
understandin
The project
manager
analyzes and
also
Project
manager
Medium High Set up in 2
week

the task
destinations
and
objectives
properly and
along these
lines the
proper time
table
prepared by
them is not
exact.
occurred
because of
the presence
of
inappropriate
information
regarding the
client’s
requirements
g about the
project that
mainly
created due
different
scheduled
risks
determines
about the
project
requirements
and
deliverables
by gather
better
understandin
g about it.
R32 4 Improper
managemen
t
In-correct
management
of different
project
activities
Project
risk It also
created in-
correct
experience
about the
In
appropriate
experience of
project
managers
guide to
All project
managers
needed to
organize the
project by
Project
manager
s
Medium High Set up in 1
week

created
more
challenges
managers. ineffective
project
management
maintaining
some perfect
methodologi
es and
strategies.
R28 5 Resources Improper
use of
project
resources
Resource
risk
Improper use
of resources
due to proper
experience
Proper
techniques
for resource
management
are not used
The
organization
must proper
experience
project
managers
Project
manager
Medium Mediu
m
Set up in 1
week

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)

Part 5: Quality Management Plan
The quality management plan for RALS project includes,
Stage 1: Identification of the quality issues
Stage 2: Analysis of the quality issues and their effect on venture
Stage 3: Development of alleviation techniques
Stage 4: Monitoring the actualized techniques
Stage 5: Reviewing the arrangement
Part 6: Project Closure
a. 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).
In this paper it mainly discussed about the “roles of monitoring and evaluation in projects”.
Otieno (2000) mainly discussed that various numbers of projects are mainly associated with
third world countries that may fail because of different reasons that includes lack age of
understanding based on needs of monitoring and evaluation.
The paper also discussed about different types of constraints that helps to mitigate different
problems related to project evaluation and implementation schedule. In addition to,
evaluation is the technique that mainly helps to determine all relevancy, effectiveness and
impact of activities based on 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.
This paper also reflects about different project management roles to achieve success. Munns
and Bjeirmi (1996) discussed that the roles of different types of project management
techniques helps to implement the project in very successful way that includes cost
controlling, quality management and time management. The researchers mainly conclude
about the demonstration of appreciation between the project and project management
processes to bring more possibilities 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 prime focus of this paper is one the risk identification techniques used by project
manager (Anca, Cezar & Adrian, 2015). It is mainly identified that all types of project risks
are defined various uncertain events having both negative and positive impact regarding the
project objectives. Apart from that, it is mainly identified shortage of different integrated
management systems and dependencies techniques on different other external participants.
However, it is identified that risk identification becomes one of the important step to manage
different project risks.
Closure checklist
Task Name Stakeholder
Signature
Undertaking feasibility study for the
different manual system
Project manager,
Requirement analyst

Business needs identification Requirement analyst
Development of vendor selection
Accountant, Project
manager
Checking development history of the
vendors
Executive sponsor,
Project manager
Improvement within new system
installation
Developer, Project
manager
Determining the needs of the system
Project manager,
System analyst
Using compatible software and
hardware
Accountant, Project
manager, System
analyst
Identifying test cases as well as test plan Tester
Testing the developed system Project manager, Tester
Assessment as well as risk identification
Project manager, Risk
manager
Risks mitigation
Project manager,
System analyst
Evaluating roistering system functions
Executive sponsor,
Project manager