Technology Implementation
Problem Statement
Client has made the decision to implement a new software system but does not have the time to oversee the implementation.
Client has some IT resources to assist implement the new software system but needs additional resources to ensure the project is successful.
Mandate
Oversee day to day software implementation while keeping executive sponsor informed of important issues and progress along the way.
Approach
Develop foundational documents including a solution design document and project governance documents (covering budget, schedule, and scope).
Secure necessary internal/external resources.
Develop change management and test plan; update as necessary.
Keep key stakeholders updated on progress, issues, decisions throughout the project.
Work with software vendor to deliver optimal solution while holding them accountable to mutually agreed milestones.
Ensure the organization is adequately trained and set up to succeed.
Deliverables
Solution Design Document
Providing a schematic of the new software application and integration with other software and data feeds. This document provides a useful blueprint for the project team and organization as a whole to depict the ‘to-be” state.Project Plan
Including scope, schedule, budget, milestones, and resource plan necessary to implement the new software.Change Management Plan
To ensure the organization is aware of the change to their staff, processes and technology and to be ready for the change. This work is ongoing throughout the life of the project.Cutover Plan
To document the precise steps involved in moving from the old software to the new software including back out plans and plans to sunset those applications no longer required.
Benefits
No unintended scope creep or budget surprises with timeline tightly managed against deliverables.
Good communication results in staff understanding, accepting, and embracing the change.
Clear visibility into risks and issues to enable timely decision making and actions.
