Project Management Plan Development and Evaluation

This assignment focuses on the development of a comprehensive project management plan. It requires students to outline a project plan, optimize resource allocation, create necessary documentation (including initiation and charter), design the system, develop an implementation plan, and anticipate test results. A key aspect is developing a project evaluation outline, specifically addressing how the project's Measurable Objectives of Value (MOV) will be assessed.

Running head: PROJECT MANAGEMENT
ITC505 Assignment 3 template
Name of the Student:
Student ID:
Name of the University:
Author’s note:

Part One: MOV - Measurable Organisational Value
• Identify the desired area of impact - Rank the following areas in terms of
importance: Strategy / Customer / Financial / Operational / Social
The desired are of impact are strategy, customer, financial, operational, and social and
they are explained below,
Customer the customer can be understood as the system area of raising various
types of queries raised by the people in relation to the system and project developed
for RALS
Strategy the strategy can be defined for impacting the operations of the project of
RALS by developing some effective and improved operations
Financial the financial system can be explained as the operations of the processes
for the development of the operations for integrating the development of the
operations and implying the completion of the project
Operational the operational processes would be implied for forming the safety of
the operations and its integration of the process for the modification of the processes
of the organization
Social the operational processes would be implied for developing the safety of the
operations and its integration of the processes
1st  Financial
2nd  Customer
3rd  Operational
4th  Strategy
5th  Social
• With reference to your project, identify one or two of the following types of value:
o Better – The RALS project had seen the development of a new system for
increasing the efficiency of work by information management
o Faster – The RALS project would help in integrating the operations of the
project and development of the increased speed of operations
o Cheaper – The RALS project would help in managing the information on a
single database and hence it would decrease the overall cost of the information
system management
o Do more – The system implementation at RALS would integrate the
information of the RALS and it would help in developing the smarter
processes of the organization.

• Develop an appropriate metric - this sets the target and expectation of all the
stakeholders. It is important to determine a quantitative target that needs to be
expressed as a metric in terms of an increase or decrease of money. (4 Bullet Points)
Rank Impact Metrics
1 Financial Cash Profit and Revenue generation
2 Customer Number of customers coming back to the organization for their services
3 Operational Less Consumption of time for the completion of the organizational
operations
4 Strategy The volunteers would get tracked due to the use of the system developed in
RALS
5 Social Volunteers would be able to get socialized with the customers
• Determine the timeframe for achieving the MOV - ask yourselves, when do we want
to achieve this target metric?
• SUMMARISE THE MOV IN A CLEAR CONCISE STATEMENT OR TABLE
Rank Impact Timeframe
1 Financial 6 months
2 Customer 2 months
3 Operational 2 months
4 Strategy 1 month
5 Social 3 months
Part Two:
Define Scope and produce a Scope Management Plan

Define the scope: The project of RALS Ticketing System development would help in
developing the improvement of the operations of the Globex for tracking customer’s
and volunteer’s information by the help of system developed.
Requirements: The project of RALS would require the following human and
material resources,
S. No. Resource Resource Type
1 Project Manager Human
2 Planner Human
3 Documenter Human
4 Budgeter Human
5 System Analyst Human
6 IT Engineer Human
7 Tester Human
8 Computer Devices Materials
9 Network Components Materials
10 Storage Materials
11 Wireless routers Materials
In scope-out scope items: The in-scope items of the RALS project are plan for the
operations of the project, development of the RALS Ticketing System, increase of
efficiency of the management of the information about volunteers, and assisting for
operational as well as strategic development. The out of scope items of the RALS
project include maintenance activities, delivery of the materials, and training of the
workers in Globex
Deliverables: The deliverables for the RALS project are,
 Project Plan and Resource Allocation Plan
 Project Documents including Initiation and Charter Documentation
 Scope Verification Plan
 System Design and Implementation Plan
 Testing Results
Acceptance Criteria: The acceptance criteria for the project would comprise of the
following checklist,
Checklist Item Checked
Development of the Project Plan 
Optimized Resource Allocation Plan 
Signing off the Project Documents including Initiation and Charter Documentation 
Effective System Design 
Step by step implementation plan 
Expected Test results 

Provide a list of Resources
Resource Name Activities
Project Manager Project Meetings
Documents are Signed off
Recruiting Project team
Reviewing the plan
Documents are reviewed
Documents are Signed off
Planner Feasibility Analysis
Identification of the Requirements
Selecting Project Plan methodology
Developing Plan outline
Completing the project plan
Budgeter Developing Project Budget
Material Resources are Ordered
Ordered Materials are Received
System Analyst Analysis of the vendor requirements
Selecting design platform
Developing Design outline
Prototyping the design
Simulation is run on the design
IT Engineer Integrated Storage is developed
Data are transferred to the new storage
Design is used for integrated ticketing system
User Interface is developed
Necessary Functions are coded and programmed
Ticketing system is integrated with the storage
Hardware components are installed
Tester User Interface is tested
Functions are tested
Black box testing
White Box testing
Computer Devices Hardware components are installed
Network Components Ticketing system is integrated with the storage
Storage Integrated Storage is developed
Wireless Routers Hardware components are installed
Resource Name Std. Rate
Project Manager $80.00/hr
Planner $90.00/hr

Documenter $85.00/hr
Budgeter $90.00/hr
System Analyst $70.00/hr
IT Engineer $75.00/hr
Tester $65.00/hr
Computer Devices $1200.00
Network Components $560.00
Storage $1500.00
Wireless routers $780.00
Part Three:
The table for the project schedule is given below,
WBS Task Name Duration Start Finish Predecessors Resource Names Cost
0 RALS Ticketing
System
138
days
Mon
10/2/17
Wed
4/11/18 $90,000.00
1 Project
Initialization 22 days Mon
10/2/17
Tue
10/31/17 $15,360.00
1.1 Feasibility
Analysis 6 days Mon
10/2/17
Mon
10/9/17 Planner $4,320.00
1.2 Identification of
the Requirements 6 days Tue
10/10/17
Tue
10/17/17 2 Planner $4,320.00
1.3 Project Initiation
Documents 4 days Wed
10/18/17
Mon
10/23/17 3 Documenter $2,720.00
1.4 Charter
Development 4 days Tue
10/24/17
Fri
10/27/17 4 Documenter $2,720.00
1.5 Project Meetings 1 day Mon
10/30/17
Mon
10/30/17 5 Project Manager $640.00
1.6 Documents are
Signed off 1 day Tue
10/31/17
Tue
10/31/17 6 Project Manager $640.00
M1 Project is Initiated 0 days Tue
10/31/17
Tue
10/31/17 7 $0.00
2 Project Resource
Accumulation 24 days Wed
11/1/17
Mon
12/4/17 $15,360.00
2.1 Analysis of the
vendor requirements 7 days Wed
11/1/17
Thu
11/9/17 8 System Analyst $3,920.00
2.2 Recruiting Project
team 10 days Fri
11/10/17
Thu
11/23/17 10 Project Manager $6,400.00
2.3 Developing
Project Budget 3 days Fri
11/24/17
Tue
11/28/17 11 Budgeter $2,160.00
2.4
Material
Resources are
Ordered
1 day Wed
11/29/17
Wed
11/29/17 12 Budgeter $720.00
2.5 Ordered Materials
are Received 3 days Thu
11/30/17
Mon
12/4/17 13 Budgeter $2,160.00
M2 Resources are
Accumulated 0 days Mon
12/4/17
Mon
12/4/17 14 $0.00
3 Project Planning
and Scheduling 12 days Tue
12/5/17
Wed
12/20/17 $8,480.00
3.1 Selecting Project
Plan methodology 1 day Tue
12/5/17
Tue
12/5/17 15 Planner $720.00
3.2 Developing Plan 3 days Wed Fri 17 Planner $2,160.00

outline 12/6/17 12/8/17
3.3 Reviewing the
plan 2 days Mon
12/11/17
Tue
12/12/17 18 Project Manager $1,280.00
3.4 Completing the
project plan 6 days Wed
12/13/17
Wed
12/20/17 19 Planner $4,320.00
M3 Project Plan is
approved 0 days Wed
12/20/17
Wed
12/20/17 20 $0.00
4 System Designing 12 days Thu
12/21/17
Fri
1/5/18 $6,720.00
4.1 Selecting design
platform 2 days Thu
12/21/17
Fri
12/22/17 21 System Analyst $1,120.00
4.2 Developing
Design outline 4 days Mon
12/25/17
Thu
12/28/17 23 System Analyst $2,240.00
4.3 Prototyping the
design 4 days Fri
12/29/17
Wed
1/3/18 24 System Analyst $2,240.00
4.4 Simulation is run
on the design 2 days Thu
1/4/18
Fri
1/5/18 25 System Analyst $1,120.00
M4 Complete Design
is developed 0 days Fri
1/5/18
Fri
1/5/18 26 $0.00
5 System
Implementation 44 days Mon
1/8/18
Thu
3/8/18 $30,440.00
5.1 Integrated
Storage is developed 10 days Mon
1/8/18
Fri
1/19/18 27 IT Engineer, Storage
[1] $7,500.00
5.2
Data are
transferred to the new
storage
4 days Mon
1/22/18
Thu
1/25/18 29 IT Engineer $2,400.00
5.3
Design is used for
integrated ticketing
system
3 days Fri
1/26/18
Tue
1/30/18 30 IT Engineer $1,800.00
5.4 User Interface is
developed 5 days Wed
1/31/18
Tue
2/6/18 31 IT Engineer $3,000.00
5.5
Necessary
Functions are coded
and programmed
12 days Wed
2/7/18
Thu
2/22/18 32 IT Engineer $7,200.00
5.6
Ticketing system
is integrated with the
storage
4 days Fri
2/23/18
Wed
2/28/18 33
IT Engineer,
Network
Components[1]
$2,960.00
5.7
Hardware
components are
installed
6 days Thu
3/1/18
Thu
3/8/18 34
IT Engineer,
Computer
Devices[1], Wireless
routers[1]
$5,580.00
M5
System is
implemented ate
Globex
0 days Thu
3/8/18
Thu
3/8/18 35 $0.00
6 Testing Phase 16 days Fri
3/9/18
Fri
3/30/18 $8,320.00
6.1 User Interface is
tested 4 days Fri
3/9/18
Wed
3/14/18 36 Tester $2,080.00
6.2 Functions are
tested 4 days Thu
3/15/18
Tue
3/20/18 38 Tester $2,080.00
6.3 Black box testing 4 days Wed
3/21/18
Mon
3/26/18 39 Tester $2,080.00
6.4 White Box testing 4 days Tue
3/27/18
Fri
3/30/18 40 Tester $2,080.00
M6 Testing Results
are developed 0 days Fri
3/30/18
Fri
3/30/18 41 $0.00

7 Final Documents 8 days Mon
4/2/18
Wed
4/11/18 $5,320.00
7.1 Final Documents
are made 5 days Mon
4/2/18
Fri
4/6/18 42 Documenter $3,400.00
7.2 Documents are
reviewed 2 days Mon
4/9/18
Tue
4/10/18 44 Project Manager $1,280.00
7.3 Documents are
Signed off 1 day Wed
4/11/18
Wed
4/11/18 45 Project Manager $640.00
M7 Project is Closed 0 days Wed
4/11/18
Wed
4/11/18 46 $0.00
The Gantt chart image for the project is also given below,

ID Task
Mode
WBS Task Name Duration Start Finish Predecessors Resource Names Cost
0 0 RALS Ticketing System 138 days Mon 10/2/17 Wed 4/11/18 $90,000.00
1 1 Project Intialization 22 days Mon 10/2/17 Tue 10/31/17 $15,360.00
2 1.1 Feasibility Analysis 6 days Mon 10/2/17 Mon 10/9/17 Planner $4,320.00
3 1.2 Identification of the Requirements 6 days Tue 10/10/17 Tue 10/17/17 2 Planner $4,320.00
4 1.3 Project Initiation Documents 4 days Wed 10/18/17 Mon 10/23/17 3 Documenter $2,720.00
5 1.4 Charter Development 4 days Tue 10/24/17 Fri 10/27/17 4 Documenter $2,720.00
6 1.5 Project Meetings 1 day Mon 10/30/17 Mon 10/30/17 5 Project Manager $640.00
7 1.6 Documents are Signed off 1 day Tue 10/31/17 Tue 10/31/17 6 Project Manager $640.00
8 M1 Project is Initiated 0 days Tue 10/31/17 Tue 10/31/17 7 $0.00
9 2 Project Resource Accumulation 24 days Wed 11/1/17 Mon 12/4/17 $15,360.00
10 2.1 Analysis of the vendor requirements 7 days Wed 11/1/17 Thu 11/9/17 8 System Analyst $3,920.00
11 2.2 Recruiting Project team 10 days Fri 11/10/17 Thu 11/23/17 10 Project Manager $6,400.00
12 2.3 Developing Project Budget 3 days Fri 11/24/17 Tue 11/28/17 11 Budgeter $2,160.00
13 2.4 Material Resources are Ordered 1 day Wed 11/29/17 Wed 11/29/17 12 Budgeter $720.00
14 2.5 Ordered Materials are Received 3 days Thu 11/30/17 Mon 12/4/17 13 Budgeter $2,160.00
15 M2 Resources are Accumulated 0 days Mon 12/4/17 Mon 12/4/17 14 $0.00
16 3 Project Planning and Scheduling 12 days Tue 12/5/17 Wed 12/20/17 $8,480.00
17 3.1 Selecting Project Plan methodology 1 day Tue 12/5/17 Tue 12/5/17 15 Planner $720.00
18 3.2 Developing Plan outline 3 days Wed 12/6/17 Fri 12/8/17 17 Planner $2,160.00
19 3.3 Reviewing the plan 2 days Mon 12/11/17 Tue 12/12/17 18 Project Manager $1,280.00
20 3.4 Completing the project plan 6 days Wed 12/13/17 Wed 12/20/17 19 Planner $4,320.00
21 M3 Project Plan is approved 0 days Wed 12/20/17 Wed 12/20/17 20 $0.00
22 4 System Designing 12 days Thu 12/21/17 Fri 1/5/18 $6,720.00
23 4.1 Selecting design platform 2 days Thu 12/21/17 Fri 12/22/17 21 System Analyst $1,120.00
24 4.2 Developing Design outline 4 days Mon 12/25/17 Thu 12/28/17 23 System Analyst $2,240.00
25 4.3 Prototyping the design 4 days Fri 12/29/17 Wed 1/3/18 24 System Analyst $2,240.00
26 4.4 Simulation is run on the design 2 days Thu 1/4/18 Fri 1/5/18 25 System Analyst $1,120.00
27 M4 Complete Design is developed 0 days Fri 1/5/18 Fri 1/5/18 26 $0.00
28 5 System Implementation 44 days Mon 1/8/18 Thu 3/8/18 $30,440.00
29 5.1 Integrated Storage is developed 10 days Mon 1/8/18 Fri 1/19/18 27 IT Engineer,Storage [1] $7,500.00
30 5.2 Data are transferred to the new
storage
4 days Mon 1/22/18 Thu 1/25/18 29 IT Engineer $2,400.00
31 5.3 Design is used for integrated
ticketing system
3 days Fri 1/26/18 Tue 1/30/18 30 IT Engineer $1,800.00
32 5.4 User Interface is developed 5 days Wed 1/31/18 Tue 2/6/18 31 IT Engineer $3,000.00
33 5.5 Necessary Functions are coded and
programmed
12 days Wed 2/7/18 Thu 2/22/18 32 IT Engineer $7,200.00
34 5.6 Ticketing system is integrated with
the storage
4 days Fri 2/23/18 Wed 2/28/18 33 IT
Engineer,Network
Components[1]
$2,960.00
35 5.7 Hardware components are installed 6 days Thu 3/1/18 Thu 3/8/18 34 IT Engineer,Computer Devices[1],Wireless routers[1]$5,580.00
36 M5 System is implemented ate Globex 0 days Thu 3/8/18 Thu 3/8/18 35 $0.00
37 6 Testing Phase 16 days Fri 3/9/18 Fri 3/30/18 $8,320.00
38 6.1 User Interface is tested 4 days Fri 3/9/18 Wed 3/14/18 36 Tester $2,080.00
39 6.2 Functions are tested 4 days Thu 3/15/18 Tue 3/20/18 38 Tester $2,080.00
40 6.3 Black box testing 4 days Wed 3/21/18 Mon 3/26/18 39 Tester $2,080.00
41 6.4 White Box testing 4 days Tue 3/27/18 Fri 3/30/18 40 Tester $2,080.00
42 M6 Testing Results are developed 0 days Fri 3/30/18 Fri 3/30/18 41 $0.00
43 7 Final Documents 8 days Mon 4/2/18 Wed 4/11/18 $5,320.00
44 7.1 Final Documents are made 5 days Mon 4/2/18 Fri 4/6/18 42 Documenter $3,400.00
45 7.2 Documents are reviewed 2 days Mon 4/9/18 Tue 4/10/18 44 Project Manager $1,280.00
46 7.3 Documents are Signed off 1 day Wed 4/11/18 Wed 4/11/18 45 Project Manager $640.00
47 M7 Project is Closed 0 days Wed 4/11/18 Wed 4/11/18 46 $0.00
Planner
Planner
Documenter
Documenter
Project Manager
Project Manager
10/31
System Analyst
Project Manager
Budgeter
Budgeter
Budgeter
12/4
Planner
Planner
Project Manager
Planner
12/20
System Analyst
System Analyst
System Analyst
System Analyst
1/5
IT Engineer,Storage [1]
IT Engineer
IT Engineer
IT Engineer
IT Engineer
IT Engineer,Network Components[1]
IT Engineer,Computer Devices[1],Wireless router
3/8
Tester
Tester
Tester
Tester
3/30
Documenter
Project Manager
Project Manager
4/11
M W F S T T S M W F
Aug 20, '17 Oct 22, '17 Dec 24, '17 Feb 25, '18 Apr 29, '18

The WBS for the project is given in the diagram below,
WBS Task Name
0 RALS Ticketing System
1 Project Initialization
1.1 Feasibility Analysis
1.2 Identification of the Requirements
1.3 Project Initiation Documents
1.4 Charter Development
1.5 Project Meetings
1.6 Documents are Signed off
M1 Project is Initiated
2 Project Resource Accumulation
2.1 Analysis of the vendor requirements
2.2 Recruiting Project team
2.3 Developing Project Budget
2.4 Material Resources are Ordered
2.5 Ordered Materials are Received
M2 Resources are Accumulated
3 Project Planning and Scheduling
3.1 Selecting Project Plan methodology
3.2 Developing Plan outline
3.3 Reviewing the plan
3.4 Completing the project plan
M3 Project Plan is approved
4 System Designing
4.1 Selecting design platform
4.2 Developing Design outline
4.3 Prototyping the design
4.4 Simulation is run on the design
M4 Complete Design is developed
5 System Implementation
5.1 Integrated Storage is developed
5.2 Data are transferred to the new storage
5.3 Design is used for integrated ticketing system
5.4 User Interface is developed
5.5 Necessary Functions are coded and programmed
5.6 Ticketing system is integrated with the storage
5.7 Hardware components are installed
M5 System is implemented ate Globex
6 Testing Phase
6.1 User Interface is tested
6.2 Functions are tested
6.3 Black box testing

6.4 White Box testing
M6 Testing Results are developed
7 Final Documents
7.1 Final Documents are made
7.2 Documents are reviewed
7.3 Documents are Signed off
M7 Project is Closed
Part Four:
Project Risk Analysis and Plan
No.: RTR001
Rank: 1st
Risk: System Failure
Description: System failure might be resulted when the ticketing system of RALS would fail to develop
the effective processing of the information for developing the improvement factors
Category: Technical
Triggers: Flaws in system
Potential Responses: Prior testing of the system before implementation
Risk Owner: IT Engineer
Probability: Likely
Impact: Critical
Status: 1 week set up
No.: RTR002
Rank: 2nd
Risk: Over budgeting
Description: The activities of the project might end up in causing excess utilization of the project
resources which might lead to the over budgeting of the project
Category: Financial
Triggers: Lack of Adequate Resources
Potential Responses: Development of provisional budget for the project
Risk Owner: Budgeter

Probability: Possible
Impact: Medium-high
Status: 2 week set up
No.: RTR003
Rank: 3rd
Risk: Design flaws
Description: The issues of the design made for the ticketing system would be a major risk factor that
could result in forming the downfall of the project
Category: Technical
Triggers: Absence of Design Methodology
Potential Responses: Selecting an accurate design methodology for the project
Risk Owner: Designer
Probability: Likely
Impact: Medium
Status: 3 week set up
No.: RTR004
Rank: 4th
Risk: Management Issue
Description: The issues in management is a major factor for the development of the hindrances in the
completion of the project
Category: Operational
Triggers: Lack of Management Approach
Potential Responses: Use of project management principles and operations
Risk Owner: Project Manager
Probability: Possible
Impact: Medium
Status: 1 week set up
No.: RTR005
Rank: 5th

Risk: Delay in completion
Description: The activities of the project would tend to result in forming the delay in completion of the
project activities and it would result in developing the issues of project
Category: Performance
Triggers: The project would tend to form the development of the issues in successful completion of the
project operations
Potential Responses: Use of proper project scheduling methods
Risk Owner: Planner
Probability: Almost certain
Impact: Low
Status: 3 week set up
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
Part Five:
Quality Management Plan
The quality management plan for RALS ticketing project can be done by following
the steps,
Step 1: Identification of the quality issues
Step 2: Analysis of the quality issues and their impact on project

Step 3: Development of mitigation strategies
Step 4: Monitoring the implemented strategies
Step 5: Reviewing the plan
Quality Assurance Verification and Validation Methods
The quality assurance verification can be done by developing the use of the project
documents like quality review form and scope integration. The analysis and
evaluation of the project would be based for the development of smart integration and
management. It is possible that the use of proper project testing methods like User
Interface testing, Functions testing, Black box testing and White Box testing would be
implied for developing the Testing Results.
Part Six: Closure and Evaluation-Researching for the closure checklist and
project evaluation
a. To prepare for this task, you will be required to provide an annotated bibliography.
According to scholars like Amrollahi, Ghapanchi and Talaei-Khoei (2014), the project
management can be developed by following the specific strategic management
methods. The strategies and processes developed for the project management would
be helpful for integrating the development of the improved processes and functions
within the organization.
On the other hand scholars like Galliers and Leidner (2014), the strategic management
face the issue of managing the project successfully due to the lag of the information
processing and development. It would be highly required for the development of the
improved technology and improvisation for aligning the functions for the project.
Hence, from the study of Stark (2015), it can be concluded that the product life cycle
management can be implied for developing the operations of the project. It is also
possible that the use of the project management principles would help in covering the
major impact of the system development models.
b. Develop a closure checklist that the project team will use to ensure that the project
has been closed properly.
Checklist Item Checked
Development of the Project Plan 
Optimized Resource Allocation Plan 
Signing off the Project Documents including Initiation and Charter
Documentation

Effective System Design 

Step by step implementation plan 
Expected Test results 
c. Develop a project evaluation –outline and discuss how your project’s MOV will be
evaluated.
 Project Plan and Resource Allocation Plan
 Project Documents including Initiation and Charter Documentation
 Scope Verification Plan
 System Design and Implementation Plan
 Testing Results

References
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.

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.