DevConf.US 2021

market, cost and increase the coverage and quality as much as possible. In this manner, managers try to minimize inner costs. They investigate the efficiency of each process. QA teams and activities are under investigation as well: Are we spending too much money for QA: What are they doing? Is it worth it? Are they successful? Problems: How can you understand if your QA team is successful? Solutions: In this presentation, we discuss most useful metrics to manage, track and evaluate QA teams & processes. We also present bad metrics (giving no idea about success). For instance, being concentrated on only test case numbers can lead us to wrong perceptions. Apart from numbers, quality and coverage are of great importance in terms of maturity of testing processes. Not to overcome other weaknesses, we discuss what maturity metrics should be followed comprehensively. It is not listing a huge list of metrics like a textbook. But, what we do is to share over each metric, what we extract as an insight. In each example, we describe how we interpret the progress and which action items we took if they represent any weakness in the processes. Similarly, due to personal experiences, we will share for which metrics do not make any sense. Results & Conclusion: We support our claims with real-life experiences in DevOps environments. We aim to find ways to achieve convincing our managers and ourselves as well for the necessity of QA activities and teams. After going over metrics which demonstrate the progress and quality of the product; we will all have a chance to compare how QA activities save money, time and prestige since potential bugs, which are likely to appear in Production environments, are eliminated in early stages. We have a code demonstration, in which we will collect data from Jira (using Jira API) & post them to CloudWatch to monitor them on graphs.