QASource Blog

QASource Blog Webinar Questions Answered: “Measuring Your Way to Successful Automation”

Webinar Questions Answered: “Measuring Your Way to Successful Automation”

QASource, in conjunction with Sauce Labs, recently presented the webinar "Measuring Your Way To Successful Automation." When preparing each webinar, we field a variety of questions about the topic at hand. We have coordinated with our expert automation engineers to answer several of the most common questions about team metrics and measurement approaches below:

  1. Which tools are used for data collection?
    • Test case management systems (Testlink, ALM, TestRail, etc.)
    • Agile management tools (Scrumworks, VersionOne, Agilotrack, etc.)
    • Defect tracking tools (Bugzilla, TestTrack Pro, Mantis, etc.)
    • Time and task management tools (Jira, LiquidPlanner, @task)

    A combination of these tools will help generate the metrics needed to evaluate team performance and drive project progress.

  2. How is the data collected and entered?
    A defined process or structure in a task tracking system (such as Jira or @task) is used from the beginning to the end of the project. With this method it only takes engineers a few minutes to record their daily task data. The tracking capability of the tools listed in question #1 also produce metrics that will highlight any areas requiring corrective action and help drive productive decision-making.
  3. How do I effectively measure my team without micro-managing them?
    Educate your engineers about the main purpose of the metrics: to track projects and improve processes. When you find a deviation in your metrics, address the issue as it relates to the process and project as a whole, rather than singling out and blaming an individual engineer. This way, metrics are viewed as a motivational force rather than a form of micro-management.
  4. How much time is required to generate these metrics?
    Not much. Integrating metrics into your process with the help of tracking tools is the best way to track your team's progress with minimal effort. In most cases, engineers should expect to spend 30 minutes a week compiling their task data.
  5. Do small teams need metrics?
    Yes, because metrics are helpful regardless of team size. Tracking the basic aspects of your team's work encourages engineers to take ownership, stay motivated and deliver the product on time. Learn more about how to increase the productivity of your QA team, regardless of size.
  6. How do I make my engineers more comfortable with the idea of team measurement with metrics?
    The culture you create has everything to do with how your team will view metrics. If you portray metrics in a positive light—as a yardstick that helps measure success rather than failure—your team will be more receptive. If possible, identify processes that have improved with the help of metrics. Remind your team that every small improvement contributes to the overall success of each project.

Are you interested in other webinars by QASource? Browse our collection here.  

Webinar - Measuring Your Way to Successful Automation

Written by QA Experts

QASource Blog, for executives and engineers, shares QA strategies, methodologies, and new ideas to inform and help effectively deliver quality products, websites, and applications.

Contact Us


Our bloggers are the test management experts at QASource. They are executives, QA managers, team leads, and testing practitioners. Their combined experience exceeds 100 years and they know how to optimize QA efforts in a variety of industries, domains, tools, and technologies.

Popular Posts