About Us

TMAP is the body of knowledge for quality engineering in IT delivery. The strength of TMAP can be largely attributed to the considerable practical experience that is the basis for the body of knowledge. This experience comes from thousands of IT professionals in as many projects over the last twenty-five years.

TMAP was created in 1995, and back then mainly contained a process description for testing. Over the years, TMAP has evolved from process-driven, business-driven, and human-driven to a body of knowledge with which quality assurance & testing activities can be integrated in all IT delivery models. The body of knowledge contains a wide range of approaches, good practices, techniques, and tools for organizing and performing of activities related to quality assurance and testing of IT systems.
Today we use TMAP as a term on its own, rather than a meaningful abbreviation. For this reason, TMAP is now written with four capital letters.

The title of the book – Quality for DevOps teams – demonstrates that this book is primarily meant for those that want to deliver quality solutions in a DevOps setting.
DevOps is the main IT delivery model in this book.
Collaboration is key.
Collaboration between people with a shared responsibility and pick up the tasks that need to be done, based on competencies and roles, no longer worrying about official functions.
The DevOps culture is the enabler for this way of high-performance IT delivery, using an automated CI/CD pipeline to deliver at speed.
Aligned with the DevOps culture of IT delivery – where roles are important and functions are not – keep in mind that if in this book you see a term such as a developer or tester, we refer to the role of a team member at a specific moment in time, not to a function.

Quality at speed is the challenge for IT delivery teams today.
In DevOps, the delivery of a product, including the quality of that product, is the responsibility of the team as a whole, therefore our body of knowledge supports all people involved: the DevOps team members and also the other people in the organization, with knowledge, skills, tools and more.
The starting point for DevOps: A cross-functional team.