Difference between revisions of "SELL THE BENEFITS"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Topic titles in capital letters) |
||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span> | ||
| − | =<span style="font-size: 16px">Pattern summary</span>= | + | =<span style="font-size: 16px">'''Pattern summary'''</span>= |
<span style="font-size: 16px">Inform management before and during test automation about achievable and achieved benefits. </span> | <span style="font-size: 16px">Inform management before and during test automation about achievable and achieved benefits. </span> | ||
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
<span style="font-size: 16px">Management</span> | <span style="font-size: 16px">Management</span> | ||
| − | =<span style="font-size: 16px">Context</span>= | + | =<span style="font-size: 16px">'''Context'''</span>= |
| − | <span style="font-size: 16px">Apply this pattern if you need support from management, testers or developers.</span><br /> <span style="font-size: 16px">You don't need it if you only plan to write some disposable scripts</span> =<span style="font-size: 16px">Description</span>= | + | <span style="font-size: 16px">Apply this pattern if you need support from management, testers or developers.</span><br /> <span style="font-size: 16px">You don't need it if you only plan to write some disposable scripts</span> |
| + | =<span style="font-size: 16px">'''Description'''</span>= | ||
<span style="font-size: 16px">Regardless what goals you are pursuing, you will not get support if you cannot illustrate the advantages your actions will bring. Inform management and the parties involved before the automation gets started and regularly as long as the automation lives. Let them participate both in your success and in your failures. Success will be a boon for next time (people will know that you deliver what you promised), but even failure can be helpful to avoid similar problems in the future ([[LEARN FROM MISTAKES]]).</span> | <span style="font-size: 16px">Regardless what goals you are pursuing, you will not get support if you cannot illustrate the advantages your actions will bring. Inform management and the parties involved before the automation gets started and regularly as long as the automation lives. Let them participate both in your success and in your failures. Success will be a boon for next time (people will know that you deliver what you promised), but even failure can be helpful to avoid similar problems in the future ([[LEARN FROM MISTAKES]]).</span> | ||
| − | =<span style="font-size: 16px">Implementation</span>= | + | =<span style="font-size: 16px">'''Implementation'''</span>= |
<span style="font-size: 16px">If needed, before the automation starts, prepare a business plan to show management “with numbers” what ROI test automation would bring.</span><br /> <span style="font-size: 16px">Even if you don't show ROI, outline what the benefits would be from automation. Make sure to distinguish benefits and objectives of <u>automation</u> as separate from <u>testing</u>.</span><br /> <span style="font-size: 16px">Take care to get a clear picture of the problems you want to solve. Include the involved parties in the search for a solution. When one has participated in a decision he or she will be much more willing to implement it and, just as important, help you explain its benefits to management, testers and developers.</span><br /> <br /> <span style="font-size: 16px">While the project is running [[SHARE INFORMATION]] and [[CELEBRATE SUCCESS]].</span><br /> <br /> <span style="font-size: 16px">Use [[SHORT ITERATIONS]] to be able to give frequent feed-back to your managers.</span><br /> <span style="font-size: 16px">Be sure to design [[READABLE REPORTS]].</span> | <span style="font-size: 16px">If needed, before the automation starts, prepare a business plan to show management “with numbers” what ROI test automation would bring.</span><br /> <span style="font-size: 16px">Even if you don't show ROI, outline what the benefits would be from automation. Make sure to distinguish benefits and objectives of <u>automation</u> as separate from <u>testing</u>.</span><br /> <span style="font-size: 16px">Take care to get a clear picture of the problems you want to solve. Include the involved parties in the search for a solution. When one has participated in a decision he or she will be much more willing to implement it and, just as important, help you explain its benefits to management, testers and developers.</span><br /> <br /> <span style="font-size: 16px">While the project is running [[SHARE INFORMATION]] and [[CELEBRATE SUCCESS]].</span><br /> <br /> <span style="font-size: 16px">Use [[SHORT ITERATIONS]] to be able to give frequent feed-back to your managers.</span><br /> <span style="font-size: 16px">Be sure to design [[READABLE REPORTS]].</span> | ||
| − | =<span style="font-size: 16px">Potential problems</span>= | + | =<span style="font-size: 16px">'''Potential problems'''</span>= |
<span style="font-size: 16px">Be careful that you aren't too successful! It is easy to describe the benefits a bit too enthusiastically, and managers may tip into ''[[UNREALISTIC EXPECTATIONS]]''</span> | <span style="font-size: 16px">Be careful that you aren't too successful! It is easy to describe the benefits a bit too enthusiastically, and managers may tip into ''[[UNREALISTIC EXPECTATIONS]]''</span> | ||
| − | =<span style="font-size: 16px">Issues addressed by this pattern</span>= | + | =<span style="font-size: 16px">'''Issues addressed by this pattern'''</span>= |
''<span style="font-size: 16px">[[INADEQUATE SUPPORT]]</span>''<br /> ''<span style="font-size: 16px">[[ INADEQUATE TOOLS]]</span>''<br /> ''<span style="font-size: 16px">[[ INSUFFICIENT METRICS]]</span>''<br /> ''<span style="font-size: 16px">[[STALLED AUTOMATION]]</span>'' | ''<span style="font-size: 16px">[[INADEQUATE SUPPORT]]</span>''<br /> ''<span style="font-size: 16px">[[ INADEQUATE TOOLS]]</span>''<br /> ''<span style="font-size: 16px">[[ INSUFFICIENT METRICS]]</span>''<br /> ''<span style="font-size: 16px">[[STALLED AUTOMATION]]</span>'' | ||
| − | =<span style="font-size: 16px">Experiences</span>= | + | =<span style="font-size: 16px">'''Experiences'''</span>= |
<span style="font-size: 16px">If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span></div> | <span style="font-size: 16px">If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span></div> | ||
Revision as of 14:58, 29 April 2018
.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns
.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns
Pattern summary
Inform management before and during test automation about achievable and achieved benefits.
Category
Management
Context
Apply this pattern if you need support from management, testers or developers.
You don't need it if you only plan to write some disposable scripts
Description
Regardless what goals you are pursuing, you will not get support if you cannot illustrate the advantages your actions will bring. Inform management and the parties involved before the automation gets started and regularly as long as the automation lives. Let them participate both in your success and in your failures. Success will be a boon for next time (people will know that you deliver what you promised), but even failure can be helpful to avoid similar problems in the future (LEARN FROM MISTAKES).
Implementation
If needed, before the automation starts, prepare a business plan to show management “with numbers” what ROI test automation would bring.
Even if you don't show ROI, outline what the benefits would be from automation. Make sure to distinguish benefits and objectives of automation as separate from testing.
Take care to get a clear picture of the problems you want to solve. Include the involved parties in the search for a solution. When one has participated in a decision he or she will be much more willing to implement it and, just as important, help you explain its benefits to management, testers and developers.
While the project is running SHARE INFORMATION and CELEBRATE SUCCESS.
Use SHORT ITERATIONS to be able to give frequent feed-back to your managers.
Be sure to design READABLE REPORTS.
Potential problems
Be careful that you aren't too successful! It is easy to describe the benefits a bit too enthusiastically, and managers may tip into UNREALISTIC EXPECTATIONS
Issues addressed by this pattern
INADEQUATE SUPPORT
INADEQUATE TOOLS
INSUFFICIENT METRICS
STALLED AUTOMATION
Experiences
If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns