Include the following information for the description of each task and adjust as necessary. Task Name – The name of the major task to be accomplished Resources – Resources that will be needed to accomplish the task Key Staff – The names and roles of key person(s) responsible for the task Success Criteria – The criteria for successful completion of the task (such as “user acceptance”) Examples of major tasks can include the following: Provide overall planning and coordination for the implementation Provide appropriate training for personnel Ensure that all manuals applicable to the implementation effort are available when needed Provide all needed technical assistance Schedule any special computer processing required for the implementation Perform site surveys before implementation Ensure that all prerequisites have been fulfilled before the implementation date Provide personnel for the implementation team Acquire special hardware or software Perform data conversion before loading data into the system Prepare site facilities for implementation] Example: Task Resources Key Success Criteria Ensure that all prerequisites have been fulfilled before the implementation date Completed Phase Checklists Testing Results Deliverable Approvals Name – Project Manager Name – Quality Manager PM and QM are able to confirm and document that all prerequisites have been fulfilled Provide appropriate training for personnel Training Curriculum Training Sessions Training Materials Name – Training Manager Training Manager confirms that any staff requiring training has received training Implementation Schedule [This section of the Implementation Management Plan provides a schedule of activities to be accomplished. Show the required tasks (described in Major Tasks) in chronological order, with the beginning and end dates of each task. Tasks, Planned Start, Planned Finish, and Dependencies should be drawn from the project’s schedule and kept in synch as the project progresses. Add tasks, planned start and finish dates, and tasks dependencies as needed.] Example:
Example: Name / ID Type Model/Version Physical Location Contract # Maint. Contract Contact Maint. Type / Level Expiration Licenses PL_PRDWEB#01 Server Model XX.XXXX Data Center IT #XXXXX Name, Number Preventative maintenance XX/XX/XXXX None
Software [This subsection of the Implementation Management Plan provides a list of non-hardware components (such as software, databases, and compilers, operating systems, and utilities) required to support the implementation. Identify the component by specific name, code, or acronym, identification numbers, version numbers, release numbers, and applicable configuration settings. Identify whether the component is commercial off-the-shelf (COTS), custom developed, or legacy. Identify any component used to facilitate the implementation process. Again, this information is likely to exist in other project documents such as the System Specification Document, the Configuration Management Plan, bill of lading, or contractual documents. If those documents exist and provide the necessary information, you may consider referencing them here instead of duplicating the information to avoid any inconsistencies that may develop. If not, then the following fields should be considered in creating the software inventory: Name/ID – Name or identifier of the software component Type – Type of software component (such as browser, RDBMS) – Model and/or version number of the software component Physical Location – Physical location where the software component is installed Software Owner – Designated owner of the equipment by organizational entity or name Maintenance Contract – Maintenance contract number (if contract exists) Maintenance Contact Point – Contact point for the maintenance contract (if one exists) Maintenance Type/ Level of Coverage – Maintenance contract coverage details (if one exists) Maintenance Period Expiration Date – Maintenance contract period (if one exists) Required Licenses – Number and type of licenses required (if applicable)]
Example: Name / ID Type Model/Version Physical Location Maint. Contract # Maint. Contract Contact Maint. Type / Level Expiration Licenses Software Title Identity and Access Management Ver. X.XX Data Center IT #XXXXX Name, Number Automatic Upgrade XX/XX/XXXX 220
Facilities [This section of the Implementation Management Plan identifies the physical facilities, accommodations, and their location(s) required during implementation. Examples include physical workspace for assembling and testing hardware components, desk space for software installers, floor space for equipment, and classroom space for training the implementation staff. Specify the hours per day needed, number of days, and anticipated dates. Document the facilities needed using the following fields. Add rows and additional columns as needed Purpose – What the facility will be used for Size – The required size of the facility. This can be expressed in of what must be accommodated or in terms of physical size. Days/hours – Planned days and hours of use for the facility Duration – Period of time the facility will be needed] Example: Purpose Size Resources Needed Day/Hours of Use Duration Training 2 instructors, 20 students per training session, computer training 22 desks 22 desktop computers CBT system Projector Network Connectivity Sufficient Electrical outlets Mon-Fri, 7 AM – 6 PM XX/XX/XXXX to XX/XX/XXXX Materials [This section of the Implementation Management Plan identifies any other consumables (such as technology, supplies, and materials) required to support the system. Provide the names, identification numbers, version numbers, release numbers, and owners.] Example: Item Identification Version #/Release # Owner Archival tapes Manufacturer Name Part # XXXX N/A IT