Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

TMAP Quality and Test Policy Template

Download as xlsx, pdf, or txt
Download as xlsx, pdf, or txt
You are on page 1of 2

TMAP template: Quality and Test Policy

© Sogeti / TMAP 2022

Quality and Test Policy subject Quality and Test Policy description
Principles of quality assurance and testing Principles of quality assurance and testing
- Definitions of Quality & testing, Quality objectives for the organization
The relationship with mission, vision and Relationship with mission, vision, business strategy, etc.
business strategy - Relation of mission, vision & business strategy to quality engineering activities
The objectives of QA & testing Objectives of QA & testing
- Set objectives that the IT products should comply with
Applied QA & testing topics Applied QA & testing topics
- Guidelines for specific application of QA & testing topics in the organization
Responsibilities in the organization Responsibilities in the organization
- General rules and guidelines for responsibilities on different levels in the organization
QA & test roles and training QA & testing roles and training
- Definition of, or reference to, specific roles in the organization, and the required level of education of the people involved
Indicators related to confidence in value Indicators related to confidence in value
- Guidelines about use of indicators (based on mission, vision and business strategy)
Testware management and reuse Testware management and reuse
- Guidelines on how to manage testware and reuse it throughout the organization
Continuous quality improvement Continuous quality improvement
- Goals and guidelines for improvement focused on quality of products, processes and people

Source:
- Chapter 15 of the book "Quality for DevOps teams", ISBN 978-90-75414-89-9
- The TMAP body of knowledge for quality engineering & testing - website: https://tmap.net/building-blocks/Quality-and-test-policy-DevOps

© Sogeti 2022
TMAP example: Quality and Test Policy
© Sogeti / TMAP 2022

The example below is by no means a perfect example, it is intended to give you an idea what policy statements may look like. For your situation they will be more specific.
A Quality & test policy should be a short document, preferably less than 1 page. There may be a separate explanation for each subject.

Quality and Test Policy subject Quality and Test Policy description
Principles of quality assurance and testing Every team together with their stakeholders takes responsibility for the quality of the IT deliverables. Principles of quality assurance and testing
We strive for a quality level that is sufficient to deliver the pursued business value and the unacceptable - Definitions of Quality & testing, Quality objectives for the organization
quality risks are covered.
Testing is an integral part of quality engineering aimed at building in quality and providing information about
quality and the related risks.

The relationship with mission, vision and In accordance with the mission and vision, our organization wants to provide visitors with a unique customer Relationship with mission, vision, business strategy, etc.
business strategy experience through the latest technology. - Relation of mission, vision & business strategy to quality engineering activities
To ensure the best experience, the IT systems should have maximum availability and uptime. Apart from
functionality, reliability and performance are most important
The objectives of QA & testing With the focus on built-in quality and right first time delivery, faults and incidents should be prevented and Objectives of QA & testing
downtime should be minimal. - Set objectives that the IT products should comply with
The end result should at least comply with:
• Fulfils the business and technical requirements as described in the contract documents, the analysis - and
design documents (including user story descriptions)
• Works as expected and can be used within its operational environment
• Is implemented with the required non-functional quality characteristics
Applied QA & testing topics The Organizing QA & Testing topics are implemented for the organization as a whole. Applied QA & testing topics
The Performing QA & Testing topics are implemented for every team specifically. - Guidelines for specific application of QA & testing topics in the organization
Responsibilities in the organization The responsibility for delivering the right product is with the product owner(s). Responsibilities in the organization
The responsibility for delivering the product right is with the DevOps team(s). - General rules and guidelines for responsibilities on different levels in the organization
The responsibility for providing the requested tools and services is with the system team(s).
People involved take joint responsibility for delivering the right quality at the right moment.
QA & test roles and training The end-to-end quality orchestrator role is implemented per Agile Release Train. QA & testing roles and training
All team members must be willing and ready to perform quality engineering tasks. - Definition of, or reference to, specific roles in the organization, and the required level of education of the people involved
All team members need to obtain the "TMAP:Quality for cross-functional teams" certification.
Indicators related to confidence in value Every team selects 5 to 8 relevant indicators and cover product, process & people at least once. Indicators related to confidence in value
The three most important indicators to measure objectives and pursued business value are: - Guidelines about use of indicators (based on mission, vision and business strategy)
• Customer satisfaction (focused on business value & product)
• Technical debt (focused on IT delivery process)
• Satisfaction and happiness of team members (focused on people)
Testware management and reuse Testware is managed using the automated tools in the CI/CD pipeline and reused as much as possible within Testware management and reuse
and across teams. - Guidelines on how to manage testware and reuse it throughout the organization
For end-to-end testing the teams involved maintain test data that aligns.
Continuous quality improvement We strive to continuously improve the products, processes and people to deliver business value. Continuous quality improvement
Use Goal Question Metric (GQM) for product improvement. - Goals and guidelines for improvement focused on quality of products, processes and people
Use Quality to Activity Mapping (QAM) for process improvement.
Use Quality to People Mapping (QPM) for people improvement.

Source:
- Chapter 15 of the book "Quality for DevOps teams", ISBN 978-90-75414-89-9
- The TMAP body of knowledge for quality engineering & testing - website: https://tmap.net/building-blocks/Quality-and-test-policy-DevOps

© Sogeti 2022

You might also like