Project Management: Quality Control Process and Tools Report

This report delves into the intricacies of project management, specifically focusing on quality control within the context of a billing system software development project. The report begins by outlining a subsidiary management plan and a comprehensive project quality control plan, detailing processes such as payment, calls, subscription fees, legacy system integration, and software testing. Each process is meticulously examined, including its frequency, sovereignty, and relevant standard operating procedures (SOPs). The report further elaborates on the quality control process, highlighting the importance of modules like payment, calls, adjustments, and subscriptions, and how they are integrated into the quality assurance framework. Additionally, it explores various data representation tools and techniques used in quality control, such as cause and effect diagrams, flowcharts, histograms, run charts, scatter diagrams, statistical sampling, and inspection methods. The report concludes with a control to closure flow diagram and references supporting the analysis.

Running head: PROJECT MANAGEMENT 1
PROJECT MANAGEMENT
[Author Name(s), First M. Last, Omit Titles and Degrees]
[Institutional Affiliation(s)]
Author Note
[Include any grant/funding information and a complete correspondence address.]

Running head: PROJECT MANAGEMENT 2
Subsidiary management plan
Project management plan represent a formal and approved documentation that defines
how the given project shall be executed and to some extends defines how the project shall be
monitored. The lack of adoption of standard control quality plans have hampered the success of
several projects are the end product normally don’t meet the client needs (Stępień, 2015).
This project quality control plan is detailed below.
Process
#
Process
Name
Frequen
cy of
occuren
ce.
Sovereignty Measure of
control.
Relevant SOP
documentation
1 Payment
This is key
process for
billing to
ensure the
user are
billed
accordingly.
Daily High -The system shell
integrate mobile
payment options
to control the
billing process
from user
perspective
-Billing shall be
done after
successful user
login into the app
-All legacy
system data shall
be quality
checked against
the current data
to ensure low
tolerance to
defects
-Billing SOP
-Payment Change
management
2 Calls
The Online
billing
system shell
integrate
with
proposed
telecommun
Daily High -Calls shall be
delivered through
the circuit
switching
network to
ensure reliability
-All current call
exchanges shall
-User support SOP

Running head: PROJECT MANAGEMENT 3
ication
infrastructur
e to ensure
high quality
of calls are
made.
be integrated
with the state of
the art
infrastructure
envisioned by the
project
3 Subscriptio
n Fee.
This process
involves the
realignment
of the
current
subscription
models to fit
into the
billing
system
Daily Medium -all subscriptions
shall be done via
secure login form
-All none
successful login
must be below
five attempts
—
subscription SOP
—
4 Legacy
system
integration.
The planned
telecom
system must
be backward
comparable
with the
existing
legacy
systems to
ensure
continued
service
delivery
without
much data
format
interchange
Once High -Test the billing
against the old
and new systems
-All
discrepancies
shall be corrected
at testing phase
—
System integration
SOP.
5 Software
testing;
This process
On
going
High -Unit test shall be
done for each
module by
-Software Testing SOP

Running head: PROJECT MANAGEMENT 4
is key to
ensure there
is quality
control
checks done
independent
testing team
-All integration
tests shall be
done by in
depended testing
team
-The full system
test shall be done
with independent
est team in
collaboration
with the
development
team
-The user
acceptance hence
shall be done
before sign off to
ensure quality
control check are
all deal with
before client
acceptance
This plan shall be the blue print upon which all the key quality checks are adhered with
Quality Control Process
The above control plan is laid out in the following plan

Running head: PROJECT MANAGEMENT 5
From the process diagram, the following key processes in the software development for the
billing system shall be entailed;
Payment module
This module is key hence must be properly tested and quality checked against the payment SOP
developed by the company. The key quality checks and control in this module includes
validating and verifying the accuracy and relevancy of the billing module.
Calls
The client deals with payment hence must have a well elaborate support system that must include
a high quality call center integration with the app.
Adjustments
This module shall be invoked when there is need to adjust the billing details. It is therefore vital
to include it in the quality control process so that the developers can have it thorough tested
during unit, integration and full product test.

Running head: PROJECT MANAGEMENT 6
Subscriptions
The software under development needs to have a quality checks done into the various
subscription models that the client has in their SOP. Using such model, the developer can use the
subscription module to improve the software quality of the end product by continue testing the
subscription functionality.
Data representation tools.
The following represents some techniques and tools used in data representation for quality
control processes
● Cause and Effect Diagrams
● Flow-Charting
● Control Charts.
● Histogram
● Run Charts.
● Scatter Diagrams
● Statistical Sampling
● Inspection
They are explained below.
Cause and Effect
This tool helps the project manager think through the causes of the problem by going deep into
the root causes (Orosa García, 2012)

Running head: PROJECT MANAGEMENT 7
Flow charting
The flow chart is a quality control tool that ensure non value processes are identified earlier and
corrective measure given. This is possible by the visual aid of the control charts (Cotrim, Filho,
Leal, & Galdamez, 2018).

Running head: PROJECT MANAGEMENT 8
Histogram
Histogram is a simple but powerful tool for continuous process improvement by aiding
the visualization of collected data (Basu, 2013).
Run charts.

Running head: PROJECT MANAGEMENT 9
Used to ensure their is trend analysis after a given quality metrics have been affected
(Trentim, 2013).
Scatter Diagrams.
This quality improvement tools is useful when manager wants to know whether some
variables have some correlation
Statistical sampling
This technique is used in quality control by taking part of the population for careful
inspection according to the quality management plan
Inspection
Used to check the level of compliance of a given process to the set standards.
Control Chart
Schedule Performance Index
80/20 rule chart

Running head: PROJECT MANAGEMENT 10
From the 80/20 rule chart, it is vital to fix the Skills gap problems to realize more quality
Control to closure flow diagram
The diagram below summarizes the control flow to closure

Running head: PROJECT MANAGEMENT 11
References
Basu, R. (2013). Managing Quality in Projects. Burlington, VT: Routledge.
Cotrim, S. L., Filho, D. A. M., Leal, G. C. L., & Galdamez, E. V. C. (2018). Implementation of
cleaner production along with quality management tools. International Journal of
Technology Management & Sustainable Development, 17(1), 65–85.
https://doi.org/10.1386/tmsd.17.1.65_1
Orosa García, J. A. (2012). Quality Control : Developments, Methods and Applications. New
York: Nova Science Publishers, Inc.
Stępień, K. (2015). Measurement and Quality Control of Processes and Products in
Manufacturing and Enterprise. Pfäffikon, Zurich, Switzerland: Trans Tech Publications.
Trentim, M. H. (2013). Managing Stakeholders As Clients : Sponsorship, Partnership,
Leadership, and Citizenship. Newtown Square, Pa: Project Management Institute.