Framework Improvement Models for RALS Project

This assignment focuses on analyzing and implementing framework improvement models within the context of a RALS (likely referring to a specific type of project or system) project. It includes a detailed checklist to guide the implementation process, outlining key aspects such as project planning, resource allocation, documentation, system design, user experience, and testing expectations. Evaluation criteria are provided for assessing the effectiveness of these improvements across various project stages. Additionally, the assignment references relevant academic literature and resources to support understanding.

Running head: PROJECT MANAGEMENT
Project Management
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1PROJECT MANAGEMENT
1. Part One: MOV - Measurable Organisational Value
The strategy, customer, financial, operational, and social is the desired area of impact for the
RALS ticket system development project. These factors are explained below,
Area of
impact
Description Ranking
Financial the money related framework can be clarified as the operations of the
procedures for the improvement of the operations for coordinating the
advancement of the operations and suggesting the consummation of the
undertaking
1st
Customer the customers can be comprehended as the framework range of raising
different sorts of questions brought by the general population up in connection
to the framework and task created for RALS
2nd
Operational the operational procedures would be inferred for shaping the security of the
operations and its reconciliation of the procedure for the adjustment of the
procedures of the association4th
3rd
Strategy the strategy can be characterized for affecting the operations of the venture of
RALS by building up some successful and enhanced operations
4th
Social the operational procedures would be suggested for building up the security of
the operations and its combination of the procedures
5th
o Better – The RALS venture had seen the advancement of another framework for
expanding the proficiency of work by data administration

2PROJECT MANAGEMENT
o Faster – The RALS undertaking would help in incorporating the operations of the venture
and advancement of the expanded speed of operations
o Cheaper – The RALS task would help in dealing with the data on a solitary database and
subsequently it would diminish the general cost of the data framework administration
o Do more – The framework usage at RALS would incorporate the data of the RALS and it
would help in building up the more intelligent procedures of the association.
Rank Impact Metrics Timeframe
1 Financial Money Profit and Revenue era 6 months
2 Customer Number of clients returning to the association for their
administrations
2 months
3 Operational Less Consumption of time for the finishing of the hierarchical
operations
2 months
4 Strategy The volunteers would get followed because of the utilization of
the framework created in RALS
1 month
5 Social Volunteers would have the capacity to get associated with the
clients
3 months

3PROJECT MANAGEMENT
2. Part Two: Define Scope and produce a Scope Management Plan
Scope Definition: The undertaking of RALS Ticketing System advancement would help in
building up the change of the operations of the Globex for following client's and volunteer's data
by the assistance of framework created.
Requirements: The requirements of the project include both project team and materials for the
development of the project operations. The requirements of the project are,
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 of scope items of the project: The in-scope things of the RALS venture are
get ready for the operations of the undertaking, improvement of the RALS Ticketing System,
increment of effectiveness of the administration of the data about volunteers, and helping for

4PROJECT MANAGEMENT
operational and key advancement. The out of degree things of the RALS venture incorporate
upkeep exercises, conveyance of the materials, and preparing of the labourers in Globex
Deliverables of the project: The deliverables for the RALS venture are,
a. Project Plan and Resource Allocation Plan
b. Project Documents including Initiation and Charter Documentation
c. Scope Verification Plan
d. System Design and Implementation Plan
e. Testing Results
Acceptance Criteria:
Checklist Item Checked
Advancement of the Project Plan 
Improved Resource Allocation Plan 
Closing down the Project Documents including Initiation and Charter
Documentation

Viable System Design 
Well ordered usage design 
Expected Test comes about 

5PROJECT MANAGEMENT
List of resources:
Resource Name Tasks
Budgeter Client's requirement is analyzed
Budget for the project is developed
Outsourcing of the project materials
Computer Devices Installing hardware components
Documenter Making Initiation documents
Charter documentation
Making final documents
Review of documents
IT Engineer Storage is developed
Transfer of the data
Design analysis for the ticket system
Development of User interface
Coding and programming is done
Integration of ticket system with storage
Installing hardware components
Network Components Installing hardware components
Planner Project team is selected
Plan methodology is selected
Outline for the plan is developed
Project Manager Analysis of the project feasibility
Requirement Analysis
Project Meetings are held
Signing off the documents

6PROJECT MANAGEMENT
Review of the plan
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 Installing hardware components
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

7PROJECT MANAGEMENT
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
3. Part Three: Project Plan
WBS Task Name Duration Start Finish Predecessor
s 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

8PROJECT MANAGEMENT
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 Accumulation
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 Tue $11,520.00

9PROJECT MANAGEMENT
12/5/17 12/26/17
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

10PROJECT MANAGEMENT
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 Documentation
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
Gantt chart for the project is shown below,

11PROJECT MANAGEMENT
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 selected7 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 Com
3/8
Tester
Tester
Tester
Tester
4/5
Documenter
Documenter
Project Manager
4/13
S T T S M W
Aug 20, '17 Nov 19, '17 Feb 18, '18 May 20, '18

12PROJECT MANAGEMENT
The Work Breakdown structure is shown in the image 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

13PROJECT MANAGEMENT
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
disappointmen
t may be come
about when the
ticketing
arrangement of
RALS would
neglect to
build up the
compelling
handling of the
data for
building up the
change factors
The exercises
of the venture
may wind up in
causing
overabundance
use of the
undertaking
assets which
may prompt the
over planning
of the task by
The issues of
the plan made
for the
ticketing
framework
would be a
noteworthy
hazard factor
that could
bring about
shaping the
defeat of the
undertaking
2013
Choosing a
precise plan
procedure for
the venture
The issues in
administration
is a main
consideration
for the
improvement
of the
obstacles in
the finishing
of the
undertaking
Category Technical Financial Technical Operational Performance
Triggers Flaws in
system
Lack of
Adequate
Resources
Absence of
Design
Methodology
Lack of
Management
Approach
The project
would tend to
form the
development
of the issues

14PROJECT MANAGEMENT
in successful
completion of
the project
operations
Potential
Responses
Earlier testing
of the
framework
before
execution
Advancement
of temporary
spending plan
for the task
Choosing a
precise plan
procedure for
the venture
improvement of
the obstacles in
the finishing of
the undertaking
Utilization of
undertaking
administration
standards and
operations
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
Methodology
System
Failure
Almost Certain Delay in
completion
5. Part 5: Quality Management Plan
The quality management plan for RALS project includes,
Stage 1: Identification of the quality issues

15PROJECT MANAGEMENT
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
6. Project Closure
a. Annotated Bibliography
As indicated by researchers like Amrollahi, Ghapanchi and Talaei-Khoei (2014), the task
administration can be produced by following the particular vital administration strategies. The
techniques and procedures created for the task administration would be useful for coordinating
the advancement of the enhanced procedures and capacities inside the association.
Then again researchers like Galliers and Leidner (2014), the key administration confront the
issue of dealing with the venture effectively because of the slack of the data handling and
improvement. It would be very required for the advancement of the enhanced innovation and
spontaneous creation for adjusting the capacities for the venture.
Consequently, from the investigation of Stark (2015), it can be inferred that the item life cycle
administration can be suggested for building up the operations of the venture. It is likewise
conceivable that the utilization of the undertaking administration standards would help in
covering the real effect of the framework improvement models.
b. Checklist for RALS project

16PROJECT MANAGEMENT
Checklist Item Checked
Advancement of the Project Plan 
Improved Resource Allocation Plan 
Closing down the Project Documents including Initiation and Charter
Documentation

Viable System Design 
Well ordered usage design 
Expected Test comes about 
C. Evaluation Criteria
a. Project Plan and Resource Allocation Plan
b. Project Documents including Initiation and Charter Documentation
c. Scope Verification Plan
d. System Design and Implementation Plan
e. Testing Results

17PROJECT 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.

18PROJECT 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.