QUALITY ASSURANCE
Download as PPTX, PDF•1 like•268 views
This document outlines the quality assurance processes at Quanteq Enterprise Solutions (QES). It begins with an overview of quality assurance and its importance in ensuring organizational policies and standards are implemented. The document then reviews QES's quality assurance model which consists of 8 processes from business development through project completion. Key processes include requirement gathering, proposing solutions, system analysis, building and testing, and training. The model aims to continually improve processes to meet standards and customer satisfaction.
QUALITY ASSURANCE
- 2. DEMING CYCLE: PDCA SIX SIGMA: REDUCE ERRORS, BY ELIMINATING WASTE 99.99999% MODEL CYCLE: Essentially all models are wrong, but some are useful
- 3. 1. To UNDERSTAND the meaning of Quality Assurance 2. To KNOW the importance of Quality Assurance 3. To REVIEW the Quality Assurance processes in QES 4. To ADOPT a Quality Assurance Model
- 4. What is Quality Assurance (QA)? QA is an organisation’s guarantee that the product or services it offers meets the accepted quality standards. It is achieved by identifying what “quality” means in context; specifying methods by which its presence can be measured to ensure conformance.
- 5. Why Quality Assurance (QA)? QA is imperative in every organisation, because its ensures that organizational policies and standards are strictly adhered and implemented in every process, product, and services, to ensure that only the best results are achieved. Some of the importance of QA are:
- 6. No.1 It creates an opportunity to monitor and to continually improve the development process until the final product simultaneously meets the development firm and the customer’s standards.
- 7. No. 2 QA is crucial to making sure that standards and procedures are followed
- 8. No. 3 To ensure the founding problems are fixed.
- 9. No. 4 It will improve customer satisfaction.
- 10. A Review of QA In Quanteq Enterprise Solutions
- 11. Start Business Development Requirement Gathering Yes/No Implement Needs Assessment End Profile Organization Marketing Event, Business Analysis Propose Solution Get approval for client site visitation Get Project Award Letter System Analysis Building & Testing Approved/ Disapproved Training/ Support Yes Approved Disapproved NO Yes/ No YES NO Blueprint Design
- 12. KEY DESCRIPTION A Business idea is initiated, and the steps to achieve it commences Major business/ project process activities. Sub-business/ project process activities Documents obtained at various stages of the process Decisions determining whether the project can proceed or terminate Blueprint Design End of business process Start Blueprint Design Yes/ No End
- 13. PROCESS NAME BUSINESS DEVELOPMENT AND PROJECT MANAGEMENT PROCESS DESCRIPTION The complete process for business development, through needs assessment up till project award, development and deployment for QES. TOTAL NUMBER OF PROCESSES 8 DEPARTMENT QUANTEQ ENTERPRISE SOLUTIONS (QES)
- 14. PROCESS LABEL DESCRIPTION BUSINESS DEVELOPMENT A meeting is conducted in the practice on how to develop business; the Practice head and business development team meet and plan on various ways to get clients, or meet with organizations. PROCESS RECIPIENT Practice Heads and Business Development Team DURATION 3 weeks – 1 month period for planning for, and organizing INPUT Business development team Financial resources Documentation Invited guests of organizations ACTION Marketing Events One-on-one Profiling Organizations OUTPUT Established contact within an organization Letter of Approval for client site visitation DECISION If the above action is successfully established, the organization may approve a client site visitation or disapprove of it.
- 15. REQUIREMENT GATHERING IT Strategic Planning PROCESS RECIPIENT Business Analyst, Business Developers, Client DURATION 2 weeks – 1 month period INPUT Business Analyst, Business Developers, Stakeholders Questionnaires One-on-one ACTION Needs Assessment Gap Analysis OUTPUT IT requirements document Proposal Document
- 16. PROPOSE SOLUTION With the information gathered during the IT strategic planning, the BD team writes a proposal to the organization, stating their IT needs. PROCESS RECIPIENT Business and Systems Analysis DURATION 1 week INPUT Business Analyst and Systems Analyst of ESG ACTION Draft a proposal letter to organization stating findings and best solutions to achieve client organizational objectives/ goals. Meet with stakeholder of the organization to conduct an analysis of clients needs. OUTPUT Proposal Document Business Requirement Document Service Level Agreement (SLA) Project Award Letter DECISION If the proposal is accepted, the client approves for a Business Analysis of the solution and a Project Award Letter is issued; If rejected, the team goes back to review their findings.
- 17. SYSTEM ANALYSIS With the project awarded, roles and responsibilities are assigned to various teams that are set up. The Infrastructure specialist receives the Business Requirement Document and commence work. He designs a blueprint document, mapping out the design of the project. PROCESS RECIPIENT Infrastructure Specialist DURATION 3 – 4 weeks INPUT Infrastructure Specialist Team leads ACTION Infrastructure Specialist reviews Business Requirement Document Project is planned, teams are set up Roles and Responsibilities are assigned to various teams Design blueprint document OUTPUT Project Blueprint Design
- 18. BUILDING AND TESTING With the blueprint design as a guide, a team of infrastructure personnel commence work on building the project. PROCESS RECIPIENT IT Infrastructure team DURATION 3 months – 1 year, depending on the project INPUT IT Infrastructure team Materials needed for building the project ACTION Building the solution Testing OUTPUT Completed project DECISION If the solution is tested and working fine, the client approves it to be implemented; otherwise, it is rejected and the Infrastructure team goes back to review the Blueprint design, and correct their lapses.
- 19. IMPLEMENTATION With the approval for deployment, the IT team proceeds to implement the designed solution at client site. PROCESS RECIPIENT Client INPUT Project Team ACTION Client Check Sign Off
- 20. TRAINING/SUPPORT After the project has been implemented, the client staff or IT personnels are trained on how to use the solution. INPUT Trainers Staff of the organization Training manuals DURATION 1 – 2 weeks ACTION Training of staff on usage of solution, and how it works. Send support staff to client location (if stated in SLA) Documentation of lessons learnt. OUTPUT Knowledge gained Certificate of Project Completion END End of business development