Project Management Plan and Evaluation

This assignment presents a comprehensive project management plan covering various aspects such as task breakdown, resource allocation (material and labor), evaluation criteria, and project documents. It includes a Work Breakdown Structure (WBS) detailing specific tasks, cost estimates for materials and labor, and defined roles like Project Manager and System Analyst. The evaluation criteria encompass resource allocation techniques, project documentation quality, system design implementation, scope verification methods, and testing results.

ICT Project Management
RALS Roistering System

Table of Contents
Part One: MOV - Measurable Organisational Value.................................................................3
Part Two: Define Scope and produce a Scope Management Plan.............................................4
Requirements:........................................................................................................................4
In-scope and Out-scope of project:........................................................................................5
Deliverables:..........................................................................................................................5
Acceptance Criteria:...............................................................................................................6
List of resources:....................................................................................................................6
Part Three: Project Plan.............................................................................................................8
Part Four: Risk Analysis and Management Plan for RALS.....................................................14
Part 5: Quality Management Plan............................................................................................15
Part 6: Project Closure.............................................................................................................16
a. Annotated Bibliography...................................................................................................16
b. Checklist for RALS project..............................................................................................16
C. Evaluation Criteria...........................................................................................................17
Bibliography.............................................................................................................................18

Part One: MOV - Measurable Organisational Value
The customer, operational, social, financial and strategy becomes the desired areas of impact
of the RALS Roistering ticketing system development project. Some of these factors are
discussed below:
Area of
impact
Description Ranking
Financial The money related structure is mainly clarified for doing the
improvements of operations to co-ordinate the advancements and
the suggestions of the consummations of undertaking.
1st
Customer All the customers are comprehended as the framework range to
raise various types of questions that mainly taken account with the
help of general populations in relation to the task created by RALS
and connection of framework.
2nd
Operational Different operational techniques are selected to shape the security
of operations and the settlement of different procedures for doing
the adjustments in association.
3rd
Strategy The strategies are mainly characterized to affect the operations of
venture of RALS by developing different enhanced and successful
operations.
4th
Social Different operational techniques are suggested to build up
operations security and the combinations of procedures.
5th
Better- RALS venture is observed based on the advancement of other framework to expand
the work proficiency with the help of data administration.
Faster- RALS undertaking mainly helps to incorporate all the operations of venture as well
as advancement to expand the speeds of operations.
Rank Impact Metrics Timeframe

1 Financial Revenue, Money, Profit calculation 6 months
2 Customer Clients returning to the association based on the
administrations
2 months
3 Operational Less needed time to finish all types of
hierarchical operations.
2 months
4 Strategy All volunteers needed to be followed due to the
utilization of framework organized by RALS
1 month
5 Social All volunteers maintained the capacity to get
linked with all clients
3 months
Part Two: Define Scope and produce a Scope Management Plan
Scope Definition: The responsibility of RALS system advancement mainly helps to build up
all the operational changes of Globex to follow all volunteer’s and client’s information with
the help of framework that is created.
Requirements: Some of the requirements of project include both project materials and team
to develop all types of project operations. Some of the requirements of resources are listed
below:
Resource Name Type
System Analyst Work
Storage Material
IT Engineer Work
Documenter Work
Wireless routers Material
Project Manager Work
Planner Work

Computer Devices Material
Tester Work
Budgeter Work
Network Components Material
In-scope and Out-scope of project:
The in-scope of project includes:
 Improvement of the RALS Roistering system for doing the business in Globex.
 It also helps to incorporate different information of volunteers counting personal
details, qualifications details an different other additional details
 To assists in the completion of documentations based on both functional as well as
non-functional requirements
 Completion of the project within the time frame of 244 days
The out-scope of project includes:
 Proper training and guidance are provided to all Globex workers
 System maintenance related issues in relation to the data security and service quality
are not mentioned
Deliverables:
Some of the deliverables of RALS Roistering project are listed below:
 To do the proper testing of system, an updated test plan of report must be created
 Documentation of proper budget plan
 Maintain the records of entire developmental phase
 Creation of training manual
 Scope Verification techniques

 Development of exact report based on system requirements
Acceptance Criteria:
Checklist Item Checked
Project Plan Advancement 
Improvised Resource Allocation Plan 
Closing of all associated project documents project charter and initiation
documents

Feasible system designing documents 
Organized usage designing documents 
Pre-determined test results 
List of resources:
Resource Name Tasks
Budgeter Analysis of Client’s requirement
Development of project budget
Outsourcing of all used project materials
Computer Devices Installation of different hardware documents
Documenter Preparation of Initiation documents
Project Charter documentation
Preparation of project final documents
Documents review
IT Engineer Increases of Storage
Data Transfer range
Design analysis of ticketing system
User Interface development

Programming and Coding is done
incorporation of ticket system
Hardware components installation
Network Components Installing hardware components
Planner Proper selection of project team
Proper methodology selected
Plan outline developed
Project Manager Doing project feasibility analysis
Requirement Analysis
Project Meetings are organized
Signing off the documents
Plan review
Signing off the documents
Storage Storage is developed
System Analyst Design Platform is selected
Outline for the design is developed
Prototype is developed
Review of the prototype
Simulation of the completed design
Tester Black box testing
UX testing
Operations and tested
white box testing
Wireless routers Hardware components installation
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
4 days Thu Tue 3 Documenter $1,920.00

documents 10/12/17 10/17/17
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 7 days Wed Thu 33 IT Engineer, $8,900.00

hardware
components 2/28/18 3/8/18
Computer
Devices[1],
Network
Components[1],
Wireless
routers[1]
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

ID Task
Mode
WBS Task Name Duration Start Finish Predecessors 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],Netwo
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

Below is the Work Breakdown Structure (WBS) of the RALS project:
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. REF001 REF003 REF03 REF004 REF005
Rank 1st 2nd 3rd 4th 5th
Risk System
Failure
Over
budgeting
Design flaws Management
Issue
Delay in
completion
Description Framework
irregularities
are occurred
due to
improper
ticketing
arrangement
of RALS
The exercise
of venture
created over
pressure due
to selected
assets
because of
over
planning of
resources
The issues of
plan that done
for ticketing
framework
becomes
remarkable
factors to have
the better
understanding
of RALS
project
Selecting of
precise
procedures
and plans
The
administrative
issues
become an
important
point to
mitigate all
obstacles
faced in the
undertaking
project
Category Technical Financial Technical Operational Performance
Triggers Different
system flaws
Shortage of
sufficient
resources
Non existence
of design
methodologies
Lack age of
different
management
approaches
This project
tends to
create
different
issues that
becomes
hurdles to the
successful
completion of
different
project

operations
Potential
Responses
Framework
testing
required
before doing
execution
Progression
of temporary
created plan
of the task
Choosing of a
proper plan
procedure for
the RALS
Creation of
obstacles
based on the
finishing
products of
the project
Proper
utilization of
different
administrative
rules and
standards
Risk Owner IT Engineer Budgeter Designer Project
Manager
Planner
Probability Likely Possible Likely Possible Almost
certain
Impact Critical Medium Medium Medium Low
Probability
of
occurrence
Impact of occurrence
Very low Low Medium High Very
high
Rare
Unlikely
Possible Management
Issue
Over budgeting
Likely Absence of
Design
Methodolog
y
System
Failure
Almost
Certain
Delay in
completio
n
Part 5: Quality Management Plan
In the quality management plan of RALS, it includes different stages:
Stage 1: Classification of different quality issues

Stage 2: Examination of various quality issues along their effects
Stage 3: Creation of alleviation methods
Stage 4: Screening of different actualized techniques
Stage 5: Arrangement reviewing
Part 6: Project Closure
a. Annotated Bibliography
Kerzner (2013) discussed that the technique of task administration is produced with the help
of different vital administrative strategies. Apart from that, it mainly discussed about different
procedures and techniques that mainly created due to task administration and also become
useful for the co-ordination of different capabilities and enhanced research procedures
associated with any organization.
In this project evaluation, Schwalbe (2015) discussed that the various administrative issues
may confront about various issues related with the venture in effective way due to the
techniques of data handling and improvements. It also mainly needed to have the
advancement of innovative techniques as well as proper creation of venture capacities.
On the other side, in this same context, researchers concludes that the item life cycle
administrative system may suggested to build up various operation related issues of the
venture (Boulmetis & Dutwin, 2014). Apart from that, it mainly be believable that proper
utilization of different administrative standards help to mitigate the causing effects of
improvement framework models.
b. Checklist for RALS project
Checklist Item Checked
Project Plan Advancement 
Improvised Resource Allocation Plan 
Closing of all associated project documents project charter and initiation
documents

Feasible system designing documents 

Organized usage designing documents 
Pre-determined test results 
C. Evaluation Criteria
 Resource Allocation Techniques and Project Evaluation techniques
 Project documents project charter and initiation documents
 System Design and Implementation Plan
 Scope Verification techniques
 Testing Results

Bibliography
Boulmetis, J., & Dutwin, P. (2014). The ABCs of evaluation: Timeless techniques for
program and project managers (Vol. 56). John Wiley & Sons.
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.
Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Nanda, V. (2016). Quality management system handbook for product development
companies.CRC Press.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.