The implementation of an EPM tool is completely organisation-dependent. It is important to understand the requirements of the organisation, the processes that the tool must support, the needs and pain points of the people that will interact with the system and the organisation’s capacity for change.
With this in mind, a phased implementation approach was taken at Midlands Co-operative Society, rolling out functionality over a period of time and only after suitable training and acceptance from the end-user had been achieved.
With this in mind, CPS set about ascertaining functionality requirements through a series of requirement gathering (discovery and envisioning) meetings with representatives from the various internal departments, including Finance, IT, infrastructure and service desk.
This approach facilitated a better understanding of what level of functionality each area was willing and had the capacity to accept as part of the first phase of the implementation and enabled CPS to help Midlands Cooperative Society shape how the product would fit seamlessly within a culture that is over 100 years old.
After these discovery and envisioning workshops, a prototype working system was put together in order to demonstrate back to the project stakeholders that CPS had correctly understood the requirements. This was further refined, with all unnecessary functionality turned off to keep the interface as understandable and unintimidating as possible.
Included in the functionality for first phase rollout was:
- A central repository for all plans (both Project and business as usual/absence) to enable project managers to plan together rather than separately.
- Metadata tagging of projects and resources in order to provide grouping, sorting and tracking information for each.
- High-level resource management (a more complete picture of who was working on what and when).
- A central resource pool with generic (primary role-based) resources for building up a longer-term picture of resource requirements.
- Reporting through the use of project metadata displayed in various grouping formats in the project centre, resource centre and data analysis.
- Project workspaces – a project-linked SharePoint site for tracking and logging of risks, issues, change requests and project-specific documentation (Project Brief, Business Case).
- Reporting task progress and work remaining through the use of the task updates – team members updating tasks, approval and acceptance by project managers into the project plan.
- SharePoint – To enable websites for each project, making it easier to share and find project documents with no ambiguity over the use of the correct version.
The EPM implementation process took two months from start to finish. In total, the final end-users totalled six Executives, five Project Managers and fifty Team Members. Support for the rollout of phase one was provided in the form of consultant time spent on-site working with the business, training of all interested parties and access to specialised third-tier knowledge through the CPS Support Helpdesk.