Business Analyst with a quality perspective
Integrating quality into the software development process should be a priority from the outset. The experience gained in testing can be a valuable...
Successful leadership in software testing requires clear models and a strong quality culture. The ACT2LEAD model offers an approach for establishing testing as a central component of the software development process. It focuses on transparency, context awareness and the balance between automation and human expertise. Learning and the ability to adapt to risks are further crucial elements. A practical handbook supports the effective implementation of these principles and the development of a sustainable testing strategy.
Today’s episode is all about software test leadership. Kari Kakkonen has been working in software testing for decades and introduces us to his ACT2LEAD model. This model focuses on making testing a core part of the software development process and ensuring that it is led effectively. Kari emphasized the need for a quality culture in which testing is transparent and contextual, encompassing both automation and human work. He also talks about the importance of learning and adapting to risk. For those who want to dive deeper, Kari has also developed a handbook on the topic.
“If you need to ask one person how does this software work and what is this software all about you actually should go to the tester. Because the tester has the big picture.” - Kari Kakkonen
Kari Kakkonen has been working in software testing for almost 30 years. He is co-author of the “ACT 2 LEAD Software Testing Leadership Handbook”. Kari is the winner of EuroSTAR Testing Excellence Award 2021, winner of Tester of the Year in Finland Award 2021 and winner of DASA Exemplary DevOps Instructor Award 2023. He is the author and CEO of Dragons Out Oy, which has developed a fantasy book to teach children how to test software. Kari works at Gofore Verify Oy as an Expertise Capability Owner and runs a training company providing software testing, agile, DevOps and AI training in Europe. He works mainly with agile testing, lean, test automation, DevOps and AI.
A crucial aspect of software testing is the lack of leadership. While teams at the operational level manage their tasks well, there is often a lack of an overarching strategy that promotes a culture of quality and innovative testing practices. Although many leaders see testing as necessary, there is often a lack of deep understanding of its importance. This lack can lead to missed opportunities to improve software quality through strategic leadership.
The “ACT2LEAD” model comprises the following elements: Add Testing to Everything, Context-driven testing, Transparency, Automation and Human involvement, Learning, Enabling Quality Culture, Adapting to Risks and Diversity. Each of these elements addresses specific aspects to improve software testing in companies.
Transparency is a central component of the model. An open exchange of information about test processes creates an environment in which all stakeholders can contribute to solving quality problems. However, transparency should be used in a targeted manner so as not to overwhelm stakeholders with unnecessary details. It is equally important to adapt to risks. The focus of testing activities should be on the areas that pose the highest risk.
A balance between automation and human involvement is crucial. Automation increases efficiency by enabling continuous integration and delivery pipelines. At the same time, human creativity is irreplaceable, especially for exploratory testing and solving complex problems. Both elements are essential for a holistic approach to testing.
Testing offers organizations the opportunity to comprehensively understand their software and continuously improve test methods. Testers often have a broader overview of software functionality than other stakeholders. A quality culture is promoted by supporting and establishing good testing practices at all management levels.
Diversity in testing refers to the use of different testing techniques, the integration of different perspectives and the use of versatile tools and methods. This diversity enables more comprehensive and robust test results, as different perspectives can uncover a wider range of errors.
ACT2LEAD serves as a practical framework and checklist for companies that want to improve their test processes. It ensures that all aspects of quality assurance are comprehensively covered. At the same time, it promotes an environment in which quality is not just the responsibility of the testers, but of everyone involved.
Test management comprises the planning, control and monitoring of all test activities within a software project. It ensures that software errors are detected and rectified at an early stage in order to guarantee the quality of the end product. This includes the definition of test strategies, the organization of the test team and the selection of suitable test tools. Effective test management minimizes risks and optimizes the entire development process.
The test manager is responsible for the conception, planning and monitoring of all test activities. He coordinates the test team, ensures compliance with quality standards and communicates with other project participants. They also identify risks, plan test resources and monitor the progress of the test phases. His main task is to ensure the quality of the software product and to design the test process efficiently.
In agile projects, test management is designed to be flexible and iterative. The test manager works closely with the development team to continuously integrate tests into the development process. This includes regular tests in short development cycles, adapting test plans to changing requirements and promoting a collaborative test culture. The aim is to ensure software quality through early and continuous testing.
The test process is divided into several phases: Test planning, test analysis and design, test implementation, test execution, evaluation of test results and test completion. Test strategies are developed in the planning phase, followed by the creation of test cases in the analysis and design phase. The implementation phase prepares the test environment, while the tests are carried out in the execution phase. Finally, the results are evaluated and documented.
Frequent challenges in test management are insufficient planning, a lack of resources, unclear requirements and communication problems within the team. In addition, technical hurdles such as the integration of test tools and dealing with changing project requirements can complicate the testing process. Proactive risk management and flexible adaptation to project changes are crucial to successfully meet these challenges.
The selection of suitable test tools is based on the specific requirements of the project. First, the required functions are identified, followed by an evaluation of available tools in terms of their suitability. Factors such as cost, user-friendliness, integration into existing systems and support are taken into account. A careful analysis ensures that the selected tool effectively supports the testing process.
Common mistakes in test management are lack of planning, inadequate resource allocation and ignoring risks. To avoid these, systematic planning is essential, including clear test strategies and realistic schedules. Regular reviews of test progress, effective communication within the team and flexible adaptation to project changes also help to minimize errors and ensure software quality.
The quality of test execution is evaluated using various metrics, such as test coverage, defect detection rate and the number of repeated defects. Compliance with schedules, the effectiveness of test cases and stakeholder satisfaction are also taken into account. Regular reviews and audits of the test process help to identify weaknesses and implement continuous improvements.
Risks in software testing projects include time delays, budget overruns, unclear requirements and technical challenges. Effective risk management begins with the identification of potential risks, followed by an assessment of their likelihood and impact. By developing countermeasures and continuous monitoring, risks can be minimized and project success ensured.
An effective test plan defines clear objectives, strategies and the scope of testing activities. It includes schedules, resource allocation, test environments and criteria for test completion. It also identifies risks and defines measures to mitigate them. Clear documentation and regular updating of the test plan ensure that everyone involved is informed and that the test process runs smoothly.
Integrating quality into the software development process should be a priority from the outset. The experience gained in testing can be a valuable...
The further development of software testing is increasingly characterized by artificial intelligence (AI). Two key areas can be distinguished: the...
World Quality Day provides an opportunity to take a look at the development of software quality and the changes in software testing over the last 20...