What AI makes out of ACT2LEAD heuristic

Last week at the SEETEST 2024 conference in Zagreb, Marko and Kari delivered a successful and thought-provoking presentation about the importance of taking the needed actions at all leadership levels to lead testing to make it efficient. There were great discussions after the presentation in the conference room and discussions continued also afterwards. Also, there were many great AI and testing talks.

Inspired by the AI talks, we gave the ACT2LEAD acronym (as described in Chapter 5.3 of our book) to GenerativeAI Claude 3.5 Sonnet. We asked it to act as Head of Testing of a large company and create a test policy aligned with the ACT2LEAD heuristic.

Here's the answer that the AI gave us. It is not formatted at all - not too bad, don't you think?

Would you use it as is in your own organization?

 

Testing Policy: ACT2LEAD Approach

 

1. Add Testing Everywhere:

   - Integrate testing into every phase of the software development lifecycle.

   - Encourage all team members, regardless of role, to participate in testing activities.

   - Implement continuous testing practices to ensure quality at every step.

 

2. Context-Driven Leadership:

   - Adapt testing strategies based on project context, team dynamics, and business needs.

   - Regularly assess and adjust testing approaches to suit changing environments.

   - Avoid one-size-fits-all solutions; tailor testing methods to each unique situation.

 

3. Transparency in Testing:

   - Implement clear reporting mechanisms for all testing activities, including outsourced work.

   - Maintain open communication channels between testing teams, developers, and stakeholders.

   - Use visual management tools (e.g., dashboards) to provide real-time insights into testing progress and results.

 

4. Two-Pronged Testing Approach:

   4.1 Human Testing:

   - Employ exploratory testing techniques to uncover unexpected issues.

   - Encourage critical thinking and scenario-based testing by human testers.

 

   4.2 Automated Testing:

   - Develop and maintain a robust automated testing suite for repetitive checks.

   - Balance automated and manual testing efforts based on project needs and risk assessment.

 

5. Learning-Centric Testing:

   - Establish a culture of continuous learning within the testing team.

   - Conduct regular retrospectives to identify lessons learned and areas for improvement.

   - Share testing insights with development and business teams to enhance overall product quality.

 

6. Enable Quality Culture:

   - Promote the importance of quality and testing across the organization.

   - Provide training and resources to all team members on quality assurance principles.

   - Recognize and reward quality-focused behaviors and initiatives.

 

7. Adaptive Risk-Based Testing:

   - Continuously assess and prioritize testing efforts based on identified risks.

   - Implement a flexible testing strategy that can quickly shift focus to high-risk areas.

   - Develop risk mitigation plans through targeted testing efforts.

 

8. Diverse Testing Approaches:

   - Employ a wide range of testing techniques and methodologies.

   - Encourage diverse perspectives within the testing team through varied skill sets and backgrounds.

   - Utilize different testing tools and frameworks to provide comprehensive coverage.