How to Develop a Knockout HRMS Project Plan
Every HRMS project should have a detailed and thorough plan. Fail to plan, plan to fail. In some ways, we could argue that an HRMS project needs such a plan even more so, as they are often the combination of two very different functions: Human Resources and Information Technology. As well as ensuring that these two sides work together, a documented and agreed up HRMS plan can alleviate any confusion or misunderstandings.
How do we go about creating such a plan? What do we need to document in our HRMS project plan?
The Scope Document
Before we begin our knockout HRMS plan, we need to start with a scope document. It should be used to obtain agreement from the stakeholders that the HRMS project is needed. It should include the business requirements behind your HRMS project and well as your objectives or the end goals to be achieved. As well, it will often have key milestones and deliverables. A typical scope document for an HRMS Project Plan may be ‘The Implementation of a Recruitment System’ with the objectives being: to achieve cost savings and improve efficiencies through one global HRMS. Key milestones in our scope may include an HRMS go-live date, as well as other high level dates such as completing design and testing.
Recommended reading: HRMS implementation: 9 steps to success
Next, you need to take the scope document and build out the details, you do this in the HRMS project plan. It is here that you include each and every task, along with the timing and the resources needed. You also need to connect these tasks, so that you know which can happen at the same time or where you have prerequisites. This plan will enable you to see an overall schedule and see where your business is over or underutilized and where additional resources such as HRMS consultants may be needed. An HRMS project plan also needs to plan around the yearly schedule of HR. For example, many HR departments are busy during year end or benefits enrollment periods. We need to adjust our project plan so that we do not include intense weeks of testing that overlap during these periods. Don’t forget to include holidays too!
A tip: Don’t forget to monitor accessibility of your HRMS project plan, as well as communicating the projects goals to the stakeholders, the plan should be readily available for your employees and other individuals working on the project. While a basic tip, if you are working with outside HRMS vendors, consultants or offshore resources, not everyone always has the same version of MS Project!
What to expect when your HRMS vendor is bought out by a larger company
Tips on what to do when your HRMS vendor is involved in a merger/acquisition with another company
Can you calculate the useful life of your HRMS?
Your HRMS’ useful life is an important consideration when selecting new software - but how accura...
Is a BYOD HRMS strategy a bad idea?
A bad BYOD HRMS strategy can go wrong - here's how to avoid common pitfalls