Quality: the degree to which a set of inherent
characteristics satisfies the stated or implied needs of the customer. To
measure quality successfully, it is necessary to turn implied needs into stated
needs via project scope management.
Quality management plan focuses on defining the objcetives for quality, how
they will be applied and how they will be meaasured. Quality can planned in to each process and
controlled along the way, or it can verified and validated in the end. The implementation of quality within the
project will cost time and money.
Quality is the fourth component the the triple constraint of Cost, Time
and Scope, as any one of these change, so do the others, all of which impact
for ERP projects under Technical Department responsibility in zoo Business
We use Scrum agile development
methodology in development lifecycle
Roles & Responsibilities
(user story) using interviews, document analysis, requirements workshops,
surveys, site visits, business process descriptions, use cases, scenarios,
business analysis, task and workflow analysis.
documents customer business functions and processes.
Participates in user
acceptance testing and testing of new system functionality.
and retrospective across development sprints.
& Functional record keeping
skills to resolve business issues
tasks and divided it to developers
the requirement specification and cost estimation for the project
the design plan and test plan for testing
coordinating, testing and assessing all aspects of quality issues.
standards to be followed by writing a quality assurance plan
Manages the proof
reading of all documents.
Is responsible for
writing the Software Test Plan (TP).
Manages the process
of testing by delegating tests to team members.
Documents all tests
that are carried out.
test, this includes gathering test group and preparation
usability errors and together with GUI designer suggests improvement to GUI
in Requirement Gathering Phase
3.1 QA in
To ensure that requirement are specified objectively and
should provide criteria for validation
that requirements specifications are easily understandable not only by
requirements analysts but also other stakeholders, including software
designers, users, and end users.
Quality Activity in
Requirement gathering phase
QC in Requirement gathering
in Development phase
QA In development phase
Good use of
descriptive comments for all methods and relevant variables.
Variables and method
names should be chosen that are short, unique and descriptive.
All code should be
written in English.
Quality activity in development
in Testing Phase
QA In testing Phase
Quality activity in testing Phase
Control for the software