The purpose of a Product Health Check is to ensure that you are gaining the maximum benefit and return from your investment in Hydra. The aim is not to wait for the edge to wear off the gains that you have made but to ensure that your usage is constantly honed so that you cut down on wasted time and effort, catch issues early and prescribe remedies so that you keep control. We see prevention being better, cheaper, and more effective, than the cure.
Hydra Management see clients taking an annual health check, starting around six to twelve months after the system has gone live. It consists of a structured review of your usage of the system and provides a series of recommendations and advice for you to implement.
The health check is product focused and has the following key activities:
Scene setting: This is for Hydra Management to spend time with the Hydra Administrator and ideally, product sponsor, to identify what initial benefits were expected from the system and to understand the immediate and future rollout plans. This will then be used to compare progress and potential when working with other people later in the health check.
Current usage: This is where Hydra Management work with the Hydra Administrator and project sponsor to understand areas such as:
What was purchased and what is being used, what gaps exist and why?
What processes are in existence around Hydra, such as timesheet entry and timesheet acceptance?
What is the frequency and accuracy of plan updates within the organisation?
How often are plans published?
What plan and task structure is now in use?
What is the Standards and Guidelines status; have things moved on since 'go-live' and have they been documented?
What archive and purge process is used or planned?
One on One meetings: This is where Hydra Management gains the detailed knowledge of how the system is being used, comparing what is expected to the way things are done in reality and comparing back to the expected initial benefits. This would involve Hydra Management meeting with different roles within the organisation and should encompass, Program Manager, Project Manager, Resource Manager, Functional Manager, Line Manager, PMO, Timesheet User and Finance. These meetings should be no longer than one hour with each person.
Reporting: This is where Hydra Management gain an understanding of the effectiveness of reporting, how they are produced and what the needs are. This is likely to be done as part of the one to one meetings.
Environment: Here Hydra Management will look to see if there are any current issues around the logical and physical configuration of the Hydra implementation and to see if steps are needed to improve the current configuration.
Report construction and walkthrough: Hydra Management will consolidate the work done into a report and make recommendations that will be discussed at a review meeting to agree the actions that need to be implemented.
Recommend this page