Quality Management Project Research

This assignment delves into the field of quality management. Students are tasked with researching and analyzing various aspects of quality management, including its principles, methodologies, and real-world applications. The assignment likely involves examining case studies of successful quality management implementations and critically evaluating research papers that explore the impact and effectiveness of different quality management tools and techniques.

ITC505 Assignment 3 template

1. Part One: MOV - Measurable Organisational Value
Desired Area of Impact: The desired area of impact for the project of RALS is
classified into five parts namely financial, customer, operational, strategy, and social.
These factors would play a significant role in forming the accurate deployment of the
system of RALS and Globex.
Project Values:
o Better – The project is helpful for improving the operations of RALS due to its
integration of activities
o Faster – The operations of the RALS would be faster due to the increased
performance of the new system of RALS
o Cheaper – The integrates system would be cost efficient for its users in terms
of operations and development
o Do more – The integrated operations would tend to involve the management
of the effective operations and its involvement
Appropriate Metric: The metrics chosen for the project are accomplishment of 110%
of the workload within the end of the month, 70 % of the Return on Investment
should be achieved, and completion of the project activities before the estimated
schedule.
Appropriate Timeframe: The project is targeted to be completed in 6 months of
duration.
Summary MOV: The statement for MOV summary is, “The project will be successful
if every stakeholder can achieve 110% of workload in each month, finish work before
planned date and after six months, if the outcome provides more than 70% ROI; the
project has desired area of interest as Operational, Customer, Social, Strategy, and
Financial and it can bring ‘better’ and ‘faster’ value for the organization”
2. Part Two: Define Scope and produce a Scope Management Plan

Define the scope: Scope can be defined as the prospect of doing any activity of the
project. The project of RALS Ticketing System Development would be developed for
integrating the development of the smart activities of the ticketing system for RALS.
Requirements: The project comprises of developing a ticketing system for the
development of the project integration and management. It is important for
developing the suit for involving the analysis of the improved integration and
management. The requirements for the project are,
Resource Name Type
Analyst Work
Documenter Work
Project Manager Work
Planner Work
Budgeter Work
Designer Work
IT Engineer Work
Database Admin Work
Developer Work
Programmer Work
Tester Work
Software Material
Hardware Material
Network Components Material
Design Tools Material
Computer Devices Material
Documents Material
Testing Tools Material
Table 1: Project Requirements
In scope-out scope items:

The project plan, system documents, Project Charter document, Project Budget,
System Design, Testing Results, and final documents are in scope items of the project.
The transportation requirements and outsourced activities of the project are out of
scope items for the project.
Deliverables: The deliverables for the project are,
WBS Task Name
1.2 Development of project initiation documents
1.3 Project Charter document is made
2.3 Project Budget is developed
2.5 Plan is reviewed
M3 System Design is approved
4.4 User interface of the system is developed
4.6 Hardware components are integrated
4.5 Functions are programmed
4.7 Application program is developed
M5 Testing Results are documented
6.1 Making final documents of the project
Table 2: Project Deliverables
Acceptance Criteria: The acceptance criteria for the project are successful
completion of the project in the estimated time and budget, testing results are positive,
and the user design is as per the client’s requirements.
Provide a list of Resources:
Resource Name Work Duration
Analyst Analysis of the requirements 24 hrs
Documenter Development of project initiation documents 40 hrs
Project Charter document is made 32 hrs
Submission of charter 8 hrs
Making final documents of the project 32 hrs

Project Manager Project Kick off meeting 8 hrs
Reviewing of the charter document 8 hrs
Plan is reviewed 16 hrs
Reviewing the final documents 8 hrs
Signing off 8 hrs
Planner Selection of plan outline 16 hrs
Resources are assigned 32 hrs
Budgeter Resources are accumulated 40 hrs
Project Budget is developed 24 hrs
Designer Design Platform is selected 16 hrs
Appropriate tools is used for making design 56 hrs
IT Engineer Design is reviewed 8 hrs
Selecting development platform 24 hrs
Database Admin Building database for the system 80 hrs
Integration of the database with existing data 64 hrs
Submission of final documents 8 hrs
Developer User interface of the system is developed 72 hrs
Hardware components are integrated 96 hrs
Programmer Functions are programmed 120 hrs
Application program is developed 104 hrs
Tester Prototype Testing 40 hrs
Design Testing 40 hrs
Simulation Testing 40 hrs
White Box Testing 40 hrs
Black Box Testing 40 hrs
Software Resources are accumulated 1
Building database for the system 1
Application program is developed 1
Hardware Resources are accumulated 1
Hardware components are integrated 1

Network Components Resources are accumulated 1
Integration of the database with existing data 1
Design Tools Appropriate tools is used for making design 1
User interface of the system is developed 1
Computer Devices Resources are accumulated 1
Selecting development platform 1
Functions are programmed 1
Hardware components are integrated 1
Documents Development of project initiation documents 1
Project Charter document is made 1
Making final documents of the project 1
Testing Tools Prototype Testing 1
Design Testing 1
Simulation Testing 1
White Box Testing 1
Black Box Testing 1
3. Part Three: Project Schedule
The schedule for the project of RALS Ticketing System Development is given in the
table below,
WBS Task Name Duration Start Finish Predecessors Resource Names
0
RALS Ticketing
System
Development
143 days Mon
10/2/17
Wed
4/18/18
1 Project
initialization 15 days Mon
10/2/17
Fri
10/20/17
1.1 Analysis of the
requirements 3 days Mon
10/2/17
Wed
10/4/17 Analyst
1.2
Development of
project initiation
documents
5 days Thu
10/5/17
Wed
10/11/17 2 Documenter,
Documents[1]
1.3 Project Charter
document is made 4 days Thu
10/12/17
Tue
10/17/17 3 Documenter,
Documents[1]

1.4 Project Kick off
meeting 1 day Wed
10/18/17
Wed
10/18/17 4 Project Manager
1.5 Submission of
charter 1 day Thu
10/19/17
Thu
10/19/17 5 Documenter
1.6
Reviewing of
the charter
document
1 day Fri
10/20/17
Fri
10/20/17 6 Project Manager
M1 Charter
Approval 0 days Fri
10/20/17
Fri
10/20/17 7
2 Project Planning 16 days Mon
10/23/17
Mon
11/13/17
2.1 Selection of
plan outline 2 days Mon
10/23/17
Tue
10/24/17 8 Planner
2.2 Resources are
accumulated 5 days Wed
10/25/17
Tue
10/31/17 10
Budgeter, Computer
Devices[1],
Hardware[1], Network
Components[1],
Software[1]
2.3 Project Budget
is developed 3 days Wed
11/1/17
Fri
11/3/17 11 Budgeter
2.4 Resources are
assigned 4 days Mon
11/6/17
Thu
11/9/17 12 Planner
2.5 Plan is
reviewed 2 days Fri
11/10/17
Mon
11/13/17 13 Project Manager
M2 Plan approval 0 days Mon
11/13/17
Mon
11/13/17 14
3 System
Designing 15 days Tue
11/14/17
Mon
12/4/17
3.1 Design Platform
is selected 2 days Tue
11/14/17
Wed
11/15/17 15 Designer
3.2
Appropriate
tools is used for
making design
7 days Thu
11/16/17
Fri
11/24/17 17 Designer, Design
Tools[1]
3.3 Design is
reviewed 1 day Mon
11/27/17
Mon
11/27/17 18 IT Engineer
M3 System Design
is approved 0 days Mon
12/4/17
Mon
12/4/17 32
4 System
Development 90 days Tue
12/5/17
Mon
4/9/18
4.1
Selecting
development
platform
3 days Tue
12/5/17
Thu
12/7/17 20 IT Engineer, Computer
Devices[1]
4.2
Building
database for the
system
10 days Fri
12/8/17
Thu
12/21/17 22 Database Admin,
Software[1]
4.3 Integration of
the database with
8 days Fri
12/29/17
Tue
1/9/18
31 Database Admin,
Network

existing data Components[1]
4.4
User interface
of the system is
developed
9 days Wed
1/10/18
Mon
1/22/18 24 Developer, Design
Tools[1]
4.5 Functions are
programmed 15 days Tue
1/30/18
Mon
2/19/18 33 Programmer, Computer
Devices[1]
4.6
Hardware
components are
integrated
12 days Tue
2/27/18
Wed
3/14/18 34 Developer, Computer
Devices[1],Hardware[1]
4.7
Application
program is
developed
13 days Thu
3/22/18
Mon
4/9/18 35 Programmer,
Software[1]
M4 System is
developed 0 days Mon
4/9/18
Mon
4/9/18 28
5 System Testing 95 days Tue
11/28/17
Mon
4/9/18
5.1 Prototype
Testing 5 days Fri
12/22/17
Thu
12/28/17 23 Tester, Testing Tools[1]
5.2 Design Testing 5 days Tue
11/28/17
Mon
12/4/17 19 Tester, Testing Tools[1]
5.3 Simulation
Testing 5 days Tue
1/23/18
Mon
1/29/18 25 Tester, Testing Tools[1]
5.4 White Box
Testing 5 days Tue
2/20/18
Mon
2/26/18 26 Tester, Testing Tools[1]
5.5 Black Box
Testing 5 days Thu
3/15/18
Wed
3/21/18 27 Tester, Testing Tools[1]
M5 Testing Results
are documented 0 days Mon
4/9/18
Mon
4/9/18 29
6
Final
Documentation
and Closure
7 days Tue
4/10/18
Wed
4/18/18
6.1
Making final
documents of the
project
4 days Tue
4/10/18
Fri
4/13/18 36 Documenter,
Documents[1]
6.2 Submission of
final documents 1 day Mon
4/16/18
Mon
4/16/18 38 Database Admin
6.3 Reviewing the
final documents 1 day Tue
4/17/18
Tue
4/17/18 39 Project Manager
6.4 Signing off 1 day Wed
4/18/18
Wed
4/18/18 40 Project Manager
M6 Project is closed 0 days Wed
4/18/18
Wed
4/18/18 41
The Gantt chart for the project is given below,

ID Task
Mode
WBS Task Name Duration Start Finish
0 0 RALS Ticketing System Development 143 days Mon 10/2/17 Wed 4/18/18
1 1 Project initialization 15 days Mon 10/2/17 Fri 10/20/17
2 1.1 Analysis of the requirements 3 days Mon 10/2/17 Wed 10/4/17
3 1.2 Development of project intiation documents 5 days Thu 10/5/17 Wed 10/11/17
4 1.3 Project Charter document is made 4 days Thu 10/12/17 Tue 10/17/17
5 1.4 Project Kick off meeting 1 day Wed 10/18/17 Wed 10/18/17
6 1.5 Submission of charter 1 day Thu 10/19/17 Thu 10/19/17
7 1.6 Reviewing of the charter document 1 day Fri 10/20/17 Fri 10/20/17
8 M1 Charter Approval 0 days Fri 10/20/17 Fri 10/20/17
9 2 Project Planning 16 days Mon 10/23/17 Mon 11/13/17
10 2.1 Selection of plan outline 2 days Mon 10/23/17 Tue 10/24/17
11 2.2 Resources are accumulated 5 days Wed 10/25/17 Tue 10/31/17
12 2.3 Project Budget is developed 3 days Wed 11/1/17 Fri 11/3/17
13 2.4 Resources are assigned 4 days Mon 11/6/17 Thu 11/9/17
14 2.5 Plan is reviewed 2 days Fri 11/10/17 Mon 11/13/17
15 M2 Plan approval 0 days Mon 11/13/17 Mon 11/13/17
16 3 System Designing 15 days Tue 11/14/17 Mon 12/4/17
17 3.1 Design Platform is selected 2 days Tue 11/14/17 Wed 11/15/17
18 3.2 Appropriate tools is used for making design 7 days Thu 11/16/17 Fri 11/24/17
19 3.3 Design is reviewed 1 day Mon 11/27/17 Mon 11/27/17
20 M3 System Design is approved 0 days Mon 12/4/17 Mon 12/4/17
21 4 System Development 90 days Tue 12/5/17 Mon 4/9/18
22 4.1 Selecting development platform 3 days Tue 12/5/17 Thu 12/7/17
23 4.2 Building database for the system 10 days Fri 12/8/17 Thu 12/21/17
24 4.3 Integration of the database with existing data 8 days Fri 12/29/17 Tue 1/9/18
25 4.4 User interface of the system is developed 9 days Wed 1/10/18 Mon 1/22/18
26 4.5 Functions are programmed 15 days Tue 1/30/18 Mon 2/19/18
27 4.6 Hardware components are integrated 12 days Tue 2/27/18 Wed 3/14/18
28 4.7 Application program is developed 13 days Thu 3/22/18 Mon 4/9/18
29 M4 System is developed 0 days Mon 4/9/18 Mon 4/9/18
30 5 System Testing 95 days Tue 11/28/17 Mon 4/9/18
31 5.1 Prototype Testing 5 days Fri 12/22/17 Thu 12/28/17
32 5.2 Design Testing 5 days Tue 11/28/17 Mon 12/4/17
33 5.3 Simulation Testing 5 days Tue 1/23/18 Mon 1/29/18
34 5.4 White Box Testing 5 days Tue 2/20/18 Mon 2/26/18
35 5.5 Black Box Testing 5 days Thu 3/15/18 Wed 3/21/18
36 M5 Testing Results are documented 0 days Mon 4/9/18 Mon 4/9/18
37 6 Final Documentation and Closure 7 days Tue 4/10/18 Wed 4/18/18
38 6.1 Making final documents of the project 4 days Tue 4/10/18 Fri 4/13/18
39 6.2 Submission of final documents 1 day Mon 4/16/18 Mon 4/16/18
40 6.3 Reviewing the final documents 1 day Tue 4/17/18 Tue 4/17/18
41 6.4 Signing off 1 day Wed 4/18/18 Wed 4/18/18
42 M6 Project is closed 0 days Wed 4/18/18 Wed 4/18/18
Analyst
Documenter,Documents[1]
Documenter,Documents[1]
Project Manager
Documenter
Project Manager
10/20
Planner
Budgeter,Computer Devices[1],Hardware[1],Network Components[1],Software[1]
Budgeter
Planner
Project Manager
11/13
Designer
Designer,Design Tools[1]
IT Engineer
12/4
IT Engineer,Computer Devices[1]
Database Admin,Software[1]
Database Admin,Network Components[1]
Developer,Design Tools[1]
Programmer,Computer Devices[1]
Developer,Computer Devices[1],Hardware[1]
Programmer,Software[1]
4/ 9
Tester,Testing Tools[1]
Tester,Testing Tools[1]
Tester,Testing Tools[1]
Tester,Testing Tools[1]
Tester,Testing Tools[1]
4/ 9
Documenter,Documents[1]
Database Admin
Project Manager
Project Manager
4/ 18
S T M F T S W S T M F T S W S T M F T S W S T M F
Sep 24, '17 Oct 22, '17 Nov 19, '17 Dec 17, '17 Jan 14, '18 Feb 11, '18 Mar 11, '18 Apr 8, '18 May 6, '18 Jun 3, '18
The work breakdown structure for the project is given below,
0 - RALS Ticketing System
Development
1 - Project initialization
1.1 - Analysis of the
requirements
1.2 - Development of project
intiation documents
1.3 - Project Charter
document is made
1.4 - Project Kick off meeting
1.5 - Submission of charter
1.6 - Reviewing of the
charter document
M1 - Charter Approval
2 - Project Planning
2.1 - Selection of plan outline
2.2 - Resources are
accumulated
2.3 - Project Budget is
developed
2.4 - Resources are assigned
2.5 - Plan is reviewed
M2 - Plan approval
3 - System Designing
3.1 - Design Platform is
selected
3.2 - Appropriate tools is
used for making design
3.3 - Design is reviewed
M3 - System Design is
approved
4 - System Development
4.1 - Selecting development
platform
4.2 - Building database for
the system
4.3 - Integration of the
database with existing
data
4.4 - User interface of the
system is developed
4.5 - Functions are
programmed
4.6 - Hardware components
are integrated
4.7 - Application program is
developed
M4 - System is developed
5 - System Testing
5.1 - Prototype Testing
5.2 - Design Testing
5.3 - Simulation Testing
5.4 - White Box Testing
5.5 - Black Box Testing
M5 - Testing Results are
documented
6 - Final Documentation
and Closure
6.1 - Making final documents
of the project
6.2 - Submission of final
documents
6.3 - Reviewing the final
documents
6.4 - Signing off
M6 - Project is closed

4. Part Four: Risk Management Plan
No. REF001 REF003 REF03 REF004 REF005
Rank 1st 2nd 3rd 4th 5th
Risk System Failure Over
budgeting
Design flaws Management
Issue
Delay in
completion
Descriptio
n
The system
failure can be
resulted from
the
development
of the simple
issues and
problems
while
conveying the
operations of
the
organization.
The
framework
disappointmen
t can be come
about because
of the
improvement
of the basic
issues and
issues while
passing on the
operations of
the
association.
The over
budgeting is
a nominal
flaw that has
caused the
excess
resource
depletion
that might
result in
forming the
issues of
completing
the project in
the estimated
budget. The
over
planning is
an ostensible
blemish that
have caused
the
abundance
asset
exhaustion
that may
bring about
framing the
issues of
finishing the
undertaking
in the
evaluated
spending
plan.
The flaws of
the deisgn of
the system
are a result
of lack of
using the
design
principles
and it would
form the
major
impact for
making the
project
unsuccessful
. The defects
of the
outline of
the
framework
are an after
effect of
absence of
utilizing the
plan
standards
and it would
shape the
significant
effect for
making the
undertaking
unsuccessful
.
The
development
of the project
plan can face
the lack of
the
governance
and it would
tend to result
in forming
the issues of
the
management
of the
operations.
The
advancement
of the task
design can
confront the
absence of
the
administratio
n and it
would tend to
bring about
framing the
issues of the
administratio
n of the
operations.
Delay in
completion is
on of the most
common issue
in the project
as it would be
raised by
several factors
including
technical,
operational,
documentatio
n and external
influence
issues.
Deferral in
culmination is
on of the most
widely
recognized
issue in the
undertaking
as it would be
raised by a
few elements
including
specialized,
operational,
documentatio
n and outer
impact issues.
Category Technical Financial Technical Operational Performance
Triggers Flaws in
system
Lack of
Adequate
Resources
Absence of
Design
Methodolog
y
Lack of
Management
Approach
The project
would tend to
form the
development
of the issues
in successful

completion of
the project
operations
Potential
Responses
Earlier testing
of the
framework
before
execution
Advancemen
t 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
Methodolog
y
System
Failure
Almost
Certain
Delay in
completion
5. Part Five: Quality Management Plan
The quality management plan is implied for developing the smarter processing of the
information for developing the use of the effective quality management plan for
implementing the project of RALS Ticketing System Development.
 A set of verification activities: The use of the quality assessment would be
helpful for the development of the improvement activities for ensuring the
use of the integrated project development.
 A set of validation activities: The quality matrix and strategy development
would be helpful for forming the operations of the organization

Part Six: Closure and Evaluation
a. Annotated Bibliography
1st Article “Simulation-based fuzzy logic approach to assessing the effect of project
quality management on construction performance”
In screening projects a portion of the criteria are utilized to rank the request of the
degrees. This incorporates the cost-viability of the time and cost investment funds of
the whole bundle of the measures (Corona-Suárez et al., 2014). This incorporates the
net present esteem, inner rate of return, income and the normal payback. At that point
there is the manageability of the funds on the life of that hardware. At that point there
is the simplicity of checking, evaluating and confirmation of the time and cost reserve
funds. Next there is the assurance of the innovation and the simplicity to adjust of the
innovation to the encompassing condition. In conclusion the natural and the social
money saving advantages are to be resolved.
2nd Article “Seven Quality Tools | ASQ Toronto Section 402”
The project administration has guaranteed that the Internet has ended up being the
appropriate, omnipresent medium to help the applications. It has been guaranteeing
that the exchanges have been happening typically and viably. The buyers ought to
likewise have the capacity to discover the provenance and nature of the information
they get from Internet (Asqtoronto.org). The Internet has been supporting expansive
scope of utilizations. It organize abilities are required to help the application and
mirror the particular attributes of the earth. The accessibility and the security have
been the unpredictable specialized necessities with respect to the Internet applications.
3rd Article “Integrating safety, environmental and quality risks for project
management using a FMEA method”
The portrayal has been the general way to deal with execute the new system. It Hs
been the sending approach or the portrayal of the whole arrangement system (Zeng,

Tam & Tam, 2015). This has been the progress methodology or the depiction of the
technique perceiving the present correspondences organize and the proposing the
system to the change the customers from the present system to the new systems. At
that point there is the progress technique. This has been the depiction of the technique
of the present correspondence arrange and recommending the methodology to change
of the client from the present system to the new systems. The following one is the
cost\benefit investigation
b. Develop a closure checklist: The closure checklist is given below,
Task Name Completed
Development of project initiation documents 
Project Charter document is made 
Project Budget is developed 
Plan is reviewed 
System Design is approved 
User interface of the system is developed 
Hardware components are integrated 
Functions are programmed 
Application program is developed 
Testing Results are documented 
Making final documents of the project 
c. Develop a project evaluation: The use of the various documents like stakeholder
management, project analysis of progress and risk management would be helpful for
evaluation of the project.
Bibliography

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.
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.
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.
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.
Levin, G. (2014). Project Quality Management: Why, What and How. Project Management
Journal, 45(5).

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.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Asqtoronto.org., (2017). Seven Quality Tools | ASQ Toronto Section 402. Retrieved 9
September 2017, from http://asqtoronto.org/resources/quality-tools/seven-quality-
tools/
Wagner, C., Groene, O., DerSarkissian, M., Thompson, C. A., Klazinga, N. S., Arah, O.
A., ... & DUQuE Project Consortium. (2014). The use of on-site visits to assess
compliance and implementation of quality management at hospital level. International
Journal for Quality in Health Care, 26(suppl_1), 27-35.
Wagner, C., Groene, O., Thompson, C. A., Dersarkissian, M., Klazinga, N. S., Arah, O. A., ...
& Lombarts, K. (2014). DUQuE quality management measures: associations between
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).