1. IntroductionQuality: the degree to which a set of inherentcharacteristics satisfies the stated or implied needs of the customer.
Tomeasure quality successfully, it is necessary to turn implied needs into statedneeds via project scope management.TheQuality management plan focuses on defining the objcetives for quality, howthey will be applied and how they will be meaasured. Quality can planned in to each process andcontrolled along the way, or it can verified and validated in the end. The implementation of quality within theproject will cost time and money.
Quality is the fourth component the the triple constraint of Cost, Timeand Scope, as any one of these change, so do the others, all of which impactquality. 2. Scope This SQPfor ERP projects under Technical Department responsibility in zoo Businesssolution. 2.
1 Structure 2.2 Quality Stander 2.3 Methodology We use Scrum agile developmentmethodology in development lifecycle 2.4 Roles & Responsibilities2.4.1 Product Owner2.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. 220.127.116.11 Defines anddocuments customer business functions and processes. 2.
4.1.3 Participates in useracceptance testing and testing of new system functionality. 2.
4.1.4 Planning, estimatingand retrospective across development sprints. 2.
4.1.5 Maintain technical& Functional record keeping 2.4.
1.6 Use analyticalskills to resolve business issues 2.4.2 Scrum Master18.104.22.168 Prepare scrumtasks and divided it to developers2.4.
2.2 Developthe requirement specification and cost estimation for the project22.214.171.124 Developthe design plan and test plan for testing 126.96.36.199 Planning,coordinating, testing and assessing all aspects of quality issues.
2.4.3 Development Team2.4.
4 Quality Team188.8.131.52 Defines qualitystandards to be followed by writing a quality assurance plan184.108.40.206 Manages the proofreading of all documents.
220.127.116.11 Is responsible forwriting the Software Test Plan (TP).2.
4.4.4 Manages the processof testing by delegating tests to team members.18.104.22.168 Documents all teststhat are carried out.2.
4.4.6 Organizes usabilitytest, this includes gathering test group and preparation22.214.171.124 Classifies eventualusability errors and together with GUI designer suggests improvement to GUI 3.
Qualityin Requirement Gathering Phase 3.1 QA inRequirement gathering 3.1.1 To ensure that requirement are specified objectively andshould provide criteria for validation3.1.2 To ensurethat requirements specifications are easily understandable not only byrequirements analysts but also other stakeholders, including softwaredesigners, users, and end users.
3.2 Quality Activity inRequirement gathering phase3.3 QC in Requirement gatheringPhase 4. Qualityin Development phase4.1 QA In development phase4.1.1 Good use ofdescriptive comments for all methods and relevant variables.4.
1.2 Variables and methodnames should be chosen that are short, unique and descriptive. 4.1.
3 All code should bewritten in English.4.2 Quality activity in developmentphase5. Qualityin Testing Phase5.1 QA In testing Phase5.
2 Quality activity in testing Phase6. QualityControl for the software7.