Certified Software Quality Manager (CSQM)
PurposeThe purpose of the CSQM certification is to help establish and advance the field of software quality management as a discipline independent of the field of software testing. Individuals pursuing Software Quality Management as a career will focus on method and techniques to manage product and process quality in software organizations. It is expected of those individuals to have a very broad range of knowledge with all software processes and ways to improve these processes. The CSQM certification is a natural progression for individuals who have achieved the Certified Test Management Certification to advance their career and be prepared to climb the corporate ladder to occupy higher positions.
Objectives of the CSQM CertificationSoftware Quality is a very broad concept. To achieve software quality, one must focus on the quality of the software product as well as the quality of the different processes used to produce the software product. In order to achieve this goal, a person in charge of improving quality in a software organization has certain responsibilities and objectives. The CSQM Certification provides the knowledge to help a Software Quality Manager carry out these responsibilities and achieve his or her objectives.
- Evaluating, developing, and monitoring
- Processes (for development, testing, inspection, CM, etc.)
- Product and process standards
- Measurements
- Evaluating and selecting tools
- Assessing the organization's capability
- Facilitating process improvement issues between groups or projects
- Assessing the impact of one process improvement effort on another process or another part of the process
- Publicizing success stories
- Acting as a consultant to projects having special problems or requirements
- Any person who has worked in software testing for at least 3 years
- People with a management or leadership role in testing
- Development managers and development leads who wish to move to a test management or lead position
- Auditors, inspectors, and others who must evaluate the work product of the testing process
Two requirements must be satisfied before the CSQM certification can be granted. These are the Formal Education Requirements and Job Experience Requirements
Formal Education RequirementsTen days of instructor-led training to cover all ten area of the Software Quality Management Body of Knowledge (SQMBOK). One day to cover each area.
CSQM Training Options Written Exam:Candidates are required to complete a written exam for each course and pass with a level of performance no less than 80%. For courses conducted by IIST, a candidate is allowed to retake the exam for a second time without having to attend the course again. There is a $100 fee for retakes. If 80% performance is not achieved on a second attempt, the candidate must retake the course or take another course covering the same BOK area. If the course failed was taken online you will get access to the online course and a retake exam for $100. If the course was taken on-site or at public training and is available online you can get access to both the online course and retake exam for half the original price of the online course. If the course is failed for a 3rd time and was taken online you will get access to the online course and a retake exam for half the original price of the online course.
Job Experience RequirementsIn order for the CSQM certification to be granted, a candidate must have a total of at least three years working in software projects, including 1 year in a lead or management position. This requirement must be completed by the time CSQM is granted. This requirement shall be met by means of a letter of support describing the candidate's specific role and responsibilities over a period of three years or more. The letter must be authored and signed by any of the following:
- The candidate's current or former supervisor/manager
- The candidate's client or customer (if self-employed)
- A co-worker currently holding a CSQM certification who has worked with the candidate on a project.
- Multiple sources may be submitted to cover the three year period. Any variation from this requirement must be reviewed and approved by the IIST Chairperson.
Upon satisfying both formal education and job experience requirements, a candidate shall submit an application to the IIST Chairperson for the certification to be granted. Application forms can be obtained here. The application must be accompanied by payment of the $180 non- refundable graduation fee. This fee covers the cost associated with record-keeping, grading exams, and certification plaque. Please note there will be an additional $100 for shipping plaques outside the U.S.
CSQM Re-Certification RequirementsThe CSQM Certification will expire 3 years after it is granted. As a result, all CSQM recipients must complete the re-certification requirements before that time. The re-certification requirements are TEN days of training to cover any topic in software quality, software testing, software engineering or soft skills that the candidate feels will help develop more skills in quality management. Training for re-certification can be from IIST or any other training provider. Non-IIST courses must be approved by the IIST Chairperson. There is a $50 course review fee. No exams are required for courses to be considered for CSQM re-certification.
Software Quality Management Body of Knowledge (SQMBOK)- Software Quality defined
- Software Quality Assurance and Testing defined and distinguished
- The difference between QC&QA
- The Software Quality Puzzle
- The Software Quality Assurance function
- The role of Software Quality Manager
- Skill set of a Software Quality Manager
- Managing Software Quality Throughout the Lifecycle
- Requirement Management and Engineering
- Change Control and Release Management
- Assuring quality during development
- Best Practices in Software Testing
- Best practices in Software Inspections and Reviews
- Defect Tracking and Reporting
- Defect Prevention
- Process Improvement Models (CMMI, SIX Sigma)
- Lean Software Process
- Traditional SDLC
- Agile development
- Incremental delivery
- Methods for determining and documenting the architecture and design (high-level and detailed) for software products
- Methods and activities associated with the release and installation of software systems
- Activities associated with supporting and maintaining software products
- Change control and management
- Activities involved in choosing, contracting with, and assuring the performance of software suppliers (both those who provide commercial off-the-shelf COTS products, and those that do custom development)
- Risk analysis methodologies
- Risk identification and classification
- Risk prioritizations and ranking
- Calculating costs and probability
- Risk reporting
- Monitoring and controlling risks
- Contingency planning and mitigation
- Purpose of Measurement
- Principles of Measurement
- Measurement Process Model and Framework
- Multilevel Measurements
- Organizational Level Measurements
- Project Level Measurements
- Choosing the best measures for your organization
- Align measurements with information needs
- Specify measures
- Specify data collection and storage
- Specify analysis
- Specify reporting, communications, and feedback
- Goal/Question/Metric Paradigm
- A set of 'Best Practices' measurements, used by SQA staffs, with examples and Case Studies
- All activities related to establishing an SQA group
- Stakeholder Identification
- Developing SQA plan
- Establish Budget
- Establish Personnel
- Establish Mission/Objectives
- Selling SQA to Management
- Demonstrating ROI for SQA efforts
- Base lining current software quality levels and Cost of Quality
- Defining standards, procedures, methodologies, best practices and guidelines
- Instituting metrics and measurements
- Deploying processes
- Evaluating Methodologies and Automated Tools
- Implementing Defect Studies
- Principles and activities of the Discipline of Software Configuration Management
- Identifying configuration items
- Establishing baselines
- Controlling change
- Establishing and maintaining repositories
- Assuring the integrity of software work products
- Defining and validating requirements
- Quality Requirements Vs Functional Requirements
- Quality Requirements for different types of systems
- Managing and maintaining requirements
- Building a Requirement-Management Process
- Requirement Traceability
- Requirement Change Control
- Verification and Validation Defined
- Unit, integration, System, and User Acceptance Testing including planning and design activities of each
- Inspections and other forms of peer reviews
- Forms of Inspections and Reviews
- Effective and practical inspections practices
- Code Analysis
- Independent V&V
- Activities associated with planning projects including size, effort and cost estimation, schedule development, resource planning, knowledge and skills planning, etc.
- Activities associated with managing projects including comparing actual measures to estimates, determining project status, managing risks, reporting status, taking corrective action, tracking action items
- Requirement-based project management
- The values, principles and philosophies that underpin Agility
- Contrasting Agile philosophy to other iterative and incremental lifecycles
- Contrasting Agile with the waterfall model
- Agile methods and method tailoring
- Agile methods and project management
- Suitability of Agile methods
- Progressive requirements elaboration
- Iterative planning and adaptation
- Incremental product delivery
- Coaching self-directed teams
- Agile project monitoring
- Welcoming project change
- Interpreting Agile practices relative to reference models (e.g. CMMI or PMBOK)
- Criticism