6 Big Questions to ask your team before your next Dev & QA automation project in 2025

Leaders in software development or quality assurance know that automation is no longer a luxury—it’s a necessity to help your business grow and scale. Whether it’s to reduce bugs, speed up release cycles, or cut development costs, Dev and QA automation are essential for modern software organizations. Yet, our experience is that many organizations struggle on where to begin planning holistic and successful QA automation project that will allow teams to do more.

Is there a common element in successful Dev & QA automation projects?

From our experience as experienced QA consultants in Toronto, Canada, we’ve observed that all successful QA projects are championed by leaders who set clear and transparent expectations. As a result, their entire team forge ahead to build and execute QA automation projects with results far exceeding initial expectations.

What are some practical questions software leaders should ask to gain clarity on how to plan and structure their Dev & QA automation projects?

The best way to start getting that clarity is to start asking questions to your team to uncover hidden, and often uncomfortable, concerns. Based on how our senior QA consultants run our initial discoveries withn our clients, we’re releasing a guide for all software leaders, with practical and actionable prompts you can use in your own reflection with your software and QA teams, to start down the path to gain the clarity necessary to develop and execute on your next dev and QA automation project. Our reflection prompts cover the following big reflection topics:

  • Has the need for increased testing slowed your release cycle?

  • If the reason to automate isn’t to improve velocity, then what is the true reason behind pursuing automation?

  • Are you automating to replace human processes or complement them?

  • Do you feel your QA automation tools are too isolated and don’t work well as part of a larger process?

  • Have your regulatory compliance obligations held you back from Dev and QA automation?

  • Have your dev and QA teams expressed anxiety or uncertainty with your automation plan?

Download our PDF guide with actual question prompts we use in our own consulting engagements.

Next
Next

The three things we learned as QA experts from the Crowdstrike Incident of July 2024.