1. We use Scrum agile development methodology in development

1.    
Introduction

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.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

The
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
quality. 

2.    
Scope

This SQP
for ERP projects under Technical Department responsibility in zoo Business
solution.

 

2.1  
Structure

 

 

 

 

 

 

2.2  
Quality Stander

 

2.3  
Methodology

We use Scrum agile development
methodology in development lifecycle

 

2.4  
Roles & Responsibilities

2.4.1       
Product Owner

2.4.1.1               
Elicit requirements
(user story) using interviews, document analysis, requirements workshops,
surveys, site visits, business process descriptions, use cases, scenarios,
business analysis, task and workflow analysis.

2.4.1.2               
Defines and
documents customer business functions and processes.

2.4.1.3               
Participates in user
acceptance testing and testing of new system functionality.

2.4.1.4               
Planning, estimating
and retrospective across development sprints.

2.4.1.5               
Maintain technical
& Functional record keeping

2.4.1.6               
Use analytical
skills to resolve business issues

 

2.4.2       
Scrum Master

2.4.2.1               
Prepare scrum
tasks and divided it to developers

2.4.2.2               
Develop
the requirement specification and cost estimation for the project

2.4.2.3               
Develop
the design plan and test plan for testing

2.4.2.4               
Planning,
coordinating, testing and assessing all aspects of quality issues.

2.4.3       
Development Team

2.4.4       
Quality Team

2.4.4.1               
Defines quality
standards to be followed by writing a quality assurance plan

2.4.4.2               
Manages the proof
reading of all documents.

2.4.4.3               
Is responsible for
writing the Software Test Plan (TP).

2.4.4.4               
Manages the process
of testing by delegating tests to team members.

2.4.4.5               
Documents all tests
that are carried out.

2.4.4.6               
Organizes usability
test, this includes gathering test group and preparation

2.4.4.7               
Classifies eventual
usability errors and together with GUI designer suggests improvement to GUI

 

 

 

 

 

 

 

3.      Quality
in Requirement Gathering Phase

3.1   QA in
Requirement gathering

3.1.1       
To ensure  that requirement are specified objectively and
should provide criteria for validation

3.1.2       
To ensure
that requirements specifications are easily understandable not only by
requirements analysts but also other stakeholders, including software
designers, users, and end users.

3.2  
Quality Activity in
Requirement gathering phase

3.3  
QC in Requirement gathering
Phase

 

4.     Quality
in Development phase

4.1  
QA In development phase

4.1.1       
Good use of
descriptive comments for all methods and relevant variables.

4.1.2       
Variables and method
names should be chosen that are short, unique and descriptive.

4.1.3       
All code should be
written in English.

4.2  
Quality activity in development
phase

5.     Quality
in Testing Phase

5.1  
QA In testing Phase

5.2  
Quality activity in testing Phase

6.     Quality
Control for the software

7.