Difference between revisions of "Management Issues"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial; font-size: 16px">Management issues list the problems that occur when management has...") |
m (Contour lines added) |
||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial; font-size: 16px">Management issues list the problems that occur when management has not given the necessary support or resources to the automation team or team members are new to test automation. Problems can also be caused by unrealistic expectations. The table below gives a short list of the issues. Clicking on an issue shows more detail and the patterns needed to solve it. </span><br /> <span style="font-family: Arial; font-size: 16px">The [[Management%20Issues%20Mind%20Map]] shows an overview of the Management Issues, </span><span style="font-size: 16px">together with the top level of resolving patterns, both the Most Recommended and other Useful patterns.</span><br /> <br /> <br /> | <div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial; font-size: 16px">Management issues list the problems that occur when management has not given the necessary support or resources to the automation team or team members are new to test automation. Problems can also be caused by unrealistic expectations. The table below gives a short list of the issues. Clicking on an issue shows more detail and the patterns needed to solve it. </span><br /> <span style="font-family: Arial; font-size: 16px">The [[Management%20Issues%20Mind%20Map]] shows an overview of the Management Issues, </span><span style="font-size: 16px">together with the top level of resolving patterns, both the Most Recommended and other Useful patterns.</span><br /> <br /> <br /> | ||
| − | {| class="wiki_table" | + | {| class="wiki_table" border="1" style="border-collapse:collapse" |
! <span style="display: block; font-size: 16px; text-align: center">Issue</span><br /> | ! <span style="display: block; font-size: 16px; text-align: center">Issue</span><br /> | ||
! <span style="display: block; font-size: 16px; text-align: center">Description</span><br /> | ! <span style="display: block; font-size: 16px; text-align: center">Description</span><br /> | ||
Latest revision as of 13:01, 30 April 2018
Management issues list the problems that occur when management has not given the necessary support or resources to the automation team or team members are new to test automation. Problems can also be caused by unrealistic expectations. The table below gives a short list of the issues. Clicking on an issue shows more detail and the patterns needed to solve it.
The Management Issues Mind Map shows an overview of the Management Issues, together with the top level of resolving patterns, both the Most Recommended and other Useful patterns.
Main Page
Back to Test Automation Issues
Back to Process Issues
Forward to Design Issues
The Management Issues Mind Map shows an overview of the Management Issues, together with the top level of resolving patterns, both the Most Recommended and other Useful patterns.
| Issue |
Description |
|---|---|
| AD-HOC AUTOMATION |
Automation is done Ad-Hoc with no planning or preparation |
| HIGH ROI EXPECTATIONS |
Management wants to maximize ROI from the test automation project, but is not prepared to invest adequately |
| INADEQUATE SUPPORT |
The test automation team doesn't get adequate support from management, testers or other specialists |
| INADEQUATE TEAM |
Either there is no test automation team and it must be built from scratch or you do not have all the roles you need on board or some or all the members of the test automation team are not suited to do test Automation |
| INADEQUATE TECHNICAL RESOURCES |
The technical resources for test automation are insufficient or not appropriate or both |
| INADEQUATE TOOLS |
The tools that are currently used are not appropriate for the Software Under Test (SUT) or are not supported any longer or you still don't have adequate tools. |
| KNOW-HOW LEAKAGE |
Test automation know-how (for instance scripting, tools) is being lost from the organisation. |
| LIMITED EXPERIENCE |
The test automation team has limited experience in test automation or in the SUT or new team members take too long to become productive |
| LOCALISED REGIMES |
Tool use or testware architecture is different from team to team |
| NO PREVIOUS TEST AUTOMATION |
You are supposed to start automating tests, but neither you nor your team has any experience in test automation and it hasn’t ever been implemented in the company |
| OBSCURE MANAGEMENT REPORTS |
Reports from test automation are not very useful to monitor the process and keep management informed |
| SCHEDULE SLIP |
The planned automation is not keeping up with its schedule for developing the automation or for automating tests |
| SUT REMAKE |
Substantial changes are being made to the SUT or it is to be rewritten from scratch |
| UNMOTIVATED TEAM |
The test automation team is not motivated. Team members don’t collaborate and are not willing to share their know-how |
| UNREALISTIC EXPECTATIONS |
There are unrealistic expectations regarding what test automation can and cannot deliver |
Main Page
Back to Test Automation Issues
Back to Process Issues
Forward to Design Issues