Difference between revisions of "INADEQUATE SUPPORT"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
|||
| (2 intermediate revisions 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=" | + | =<span style="font-size: 16px">'''Issue summary'''</span>= |
| − | + | <span style="font-size: 16px">The test automation team doesn't get adequate support from management, testers or other specialists</span> | |
| − | =<span style=" | + | =<span style="font-size: 16px">'''Category'''</span>= |
| − | + | <span style="font-family: Arial; font-size: 16px">Management</span> | |
| − | =<span style=" | + | =<span style="font-size: 16px">'''Examples'''</span>= |
| − | |||
| − | |||
# <span style="font-family: Arial; font-size: 16px">Management knows too little about the benefits of test automation or about the investment needed in time or money to achieve good automation.</span> | # <span style="font-family: Arial; font-size: 16px">Management knows too little about the benefits of test automation or about the investment needed in time or money to achieve good automation.</span> | ||
# <span style="font-family: Arial; font-size: 16px">Testers don’t have time to write test cases to be automated or to otherwise support the test automation team.</span> | # <span style="font-family: Arial; font-size: 16px">Testers don’t have time to write test cases to be automated or to otherwise support the test automation team.</span> | ||
| Line 12: | Line 10: | ||
# <span style="font-family: Arial; font-size: 16px">You need support (from IT-specialists, developers, database experts, business analysts etc), but nobody has time for you.</span> | # <span style="font-family: Arial; font-size: 16px">You need support (from IT-specialists, developers, database experts, business analysts etc), but nobody has time for you.</span> | ||
# <span style="font-size: 16px">Expenses or time for training haven't been budgeted.</span> | # <span style="font-size: 16px">Expenses or time for training haven't been budgeted.</span> | ||
| − | + | =<span style="font-size: 16px">'''Resolving Patterns'''</span>= | |
| − | =<span style=" | + | <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> <span style="font-family: Arial; font-size: 16px">Automation started by one person does not often "scale up". You may need to use this experience as a learning exercise and start again with good </span><span style="font-family: Arial; font-size: 16px; line-height: 1.5">[[MANAGEMENT SUPPORT]]</span><span style="font-size: 16px">. This pattern also applies if the automation work does not have a high enough priority, compared to other tasks.</span><br /> <br /> <span style="font-family: Arial; font-size: 16px">When support from other people is not there, this could also be because of a failure to [[PLAN SUPPORT ACTIVITIES]]. If you end up starting again, be sure to use this pattern, which may be more difficult if your team is distributed over different geographical locations.</span><br /> <br /> <span style="font-family: Arial; font-size: 16px">Other useful patterns:</span> |
| − | + | * <span style="font-size: 16px">[[SELL THE BENEFITS]]: use this pattern again and again to show everyone what the automation effort can achieve with their support.</span> | |
| + | * <span style="font-size: 16px">[[SHARE INFORMATION]]: this pattern may help explain why people have no time for you. It is important to let people know why and when you need their support.</span> | ||
| + | * <span style="font-size: 16px">[[SHORT ITERATIONS]]: use this pattern to work with short feedback cycles. This will let people who are supporting the automation effort know more quickly that their support is enabling you to achieve results, and this will encourage further support.</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Latest revision as of 12:33, 26 June 2018
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
Issue summary
The test automation team doesn't get adequate support from management, testers or other specialists
Category
Management
Examples
- Management knows too little about the benefits of test automation or about the investment needed in time or money to achieve good automation.
- Testers don’t have time to write test cases to be automated or to otherwise support the test automation team.
- The test automation team never gets time for maintenance.
- You need support (from IT-specialists, developers, database experts, business analysts etc), but nobody has time for you.
- Expenses or time for training haven't been budgeted.
Resolving Patterns
Most recommended:
Automation started by one person does not often "scale up". You may need to use this experience as a learning exercise and start again with good MANAGEMENT SUPPORT. This pattern also applies if the automation work does not have a high enough priority, compared to other tasks.
When support from other people is not there, this could also be because of a failure to PLAN SUPPORT ACTIVITIES. If you end up starting again, be sure to use this pattern, which may be more difficult if your team is distributed over different geographical locations.
Other useful patterns:
- SELL THE BENEFITS: use this pattern again and again to show everyone what the automation effort can achieve with their support.
- SHARE INFORMATION: this pattern may help explain why people have no time for you. It is important to let people know why and when you need their support.
- SHORT ITERATIONS: use this pattern to work with short feedback cycles. This will let people who are supporting the automation effort know more quickly that their support is enabling you to achieve results, and this will encourage further support.
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues