Sample Project Plan
This appendix provides a sample of an automation project plan for you to use as a model when you develop your own plan. The plan given here is only an example; it is not intended to apply to all environments.
The automation plan follows the four-phase approach used elsewhere in this book. Table 1 lists the phases and summarizes the activities involved in each phase. Although the phases are generally sequential, you might need to start one phase before you complete all parts of the preceding phase. That is, some tasks within a phase could depend on the completion of a task in a different phase. For example, you might need to complete the resource-definition task of the design phase (task 2.03) before you can perform the cost-justification task of the definition phase (task 1.13). Also, install automation on the test system (task 3.04) before you track and compare performance on the test system (task 2.05).
| Phase | Phase Name | Summary of Activities |
|---|---|---|
| 1 | Definition | Set up a planning team to manage and perform activities. Identify goals and objectives. Define short- and long-range goals for the automation project. Document the current operating environment and practices. Create a project plan for automation. |
| 2 | Design | Set up a design team to manage and perform activities. Design an implementation plan for automation and ensure that the plan meets your short-range and long-range goals and objectives. |
| 3 | Implementation | Set up an implementation team to manage and perform activities. Develop the procedures to automate operations in the areas identified, following the plan from the design phase. Code and test these procedures on a test system. |
| 4 | Production | Set up a production team to manage and perform activities. Install and test your automation procedures on production systems. Track system performance and revise procedures as necessary. Gather data to plan for the next stage of automation. |
If you implement automation in stages, rather than all at once, you can perform the tasks in your automation plan repeatedly throughout the automation process. Experience and data gathered from one stage can help you improve your plan for the next stage.
An operating environment is dynamic. As you work on your automation plan, your organization might add new software and hardware to its systems and networks. Be prepared to accommodate the changes. Allow time in your schedules to analyze changes, to evaluate automation with regard to new products, and to incorporate new products into the automation process.
If your organization has a thorough set of operating procedures, policies, and reports, you can accomplish many of the information-gathering tasks simply by collecting existing documentation.