Project Management Plan Template

This assignment provides a detailed template for creating a project management plan. It includes sections for identifying strengths, weaknesses, opportunities, and threats (SWOT analysis), outlining roles and responsibilities of team members, and describing the overall project scope. The template is designed to guide students in developing a structured and comprehensive project management plan.

Running head: PROJECT REPORT
Project Report: Global Health Record System for Health Organisation
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1PROJECT REPORT
Table of Contents
1. Project Title.................................................................................................................................2
2. Introduction..................................................................................................................................2
3. Business Case..............................................................................................................................2
3.1 Project Background...............................................................................................................2
3.2 Project Analysis: SWOT Analysis.........................................................................................3
3.3 Project Objectives..................................................................................................................6
3.4 Assumptions and Constraints................................................................................................6
4. Project Scope...............................................................................................................................7
4.1 Project Scope Statement........................................................................................................7
4.2 High Level WBS....................................................................................................................8
5. Literature Review......................................................................................................................11
5.1 Literature Summary on Project/Program Best Practice Delivery Models...........................11
5.1.1 Project Delivery Methods.............................................................................................11
5.2 Literature Summary Related to Project Topic.....................................................................12
6. Selected Project Delivery Method.............................................................................................12
6.1 Processes – Phases in Project Delivery System...................................................................12

2PROJECT REPORT
6.1.1 Advantages of Project Delivery System.......................................................................13
6.1.2 Disadvantages and Risk in Project Delivery System....................................................13
6.2 Contracting and Procurement Methods...............................................................................13
7. Management Plans and Delivery System Implementation........................................................14
7.1 Human Resource Management Plan....................................................................................14
7.1.1 Organizational and operation chart...............................................................................14
7.2 Analysis of Stakeholder and Communication Management Plan.......................................15
7.3 Project Timetable.................................................................................................................16
7.4 Feasibility Analysis.............................................................................................................19
7.5 Project Governance..............................................................................................................20
8. Conclusion.................................................................................................................................20
9. References..................................................................................................................................22

3PROJECT REPORT
1. Project Title
The title of the project is “Global Health Record System for Health Organisation” and it
is formed for implementing an information system that could store the health records of the
patients, doctors, and diseases from all over the world.
2. Introduction
The project management holds an integral role is successful completion of the project
operations and its simplified development and management. The development of the project
would help in integrating the development of the effective and improved analysis of the system
management and development process. The development of the project would be helpful for the
integration of the database for the records of the patients and doctors. The following assignment
would be developed for evaluation of the project business case, background, swot analysis,
objectives, assumptions and constraints, scope, literature review on the topic, summary on
project/program best practice delivery models, selected project delivery method, and
management plans and delivery system implementation would be done for the project of Global
Health Record System for Health Organisation.
3. Business Case
3.1 Project Background
The project is developed for assisting the deployment of the effective and improved
organization processing within the information processing of the organization. The involvement
of the project integration would be helpful for forming the supplementary development of the
operations of information seeking by health organizations. The project would develop an

4PROJECT REPORT
integrated information system for the storing the data and information related to the patients and
doctors. The analysis would help in forming the situational analysis of the project in terms of
technical and financial feasibility. The issues that could be solved by development of the health
record system are,
 Lack of information access
 Delay in treatment of the patients
 Issues in communication among the doctors and patients
 Absence of an overview of the health organization
The implementation of the project would be helpful for critical evaluation of the
technology for developing solutions to these problems. The health record system would serve the
purpose of the communication and information transmission for various operations of the health
organization. It would also provide scope for the backing up the data in an integrated storage
system.
3.2 Project Analysis: SWOT Analysis
The SWOT analysis is the concept of forming the effective and improved evaluation of
the project of development of health record system for health organization. The analysis of the
project is shown in the following diagram,

5PROJECT REPORT
Figure 1: SWOT Analysis of the Project
(Source: Created by the author)
Strengths The strengths of the project of development of the health record system
are integrated database, improved data transfer and access, and use of
technology. The use of the integrated database would be helpful for
developing the effective and smart project operations. The use of the
integrated information system management would be helpful for
conveying the development of the information. The data transfer process
would be facilitated due to the deployment of the system and it would
form the development of the improved analysis methods.
Weaknesses The weaknesses of the project of development of the health record system
Threats
Cyber Criminal Activities
Data lost and manipulation
Crashing of the system
Weaknesses
Absence of prior knowledge
Probability of Technical Errors
Issues in alignment of database
Opportunities
Communication Improvement
Global Data Integration
Faster Information Processing
Strengths
Integrated database,
Improved data transfer and access
Use of technology
SWOT Analysis

6PROJECT REPORT
are absence of prior knowledge, probability of technical errors, and issues
in alignment of database. The development of the project would form the
analysis of the effective and improved information management. The
completion of the project implementation can be benefitted by the use of
the supportive data management process. However, the issues of absence
of prior knowledge, probability of technical errors, and issues in
alignment of database would form the major conflict in the completion of
the project operations.
Opportunities The opportunities of the project of development of the health record
system are communication improvement, global data integration, and
faster information processing. The health record system would be helpful
for carrying out the analysis of the project integration management and its
synthetic development of the operations. The analysis of the opportunities
would tend to form the development of the system integration and
development.
Threats The threats of the project of development of the health record system are
cyber criminal activities, data lost and manipulation, and crashing of the
system. The project requires the use of technical development and
processing. Hence it is possible that the use of the technology would bring
about the issues and problems of running the information system
development. The threats of the project are based on the exploitation and
formation of the issues in the information system for health records.
Table 1: SWOT Analysis of the Project
(Source: Created by the author)
3.3 Project Objectives

7PROJECT REPORT
The project titled Global Health Record System for Health Organisation is developed for
implementing an information system that could store the health records of the patients, doctors,
and diseases from all over the world. The objectives of the project are,
 To develop a health record system for the health organization
 To form the effective transmission of the information at required places
 To support the deployment of the supplementary management of the information
 To integrate the data about the patients and doctors on a single database platform
 To increase the performance of data access within the health organization
3.4 Assumptions and Constraints
The assumptions of the project titled Global Health Record System for Health
Organisation are given below,
Timely Completion of the project: Global Health Record System for Health
Organisation Project would be completed in the estimated time duration as per the plan
Operation Improvement for Health Organization: Global Health Record System for
Health Organisation Project would be successful in implementing the development of the data
transfer
Accumulation of Project Resources: The resources required in the project would be
easily accumulated and it would serve the purpose of developing the system

8PROJECT REPORT
The constraints of the project titled Global Health Record System for Health Organisation
are given below,
Technology Dependency: Global Health Record System for Health Organisation Project
would be dependent on the technological knowledge of the organization. It is possible that the
health organization might not be able to successfully implement the system and convey their
requirements of the project.
Security Limitation: The limited security functions for the Global Health Record
System for Health Organisation Project is another constraint for the operations of the
organization. It is possible that the project would comprise of some security structure that would
inhabit the deployment of the project operations.
4. Project Scope
4.1 Project Scope Statement
The project scope statement for the Global Health Record System for Health
Organisation Project is given below,
“The project involves the development of a health record system for the health
organization for forming the effective transmission of the information at required places and
supporting the deployment of the supplementary management of the information. The successful
implementation of the project would help in integrating the data about the patients and doctors
on a single database platform and increasing the performance of data access within the health
organization.”

9PROJECT REPORT
4.2 High Level WBS
The high level WBS for the Global Health Record System for Health Organisation
Project can be shown in both table and diagram format,
In table format,
WBS Task Name
0 Global Health Record System for Health Organization
1 Project Initiation and Plan Development Phase
1.1 Project Scope Analysis
1.2 Charter Documentation
1.3 Development of PID
1.4 Project Resources are gathered
1.5 Plan outline development
1.6 Resource allocation to plan
1.7 Plan review
M1 Plan is Approved
2 Global Health Record System Design Phase
2.1 Analysis of Design Requirements
2.2 Design Methodology is selected
2.3 System design is developed
2.4 Design Review in terms of feasibility and sustainability
M2 Design is Approved
3 Development of Global Health Record System
3.1 Integrated Database is developed

10PROJECT REPORT
3.2 Health Records data is stored on the integrated database
3.3 System Analysis is done
3.4 User Interface for the system is built
3.5 Functions of the system is Programmed
3.6 Security Functions are aligned
3.7 Software and Hardware components are integrated
3.8 Server Connection for Global Data Integration
3.9 High Security (IDS/IPS, Encryption, Authorization) is applied
M3 Global Health Record System is Developed
4 Testing of the System Developed
4.1 User Function Testing
4.2 Prototyping and Simulation testing
4.3 Black box and white box testing
M4 Testing Results are documented
5 Final Documents
5.1 Making Final Project Document
5.2 Reviewing the documents made
5.3 Submission of the documents
5.4 Signed off
M5 Project is Closed
Table 2: Project WBS
(Source: Created by the author)

11PROJECT REPORT
In diagram format,
0 - Global Health Record
System for Health
Organisation
1- Project Initiation and Plan
Development Phase
1.1 - Project Scope Analysis
1.2 - Charter Documentation
1.3 - Development of PID
1.4 - Project Resources are
gathered
1.5 - Plan outline
development
1.6 - Resource allocation to
plan
1.7 - Plan review
M1 - Plan is Approved
2 - Global Health Record
System Design Phase
2.1 - Analysis of Design
Requirements
2.2 - Design Methodology is
selected
2.3 - System design is
developed
2.4 - Design Review in terms
of feasibility and
sustainability
M2 - Design is Approved
3 - Development of Global
Health Record System
3.1 - Integrated Database is
developed
3.2 - Health Records data is
stored on the integrated
database
3.3 - System Analysis is done
3.4 - User Interface for the
system is built
3.5 - Functions of the system
is Programmed
3.6 - Security Functions are
aligned
3.7 - Software and Hardware
components are integrated
3.8 - Server Connection for
Global Data Integration
3.9 - High Security (IDS/IPS,
Encryption, Authorization)
is applied
M3 - Global Health Record
System is Developed
4 - Testing of the System
Developed
4.1 - User Function Testing
4.2 - Prototyping and
Simulation testing
4.3 - Black box and white box
testing
M4 - Testing Results are
documented
5 - Final Documents
5.1 - Making Final Project
Document
5.2 - Reviewing the
documents made
5.3 - Submission of the
documents
5.4 - Signed off
M5 - Project is Closed
Figure 2: Project WBS
(Source: Created by the author)

12PROJECT REPORT
5. Literature Review
5.1 Literature Summary on Project/Program Best Practice Delivery Models
According to Fong, Avetisyan and Cui (2014), the project delivery model comprises of
developing an effective and improvised planning, designing and implementing the execution of
the project operations. The delivery of the project is one of the most sincere methods for the
analysis of the acquisition strategy for the development of the project deliverance to the client.
The selection of the project delivery model is another major factor that could impact the success
of the project (Kereri & Gad, (2015). The delivery methods chosen should be done only after
prior knowledge of the various project delivery methods.
5.1.1 Project Delivery Methods
As opined by Shrestha et al. (2014), the various project delivery methods used for the different
projects are CMR or construction management at risk, design-bid-build, design build, and multi
prime. These methods would be helpful for conveying the appropriateness of the project
deliverance to the client. The delivery method of construction management at risk is implied for
entailing the commitment made by the project owner and it’s significant delivery of the project
in a definite schedule and price. The operations of project would comprise of the development of
the effective and improved processes. These techniques would be useful for passing on the
fittingness of the task deliverance to the customer (Lines, Sullivan & Smithwick, (2014). The
conveyance strategy for development administration in danger is inferred for involving the
dedication made by the undertaking proprietor and it's noteworthy conveyance of the task in a
positive calendar and cost. The operations of project would include the advancement of the

13PROJECT REPORT
powerful and enhanced procedures. The distinctive activities are CMR or development
administration in danger, plan offer form, outline manufacture, and multi prime.
5.2 Literature Summary Related to Project Topic
According to Fewings (2013), the project management holds a fundamental part is
effective fruition of the undertaking operations and its improved advancement and
administration. The advancement of the task would help in coordinating the improvement of the
compelling and enhanced investigation of the framework administration and advancement
process. The improvement of the task would be useful for the mix of the database for the records
of the patients and specialists. The undertaking is produced for helping the arrangement of the
viable and enhanced association preparing inside the data handling of the association. On the
other hand, Golini, Kalchschmidt and Landoni (2015) have pointed out that the association of the
task combination would be useful for framing the supplementary advancement of the operations
of data looking for by wellbeing associations. The task would build up an incorporated data
framework for the putting away the information and data identified with the patients and
specialists. The investigation would help in framing the situational examination of the project as
far as specialized and money related practicality.
6. Selected Project Delivery Method
6.1 Processes – Phases in Project Delivery System
The effective project delivery method would be implied for the development of the
processes of the Global Health Record System for Health Organisation Project. The project
delivery system that can be used for the project is Construction Management at Risk method.

14PROJECT REPORT
The construction management at risk includes three linear phases namely Design, Bid, and
Build/Fast Tracked. The project would be helpful for the deployment of the health record
system and it would result in implication of the effective processing. The phases would be
implied for developing the effective skills and processes.
6.1.1 Advantages of Project Delivery System
The Construction Management at risk would be helpful for involving three prime persons
in the project and they are owner, designer, and CM-constructor. It would help in concentrating
the deployment of the effective and improved functions in the organization. There are two
separate contracts in this method namely, owner to designer and owner to CM-constructor.
6.1.2 Disadvantages and Risk in Project Delivery System
The Construction Management at risk would result in cornering the project by limiting
the power of the project to the owner. The sole responsibility of detailing the design for the
project is the owner and it would form the issues in developing the concise planning.
6.2 Contracting and Procurement Methods
The contracting and procurement methods are helpful for the involvement of the
successful project completion. The procurement and contracting methods are helpful for building
the appropriate methods of development strategy and its significant management strategy. The
contract development is implied for forming the analysis of the materials and supplying the
project with integration and management. The contract selection would form the management of
the operations. The contracting and acquirement techniques are useful for the inclusion of the
fruitful task culmination. The obtainment and contracting strategies are useful for building the

15PROJECT REPORT
suitable techniques for advancement system and its huge administration procedure. The
agreement advancement is suggested for shaping the examination of the materials and providing
the undertaking with reconciliation and administration. The agreement determination would
shape the administration of the operations.
7. Management Plans and Delivery System Implementation
7.1 Human Resource Management Plan
The human resource management plan is deployed for the management of the individuals
in the project and it would carry on the development of the human resource management plan.
The project comprises of Client, Project Manager, IT Engineer, Documenter, Planner, System
Analyst, and Developer. The human resources would be responsible for carrying out the
activities of the project and develop the effective completion of the Global Health Record
System for Health Organisation Project. The resource development of the project would develop
the involvement of these human individuals for the development of the project.
7.1.1 Organizational and operation chart

16PROJECT REPORT
Figure 3: Project Organization Chart
7.2 Analysis of Stakeholder and Communication Management Plan
Name of the
Stakeholder
Role in the project Communication
Medium
Information
Communicated
Client Provides the basic requirements of
the project and resources for the
project
Would be the benefited by the use
of the system integration
Reports Requirements and
any changes in the
project
Project
Manager
Would take care of all the
activities of the project including
the planning and developing the
proper project analysis
Emails Project progress and
resource usage
IT Engineer Would take care of all the IT and
technology related operations of
Conversation Development of the
system and its
Client Project Manager
IT Engineer
DeveloperSystem Analyst
PlannerDocumenter

17PROJECT REPORT
the project analysis
Documenter Documentation of the project plan
and its synthesis for the
management of the operations
Project Reports All documents that
need to be developed
Planner Planning the project and
scheduling the activities of the
project for ensuring the system
would be developed
Plan Document Activities scheduling
System
Analyst
The analysis of the system and its
requirements would be in-charge
of the effective development of the
project analysis documents
Conversation Requirements of the
system operations
Developer System developing and formation
would be eased by the use of the
effective synthesizing of the
operations
Emails Issues in
development of the
system
Table 3: Project Stakeholder and Communication Plan
7.3 Project Timetable
The time table for the Global Health Record System for Health Organisation Project can
be shown in table and Gantt chart format below,
In table format,
WBS Task Name Duration Start Finish Predecessors
0 Global Health Record System for Health
Organization 98 days Fri 12/1/17 Tue
4/17/18
1 Project Initiation and Plan
Development Phase 22 days Fri 12/1/17 Mon
1/1/18
1.1 Project Scope Analysis 2 days Fri 12/1/17 Mon
12/4/17

18PROJECT REPORT
1.2 Charter Documentation 3 days Tue
12/5/17
Thu
12/7/17 2
1.3 Development of PID 3 days Fri 12/8/17 Tue
12/12/17 3
1.4 Project Resources are gathered 5 days Wed
12/13/17
Tue
12/19/17 4
1.5 Plan outline development 6 days Wed
12/20/17
Wed
12/27/17 5
1.6 Resource allocation to plan 2 days Thu
12/28/17
Fri
12/29/17 6
1.7 Plan review 1 day Mon 1/1/18 Mon 1/1/18 7
M1 Plan is Approved 0 days Mon 1/1/18 Mon 1/1/18 8
2 Global Health Record System Design
Phase 16 days Tue 1/2/18 Tue
1/23/18
2.1 Analysis of Design Requirements 4 days Tue 1/2/18 Fri 1/5/18 9
2.2 Design Methodology is selected 1 day Mon 1/8/18 Mon 1/8/18 11
2.3 System design is developed 8 days Tue 1/9/18 Thu
1/18/18 12
2.4 Design Review in terms of feasibility
and sustainability 3 days Fri 1/19/18 Tue
1/23/18 13
M2 Design is Approved 0 days Tue
1/23/18
Tue
1/23/18 14
3 Development of Global Health Record
System 46 days Wed
1/24/18
Wed
3/28/18
3.1 Integrated Database is developed 8 days Wed
1/24/18 Fri 2/2/18 15
3.2 Health Records data is stored on the
integrated database 2 days Mon 2/5/18 Tue 2/6/18 17
3.3 System Analysis is done 3 days Wed 2/7/18 Fri 2/9/18 18
3.4 User Interface for the system is built 5 days Mon
2/12/18 Fri 2/16/18 19

19PROJECT REPORT
3.5 Functions of the system is Programmed 10 days Mon
2/19/18 Fri 3/2/18 20
3.6 Security Functions are aligned 3 days Mon 3/5/18 Wed 3/7/18 21
3.7 Software and Hardware components are
integrated 4 days Thu 3/8/18 Tue
3/13/18 22
3.8 Server Connection for Global Data
Integration 6 days Wed
3/14/18
Wed
3/21/18 23
3.9 High Security (IDS/IPS, Encryption,
Authorization) is applied 5 days Thu
3/22/18
Wed
3/28/18 24
M3 Global Health Record System is
Developed 0 days Wed
3/28/18
Wed
3/28/18 25
4 Testing of the System Developed 9 days Thu
3/29/18
Tue
4/10/18
4.1 User Function Testing 3 days Thu
3/29/18 Mon 4/2/18 26
4.2 Prototyping and Simulation testing 3 days Tue 4/3/18 Thu 4/5/18 28
4.3 Black box and white box testing 3 days Fri 4/6/18 Tue
4/10/18 29
M4 Testing Results are documented 0 days Tue
4/10/18
Tue
4/10/18 30
5 Final Documents 5 days Wed
4/11/18
Tue
4/17/18
5.1 Making Final Project Document 3 days Wed
4/11/18 Fri 4/13/18 31
5.2 Reviewing the documents made 1 day Mon
4/16/18
Mon
4/16/18 33
5.3 Submission of the documents 0.5 days Tue
4/17/18
Tue
4/17/18 34
5.4 Signed off 0.5 days Tue
4/17/18
Tue
4/17/18 35
M5 Project is Closed 0 days Tue
4/17/18
Tue
4/17/18 36

20PROJECT REPORT
Table 4: Project Schedule
(Source: Created by the author)
In Gantt chart format,
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors Resource Names
0 0 Global Health Record System for Health Organisation98 days Fri 12/1/17 Tue 4/17/18
1 1 Project Initiation and Plan Development Phase 22 days Fri 12/1/17 Mon 1/1/18
2 1.1 Project Scope Analysis 2 days Fri 12/1/17 Mon 12/4/17
3 1.2 Charter Documentation 3 days Tue 12/5/17 Thu 12/7/17 2
4 1.3 Development of PID 3 days Fri 12/8/17 Tue 12/12/17 3
5 1.4 Project Resources are gathered 5 days Wed 12/13/17 Tue 12/19/17 4
6 1.5 Plan outline development 6 days Wed 12/20/17 Wed 12/27/17 5
7 1.6 Resource allocation to plan 2 days Thu 12/28/17 Fri 12/29/17 6
8 1.7 Plan review 1 day Mon 1/1/18 Mon 1/1/18 7
9 M1 Plan is Approved 0 days Mon 1/1/18 Mon 1/1/18 8
10 2 Global Health Record System Design Phase 16 days Tue 1/2/18 Tue 1/23/18
11 2.1 Analysis of Design Requirements 4 days Tue 1/2/18 Fri 1/5/18 9
12 2.2 Design Methodology is selected 1 day Mon 1/8/18 Mon 1/8/18 11
13 2.3 System design is developed 8 days Tue 1/9/18 Thu 1/18/18 12
14 2.4 Design Review in terms of feasibility and sustainability3 days Fri 1/19/18 Tue 1/23/18 13
15 M2 Design is Approved 0 days Tue 1/23/18 Tue 1/23/18 14
16 3 Development of Global Health Record System 46 days Wed 1/24/18 Wed 3/28/18
17 3.1 Integrated Database is developed 8 days Wed 1/24/18 Fri 2/2/18 15
18 3.2 Health Records data is stored on the integrated database2 days Mon 2/5/18 Tue 2/6/18 17
19 3.3 System Analysis is done 3 days Wed 2/7/18 Fri 2/9/18 18
20 3.4 User Interface for the system is built 5 days Mon 2/12/18 Fri 2/16/18 19
21 3.5 Functions of the system is Programmed 10 days Mon 2/19/18 Fri 3/2/18 20
22 3.6 Security Functions are aligned 3 days Mon 3/5/18 Wed 3/7/18 21
23 3.7 Software and Hardware components are integrated4 days Thu 3/8/18 Tue 3/13/18 22
24 3.8 Server Connection for Global Data Integration 6 days Wed 3/14/18 Wed 3/21/18 23
25 3.9 High Security (IDS/IPS, Encryption, Authorization) is applied5 days Thu 3/22/18 Wed 3/28/18 24
26 M3 Global Health Record System is Developed 0 days Wed 3/28/18 Wed 3/28/18 25
27 4 Testing of the System Developed 9 days Thu 3/29/18 Tue 4/10/18
28 4.1 User Function Testing 3 days Thu 3/29/18 Mon 4/2/18 26
29 4.2 Prototyping and Simulation testing 3 days Tue 4/3/18 Thu 4/5/18 28
30 4.3 Black box and white box testing 3 days Fri 4/6/18 Tue 4/10/18 29
31 M4 Testing Results are documented 0 days Tue 4/10/18 Tue 4/10/18 30
32 5 Final Documents 5 days Wed 4/11/18 Tue 4/17/18
33 5.1 Making Final Project Document 3 days Wed 4/11/18 Fri 4/13/18 31
34 5.2 Reviewing the documents made 1 day Mon 4/16/18 Mon 4/16/18 33
35 5.3 Submission of the documents 0.5 days Tue 4/17/18 Tue 4/17/18 34
36 5.4 Signed off 0.5 days Tue 4/17/18 Tue 4/17/18 35
37 M5 Project is Closed 0 days Tue 4/17/18 Tue 4/17/18 36
1/1
1/23
3/28
4/10
4/17
11/19 12/17 1/14 2/11 3/11 4/8 5/6
November 1 January 1 March 1 May 1
Figure 3: Gantt chart of the project
7.4 Feasibility Analysis

21PROJECT REPORT
The project feasibility analysis is based on the development of the project documents like
NPV, Project Budget, Scheduling, Safety and Health Compliance, and Government Approval.
7.5 Project Governance
The project is governed by the board of members of the health organization that are in-
charge of the project team members. The project team comprises of Client, Project Manager, IT
Engineer, Documenter, Planner, System Analyst, and Developer.
8. Conclusion
The completion of the assignment had helped in coordinating the improvement of the
compelling and enhanced investigation of the framework administration and advancement
process. The improvement of the task was useful for the mix of the database for the records of
the patients and specialists. The undertaking is produced for helping the arrangement of the
viable and enhanced association preparing inside the data handling of the association. The
project delivery model comprised of developing an effective and improvised planning, designing
and implementing the execution of the project operations. The delivery of the project was one of
the most sincere methods for the analysis of the acquisition strategy for the development of the
project deliverance to the client. The selection of the project delivery model was another major
factor that could impact the success of the project. The delivery method chosen was done only
after prior knowledge of the various project delivery methods. The operations of project had
comprised of the development of the effective and improved processes. These techniques would
be useful for passing on the fittingness of the task deliverance to the customer. The conveyance
strategy for development administration in danger is inferred for involving the dedication made
by the undertaking proprietor and it's noteworthy conveyance of the task in a positive calendar

22PROJECT REPORT
and cost. The operations of project would include the advancement of the powerful and enhanced
procedures. The distinctive activities are CMR or development administration in danger, plan
offer form, outline manufacture, and multi prime.

23PROJECT REPORT
9. References
Asqtoronto.org., (2017). Seven Quality Tools | ASQ Toronto Section 402. Retrieved 9
September 2017, from http://asqtoronto.org/resources/quality-tools/seven-quality-tools/
Chartier, L. B., Cheng, A. H., Stang, A. S., & Vaillancourt, S. (2017). Quality improvement
primer part 1: Preparing for a quality improvement project in the emergency
department. Canadian Journal of Emergency Medicine, 1-8.
Corona-Suárez, G. A., AbouRizk, S. M., & Karapetrovic, S. (2014). Simulation-based fuzzy
logic approach to assessing the effect of project quality management on construction
performance. Journal of Quality and Reliability Engineering, 2014.
Fewings, P. (2013). Construction project management: an integrated approach. Routledge.
Fong, C. K., Avetisyan, H. G., & Cui, Q. (2014). Understanding the Sustainable Outcome of
Project Delivery Methods in the Built Environment. Organization, Technology &
Management in Construction, 6(3).
Golini, R., Kalchschmidt, M., & Landoni, P. (2015). Adoption of project management practices:
the impact on international development projects of non-governmental
organizations. International Journal of Project Management, 33(3), 650-663.
Handschu, R., Scibor, M., Wacker, A., Stark, D. R., Köhrmann, M., Erbguth, F., ... & Marquardt,
L. (2014). Feasibility of certified quality management in a comprehensive stroke care
network using telemedicine: STENO project. International Journal of Stroke, 9(8), 1011-
1016.

24PROJECT REPORT
Heinrich, S., Irouschek, A., Prottengeier, J., Ackermann, A., & Schmidt, J. (2015). Adverse
airway events in parturient compared with non‐parturient patients. Is there a difference?
Results from a quality management project. Journal of Obstetrics and Gynaecology
Research, 41(7), 1032-1039.
Jazayeri, E., & Pajouhi, H. (2017). Relationship between Construction Project Delivery Methods
and Project Performance. International Journal of Engineering Science, 13615.
Kereri, J. O., & Gad, G. M. (2015). Comparative study of relationship management in design-
bid-build project delivery methods in infrastructure projects.
Kheni, N. A., & Ackon, F. (2015). Impact of Total Quality Management Practices (TQMPs) on
Construction Project Quality Performance in Developing Countries: Study of
Construction Businesses in Ghana. International Journal of Management Science, 2(3),
35-51.
Kwon, O., Lee, N., & Shin, B. (2014). Data quality management, data usage experience and
acquisition intention of big data analytics. International Journal of Information
Management, 34(3), 387-394.
Lappe, M., & Spang, K. (2014). Investments in project management are profitable: A case study-
based analysis of the relationship between the costs and benefits of project
management. International Journal of Project Management, 32(4), 603-612.
Levin, G. (2014). Project Quality Management: Why, What and How. Project Management
Journal, 45(5).

25PROJECT REPORT
Lines, B., Sullivan, K., & Smithwick, J. (2014). An action research approach to implementation
of alternative project delivery methods within architectural, engineering, and construction
owner organizations: Overcoming resistance through education. In Construction
Research Congress 2014: Construction in a Global Network (pp. 2084-2095).
Low, S. P., & Ong, J. (2014). Quality Management. In Project Quality Management (pp. 29-36).
Springer Singapore.
Olafsdottir, H. (2016). Announcement of the IPMA Research Awards 2015. International Journal
of Project Management, 34, A1-A2.
Papp, J. (2014). Quality Management in the Imaging Sciences-E-Book. Elsevier Health Sciences.
Phillips, J. (2013). PMP, Project Management Professional (Certification Study Guides).
McGraw-Hill Osborne Media.
Rees-Caldwell, K., & Pinnington, A. H. (2013). National culture differences in project
management: Comparing British and Arab project managers' perceptions of different
planning areas. International Journal of Project Management, 31(2), 212-227.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Shrestha, P. P., Maharjan, R., Shakya, B., & Batista, J. (2014). Alternative project delivery
methods for water and wastewater projects: the satisfaction level of owners.
In Construction Research Congress 2014: Construction in a Global Network (pp. 1733-
1742).
Wagner, C., Groene, O., Thompson, C. A., Dersarkissian, M., Klazinga, N. S., Arah, O. A., ... &
Lombarts, K. (2014). DUQuE quality management measures: associations between

26PROJECT REPORT
quality management at hospital and pathway levels. International Journal for Quality in
Health Care, 26(suppl_1), 66-73.
Zeng, S. X., Tam, C. M., & Tam, V. W. (2015). Integrating safety, environmental and quality
risks for project management using a FMEA method. Engineering Economics, 66(1).