Difference between revisions of "HIGH ROI EXPECTATIONS"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span | + | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span> |
=<span style="font-size: 16px">'''Issue Summary'''</span>= | =<span style="font-size: 16px">'''Issue Summary'''</span>= | ||
| − | <span style="font-size: 16px">Management wants to maximize ROI from the test automation project, but is not prepared to invest adequately | + | <span style="font-size: 16px">Management wants to maximize ROI from the test automation project, but is not prepared to invest adequately.</span> |
=<span style="font-family: Arial; font-size: 16px">'''Category'''</span>= | =<span style="font-family: Arial; font-size: 16px">'''Category'''</span>= | ||
| − | <span style="font-family: Arial; font-size: 16px">Management</span | + | <span style="font-family: Arial; font-size: 16px">Management</span> |
=<span style="font-size: 16px">'''Examples'''</span>= | =<span style="font-size: 16px">'''Examples'''</span>= | ||
| − | |||
| − | |||
# <span style="font-size: 16px">Management thinks that buying an expensive testing tool is all that's needed for test automation</span> | # <span style="font-size: 16px">Management thinks that buying an expensive testing tool is all that's needed for test automation</span> | ||
# <span style="font-size: 16px">Management expects that with test automation you will be able to find lots of bugs (even if it is regression testing that was automated)</span> | # <span style="font-size: 16px">Management expects that with test automation you will be able to find lots of bugs (even if it is regression testing that was automated)</span> | ||
# <span style="font-size: 16px">Management thinks that having test automation means that fewer testers will be needed</span> | # <span style="font-size: 16px">Management thinks that having test automation means that fewer testers will be needed</span> | ||
# <span style="font-size: 16px">Management thinks that you will never have to change tools, so why put so much effort into the architecture of the testware</span> | # <span style="font-size: 16px">Management thinks that you will never have to change tools, so why put so much effort into the architecture of the testware</span> | ||
| − | |||
=<span style="font-size: 16px">'''Questions'''</span>= | =<span style="font-size: 16px">'''Questions'''</span>= | ||
| − | <span style="font-size: 16px">What does management expect from test automation? What do testers expect?</span><br /> <span style="font-size: 16px">Has a business plan been worked out? </span | + | <span style="font-size: 16px">What does management expect from test automation? What do testers expect?</span><br /> <span style="font-size: 16px">Has a business plan been worked out? </span> |
=<span style="font-size: 16px">'''Resolving Patterns'''</span>= | =<span style="font-size: 16px">'''Resolving Patterns'''</span>= | ||
<span style="font-size: 16px">Most recommended:</span><br /> | <span style="font-size: 16px">Most recommended:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">[[AUTOMATE GOOD TESTS]]: use this pattern to select the test cases to automate that will bring the greatest ROI as quickly as possible</span> | * <span style="font-size: 16px">[[AUTOMATE GOOD TESTS]]: use this pattern to select the test cases to automate that will bring the greatest ROI as quickly as possible</span> | ||
* <span style="font-size: 16px">Make sure that you have [[SET CLEAR GOALS]] which are realistic and achievable</span> | * <span style="font-size: 16px">Make sure that you have [[SET CLEAR GOALS]] which are realistic and achievable</span> | ||
| Line 23: | Line 19: | ||
* <span style="font-size: 16px">[[SHARE INFORMATION]]: communicate what can realistically be achieved with automation, set manager's expectations to more realistic levels</span> | * <span style="font-size: 16px">[[SHARE INFORMATION]]: communicate what can realistically be achieved with automation, set manager's expectations to more realistic levels</span> | ||
<br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | <br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">[[ AUTOMATE EARLY]]: This pattern, together with [[WHOLE TEAM APPROACH]], can help you deliver solid automation from the project start.</span> | * <span style="font-size: 16px">[[ AUTOMATE EARLY]]: This pattern, together with [[WHOLE TEAM APPROACH]], can help you deliver solid automation from the project start.</span> | ||
* <span style="font-size: 16px">[[DESIGN FOR REUSE]]: Apply this pattern for long-term ROI</span> | * <span style="font-size: 16px">[[DESIGN FOR REUSE]]: Apply this pattern for long-term ROI</span> | ||
| Line 31: | Line 26: | ||
* <span style="font-size: 16px">[[TEST AUTOMATION FRAMEWORK]]: Good pattern for long-term ROI</span> | * <span style="font-size: 16px">[[TEST AUTOMATION FRAMEWORK]]: Good pattern for long-term ROI</span> | ||
* <span style="font-size: 16px">[[TOOL INDEPENDENCE]]: Apply this pattern if you want to implement really long lasting automation</span> | * <span style="font-size: 16px">[[TOOL INDEPENDENCE]]: Apply this pattern if you want to implement really long lasting automation</span> | ||
| − | * <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: If you are just starting with automation and your developers are using an agile process, then this is definitely the pattern of choice. Otherwise you must first | + | * <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: If you are just starting with automation and your developers are using an agile process, then this is definitely the pattern of choice. Otherwise you must first convince management and development to switch to agile.</span> |
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div> | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 14:40, 27 June 2018
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
Issue Summary
Management wants to maximize ROI from the test automation project, but is not prepared to invest adequately.
Category
Management
Examples
- Management thinks that buying an expensive testing tool is all that's needed for test automation
- Management expects that with test automation you will be able to find lots of bugs (even if it is regression testing that was automated)
- Management thinks that having test automation means that fewer testers will be needed
- Management thinks that you will never have to change tools, so why put so much effort into the architecture of the testware
Questions
What does management expect from test automation? What do testers expect?
Has a business plan been worked out?
Resolving Patterns
Most recommended:
- AUTOMATE GOOD TESTS: use this pattern to select the test cases to automate that will bring the greatest ROI as quickly as possible
- Make sure that you have SET CLEAR GOALS which are realistic and achievable
- DO A PILOT: apply this pattern if you are just starting with test automation and neither management nor you really can judge what it costs and what it will bring, or if previous automation has been too expensive and you want to make significant changes to improve the ROI
- MAINTAINABLE TESTWARE: apply this pattern for long-term ROI, not necessarily for quick wins
- SHARE INFORMATION: communicate what can realistically be achieved with automation, set manager's expectations to more realistic levels
Other useful patterns:
- AUTOMATE EARLY: This pattern, together with WHOLE TEAM APPROACH, can help you deliver solid automation from the project start.
- DESIGN FOR REUSE: Apply this pattern for long-term ROI
- GOOD PROGRAMMING PRACTICES: Apply this pattern for long-term ROI
- MANAGEMENT SUPPORT: You will need this pattern in order to be able to implement other patterns (for instance WHOLE TEAM APPROACH or DO A PILOT)
- TAKE SMALL STEPS: Use this pattern for quick wins, but actually it's always applicable
- TEST AUTOMATION FRAMEWORK: Good pattern for long-term ROI
- TOOL INDEPENDENCE: Apply this pattern if you want to implement really long lasting automation
- WHOLE TEAM APPROACH: If you are just starting with automation and your developers are using an agile process, then this is definitely the pattern of choice. Otherwise you must first convince management and development to switch to agile.
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues