Showing key stakeholders that your test automation
efforts are worth continued investment is often tricky, because value is a
relative term that varies based on a given organization's needs. One important
aspect in relaying value is telling a well-rounded story of how test automation
has been beneficial to your organization. This story might include the
following:
·
Script Development Metrics - Identifying metrics
related to the percentage of manual tests that have been automated helps to
reveal the productivity of your team
·
Cost Savings ROI - The amount of money that has
been saved in the test implementation
·
Efficiency ROI - The amount of time that has
been saved in the test implementation
·
Risk Reduction ROI - The amount of money that
has potentially been saved by reducing risks, increasing test coverage, and
allowing manual testers to focus on finding costly, hard to find defects
·
Defects Identified - The number of defects found
during automated test development and/or implementation
·
Organizational Impact - Revealing how the
introduction of automation has caused testing to be done earlier, or how it has
caused development and/or testing practices to improve, or how some small
utilities you've created are being used by other teams to increase their
efficiencies
The Business value articulation of this problem is the most sought after
deliverable.
