Difference between revisions of "FULL TIME JOB"
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 [[ Process Patterns]] / Back to [[Test Automation Patterns]]</span><br /> | + | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[ Process Patterns]] / Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 16px">'''Pattern Summary'''</span><br /> <span style="font-size: 16px">Arrange for the test automation team to be available full time.</span><br /> <br /> |
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
<span style="font-size: 16px">Process</span><br /> <br /> | <span style="font-size: 16px">Process</span><br /> <br /> | ||
| − | =<span style="font-size: 16px">Context</span>= | + | =<span style="font-size: 16px">'''Context'''</span>= |
<span style="font-size: 16px">This pattern is appropriate for larger organisations, or for those who are establishing a solid starting point for long lasting, maintainable test automation. It is a good idea to have a pilot automation project staffed by a few people full-time for a few months.</span><br /> <span style="font-size: 16px">Once your automation is well-established, you may not need automators full-time, so this pattern may be a temporary one for you.</span><br /> <span style="font-size: 16px">This pattern is not appropriate for small organisations, or where one person must be both tester and automator, or when there are severe resource restrictions.</span><br /> <br /> | <span style="font-size: 16px">This pattern is appropriate for larger organisations, or for those who are establishing a solid starting point for long lasting, maintainable test automation. It is a good idea to have a pilot automation project staffed by a few people full-time for a few months.</span><br /> <span style="font-size: 16px">Once your automation is well-established, you may not need automators full-time, so this pattern may be a temporary one for you.</span><br /> <span style="font-size: 16px">This pattern is not appropriate for small organisations, or where one person must be both tester and automator, or when there are severe resource restrictions.</span><br /> <br /> | ||
| − | =<span style="font-size: 16px">Description</span>= | + | =<span style="font-size: 16px">'''Description'''</span>= |
<span style="font-size: 16px">Test automation is quite a complex task, so it is very helpful if team members are dedicated to the task and are able to concentrate full time on test automation. The full-time team may be formed for a relatively short time, e.g. 3 to 6 months, or it could be for a longer time (several years). In larger organisations, there may be a permanent full-time team dedicated to test automation.</span><br /> <br /> | <span style="font-size: 16px">Test automation is quite a complex task, so it is very helpful if team members are dedicated to the task and are able to concentrate full time on test automation. The full-time team may be formed for a relatively short time, e.g. 3 to 6 months, or it could be for a longer time (several years). In larger organisations, there may be a permanent full-time team dedicated to test automation.</span><br /> <br /> | ||
| − | =<span style="font-size: 16px">Implementation</span>= | + | =<span style="font-size: 16px">'''Implementation'''</span>= |
<span style="font-size: 16px">With [[ MANAGEMENT SUPPORT]] you should be able to free your team members from other tasks. </span><br /> <span style="font-size: 16px">Working full time on the test automation team will also be a boost to motivation, because by concentrating on one job, people can work better and so get more satisfaction from what they’re doing.</span><br /> <br /> | <span style="font-size: 16px">With [[ MANAGEMENT SUPPORT]] you should be able to free your team members from other tasks. </span><br /> <span style="font-size: 16px">Working full time on the test automation team will also be a boost to motivation, because by concentrating on one job, people can work better and so get more satisfaction from what they’re doing.</span><br /> <br /> | ||
| − | =<span style="font-size: 16px">Recommendations</span>= | + | =<span style="font-size: 16px">'''Recommendations'''</span>= |
<span style="font-size: 16px">Inform management of the benefits of having the team work exclusively on the test automation project.</span><br /> <span style="font-size: 16px">[[SHARE INFORMATION]] to management about the risks of not being able to implement automation as successfully if the team cannot concentrate completely on it, at least for a time. </span><br /> <br /> | <span style="font-size: 16px">Inform management of the benefits of having the team work exclusively on the test automation project.</span><br /> <span style="font-size: 16px">[[SHARE INFORMATION]] to management about the risks of not being able to implement automation as successfully if the team cannot concentrate completely on it, at least for a time. </span><br /> <br /> | ||
| − | =<span style="font-size: 16px">Potential Problems</span>= | + | =<span style="font-size: 16px">'''Potential Problems'''</span>= |
<span style="font-size: 16px">If you do most of the automation work on the side-line, maybe because you found it really interesting, you let management believe that everybody will be doing it just like you and they will expect the same from everybody. This is a good way to loose good people if they are not willing to sacrifice all their free time for the job.</span><br /> <br /> | <span style="font-size: 16px">If you do most of the automation work on the side-line, maybe because you found it really interesting, you let management believe that everybody will be doing it just like you and they will expect the same from everybody. This is a good way to loose good people if they are not willing to sacrifice all their free time for the job.</span><br /> <br /> | ||
| − | =<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 TEAM]]</span>''<br /> ''<span style="font-size: 16px">[[SCHEDULE SLIP]]</span>''<br /> ''<span style="font-size: 16px">[[UNMOTIVATED TEAM]]</span>''<br /> <br /> | ''<span style="font-size: 16px">[[INADEQUATE TEAM]]</span>''<br /> ''<span style="font-size: 16px">[[SCHEDULE SLIP]]</span>''<br /> ''<span style="font-size: 16px">[[UNMOTIVATED TEAM]]</span>''<br /> <br /> | ||
| − | =<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 [[Process 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 [[Process Patterns]] / Back to [[Test Automation Patterns]]</span></div> | ||
Revision as of 13:13, 28 April 2018
.................................................................................................................Main Page / Back to Process Patterns / Back to Test Automation Patterns
Pattern Summary
Arrange for the test automation team to be available full time.
.................................................................................................................Main Page / Back to Process Patterns / Back to Test Automation Patterns
Pattern Summary
Arrange for the test automation team to be available full time.
Category
Process
Context
This pattern is appropriate for larger organisations, or for those who are establishing a solid starting point for long lasting, maintainable test automation. It is a good idea to have a pilot automation project staffed by a few people full-time for a few months.
Once your automation is well-established, you may not need automators full-time, so this pattern may be a temporary one for you.
This pattern is not appropriate for small organisations, or where one person must be both tester and automator, or when there are severe resource restrictions.
Description
Test automation is quite a complex task, so it is very helpful if team members are dedicated to the task and are able to concentrate full time on test automation. The full-time team may be formed for a relatively short time, e.g. 3 to 6 months, or it could be for a longer time (several years). In larger organisations, there may be a permanent full-time team dedicated to test automation.
Implementation
With MANAGEMENT SUPPORT you should be able to free your team members from other tasks.
Working full time on the test automation team will also be a boost to motivation, because by concentrating on one job, people can work better and so get more satisfaction from what they’re doing.
Recommendations
Inform management of the benefits of having the team work exclusively on the test automation project.
SHARE INFORMATION to management about the risks of not being able to implement automation as successfully if the team cannot concentrate completely on it, at least for a time.
Potential Problems
If you do most of the automation work on the side-line, maybe because you found it really interesting, you let management believe that everybody will be doing it just like you and they will expect the same from everybody. This is a good way to loose good people if they are not willing to sacrifice all their free time for the job.
Issues addressed by this pattern
INADEQUATE TEAM
SCHEDULE SLIP
UNMOTIVATED TEAM
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 Process Patterns / Back to Test Automation Patterns