Software Training Plan

Software Training Plan

1 Purpose of This Document (Objectives)

Insert the purpose of this document, its objectives, and its intended audience. Example: The purpose of this document is to formally recognize and codify the policies and procedures Company wishes to enact in order to organize the software training Company provides to employees and vendors. The goals and objectives listed in this plan are meant to allow the Company to achieve a consistent training experience. The Company provides its employees, staff and vendors this Software Training Plan as an overview of the required steps and policies to be enacted when developing or executing software training.

2 Scope of Document

Insert description of the scope of this Software Training Plan and explain whether this covers an entire application or a component thereof. Indicate whether this training plan shall be governed by or supersedes other policy documents that may already be in place concerning training or a specific process or procedure.

1 Scope Constraints

Insert constraints, such as schedules, costs, interactions, overview, or any other information relevant to the training desired.

3 Goals of This Plan

Insert an overview or brief description of the product, software, or other desired end result to be achieved by this Software Training Plan.

4 Business Context

Insert an overview of the business or organizations impacted by this Software Training Plan. Include the business or organization's critical components and reliance on specific vendors, services or other assets.

5 Goals Defined

The overall goal of the Software Training Plan is to provide an easy and accessible outline to enable Company Name staff or vendors to organize and execute acceptable training and education plans.

Additional goals include:

6 References and Reference Material

Insert a list of all reference documents and other materials related to the Software Training Plan.

References will often include, but are not limited to:

User guides or manuals. Third-party books or resources. Other company software training plan(s). Any other relevant document or resource.

7 Documentation Items

Insert references to documentation or contact lists, which may include but are not limited to:

Company critical software services list. Company critical software vendors list. Company commercial software support phone numbers and services.

Company support logins or passwords. Company software support or maintenance agreements and relevant contacts.

8 Terminology Used in This Software Training Plan

Insert references and delimitations for terminology used in this plan. Include all acronyms and abbreviations as well.

9 Points of Contact

Insert point of contact, contact method and all policies for coordination of such contacts. Contact Name Contact Phone Contact Email Area of Responsibility. Software Training Plan: Current System Summary.

1 Background and System Objectives

Include the purpose and business objective(s) of the current system.

2 Hardware Requirements and Constraints

Information concerning hardware required by this plan and whether there are constraints to be considered (e.g., browsers to be used, secure locations to access software, etc.

3 Known Issues

The following are limitations or known issues impacting the Software Training Plan:

Insert additional descriptions of the limitations or known issues here.

4 Documentation

The following documentation is available for the current system:

Insert additional descriptions or lists of the available documentation.

Implementation of the Plan

Insert the overall objectives for implementation of the Software Training Plan. Your Software Training Plan may contain several different approaches for certain types of training, such as individual, small group, large group, department, seminar, review, etc.

1 Training Methods and Procedures

Here you will describe the methods and procedures you wish your trainers to follow and to educate staff on. If methods and procedures from an existing system or Training Plan are to be included in this plan, you will want to describe these procedures in this section rather than simply reference them.

2 Testing, Training Retention and Evaluation

Describe the methods to be used for administering tests, quizzes or other methods for benchmarking the retaining of the training. Explain whether testing and evaluation are to be done after the completion of the initial training plan, after a set amount of time, or a combination thereof. Make sure to describe the goals that must be achieved in this section as well.

3 Software Training Plan Timelines and Schedules

Insert any timelines, milestones or date-sensitive deadlines that must be adhered to for this Software Training Plan.

4 Software Training Plan Objectives vs. Mandates

The objectives set forth in Sect. 1.5 should be considered the overall goals of the Software Training Plan. They may not always be exact mandates. Individual departmental policies and procedures or other Software Training Plans may outline additional instructions to be followed.

5 Software Training Plan Administration: Creating Outline(s)

Using an outline format, insert a description of the methods that the Company wishes to use for administering the Software Training Plan.

For example, you might write: The Company desires that all Software Training Plans include an outline for how the trainer is to handle the following:

Enrollment of students (Learning Management System (LMS)). Classroom environment to be utilized (conference room, lecture hall). Equipment required (visual aids, projectors, workstations).

Learning materials required (books, manuals, etc. Record-keeping requirements, certificates, tests, etc.

6 Software Training Plan Performance Testing

Insert the objectives and requirements for testing to ensure that the plan operates correctly in regard to normal operation, response and execution times, scalability, portability and all other performance requirements within the business environment.

7 Software Training Plan Administration: Follow-up Training

Insert any information pertaining to whether follow-up training is required and under what schedule it must be performed. If certifications are to be considered, then include information on how students are to make sure that they achieve and keep current their third-party certifications.

8 Software Training Plan Revisions and Alterations

Insert the objectives and requirements for how revisions and alterations are to be made to the Software Training Plan. Often new methods begin to be incorporated into established training programs without being represented within a company plan document. Insert a description of how/when this document must be updated when new methods are used.

Software Training Plan: Materials. In this section you will describe and define each of the materials that will be required for the Software Training Plan. This is a detailed accounting.

You may attach additional exhibits to this section if your Software Training Plan requires them. Software Training Plan Curriculum. Insert the specific descriptions of each section of the Software Training Plan curriculum.

This is to be considered your syllabus for this Software Training Plan.

A syllabus may include, but is not limited to the following organizational structure:

General Notes

Software Training Plan Evaluation. A description of methodology concerning how evaluations of instructor(s), student(s) and course(s) are to be conducted post-training. Determine whether evaluations will be immediate or after a particular milestone or benchmark is reached (testing, certification, etc. Software Testing Plan Hardware and Environmental Requirements List.

A description of the hardware and environmental requirements for the Software Training Plan.

6 Specific Risks and Assumptions

Insert description here

Focus on restraints such as resource availability, time constraints, staff and developer availability, and all other resource dependencies or external factors that can influence the Software Training Plan.

1 Risk and Assumption Contingency Plan(s)

Insert a description of the contingency plan for each item listed above (e.g., a developer or support staff member is out sick on the day of training.

Change Request and Management

A description of the Software Training Plan change request and change management procedures. Describe the process that must be followed for submission, review and authorization for all requests for change to the Software Training Plan or for any change to any part of the deliverables.

Approval for Software Training Plan

A description of the personnel authorized to approve the Software Training Plan. Their names, titles and signatures must accompany this document.

Appendices

A description of all other supporting information required for the understanding and execution of the Software Training Plan and requirements.

All Software Training Plan documents require the following two appendices:

1 Definitions, Acronyms, Abbreviations

Definitions of important terms, abbreviations and acronyms. This may also include a Glossary of terms.

2 References

A listing of all citations to all documents and meetings referenced or used in the preparation of this Software Training Plan and testing requirements document.