Difference between revisions of "SCHEDULE SLIP"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Put 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 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">The planned automation is not keeping up with its schedule for developing the automation or for automating tests.</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-size: 16px">Examples</span>= | + | =<span style="font-size: 16px">'''Examples'''</span>= |
| − | |||
| − | |||
# <span style="font-size: 16px">Test automation is done only in people's spare time</span> | # <span style="font-size: 16px">Test automation is done only in people's spare time</span> | ||
# <span style="font-size: 16px">Team members are working on concurrent tasks which take priority over automation tasks</span> | # <span style="font-size: 16px">Team members are working on concurrent tasks which take priority over automation tasks</span> | ||
| Line 12: | Line 10: | ||
# <span style="font-size: 16px">Necessary software or hardware is not available on time or has to be shared with other projects</span> | # <span style="font-size: 16px">Necessary software or hardware is not available on time or has to be shared with other projects</span> | ||
# <span style="font-size: 16px">The planned schedule was not realistic</span> | # <span style="font-size: 16px">The planned schedule was not realistic</span> | ||
| − | + | =<span style="font-size: 16px">'''Questions'''</span>= | |
| − | =<span style="font-size: 16px">Questions</span>= | + | <span style="font-size: 16px">What is the priority for test automation?</span><br /> <span style="font-size: 16px">Is test automation supported by management or is it performed by a "lone crusader"?</span><br /> <span style="font-size: 16px">Who is doing the planning for test automation? How is the required time for automation calculated? </span><br /> <span style="font-size: 16px">What software or hardware is needed? When?</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">[[SHORT ITERATIONS]]: using this pattern you will be able to deliver something sooner, even if not what you had originally hoped or planned</span> | * <span style="font-size: 16px">[[SHORT ITERATIONS]]: using this pattern you will be able to deliver something sooner, even if not what you had originally hoped or planned</span> | ||
* <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: if development is using an agile process, then this is the pattern to apply</span> | * <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: if development is using an agile process, then this is the pattern to apply</span> | ||
| Line 23: | Line 19: | ||
* <span style="font-size: 16px">[[PLAN SUPPORT ACTIVITIES]]: use this pattern from the beginning so that resources are available when needed</span> | * <span style="font-size: 16px">[[PLAN SUPPORT ACTIVITIES]]: use this pattern from the beginning so that resources are available when needed</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">[[FULL TIME JOB]]: this pattern helps the automation team work more efficiently</span> | * <span style="font-size: 16px">[[FULL TIME JOB]]: this pattern helps the automation team work more efficiently</span> | ||
* <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: use this pattern to free DEDICATED RESOURCES</span> | * <span style="font-size: 16px">[[MANAGEMENT SUPPORT]]: use this pattern to free DEDICATED RESOURCES</span> | ||
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span><br /> <span style="font-size: 14px">B2</span></div> | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span><br /> <span style="font-size: 14px">B2</span></div> | ||
Revision as of 07:47, 1 May 2018
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
B2
Issue Summary
The planned automation is not keeping up with its schedule for developing the automation or for automating tests.
Category
Management
Examples
- Test automation is done only in people's spare time
- Team members are working on concurrent tasks which take priority over automation tasks
- Schedules for what automation can be done were too optimistic
- Necessary software or hardware is not available on time or has to be shared with other projects
- The planned schedule was not realistic
Questions
What is the priority for test automation?
Is test automation supported by management or is it performed by a "lone crusader"?
Who is doing the planning for test automation? How is the required time for automation calculated?
What software or hardware is needed? When?
Resolving Patterns
Most recommended:
- SHORT ITERATIONS: using this pattern you will be able to deliver something sooner, even if not what you had originally hoped or planned
- WHOLE TEAM APPROACH: if development is using an agile process, then this is the pattern to apply
- DEDICATED RESOURCES: this pattern will help you pick up speed.
- PLAN SUPPORT ACTIVITIES: use this pattern from the beginning so that resources are available when needed
Other useful patterns:
- FULL TIME JOB: this pattern helps the automation team work more efficiently
- MANAGEMENT SUPPORT: use this pattern to free DEDICATED RESOURCES
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
B2