Difference between revisions of "SCHEDULE SLIP"
Jump to navigation
Jump to search
m (empty lines removed) |
|||
| Line 21: | Line 21: | ||
* <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]] | + | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div> |
Latest revision as of 14:57, 27 June 2018
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues
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