Subsidiary Management Plan Project 2022

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