The previous post was all about HRIS requirements definition. Having been through this process a fair few times I’d recommend once you have gathered the business requirements that you take a step back.
Bring your focus back to the Project Vision and assess the requirements in light of that Vision.
- Does the requirements document reflect the changes you are seeking?
- Are there gaps in the requirements definition which need to be filled/articulated?
- Are there requirements listed that are realistically not within the remit of the function?
- Is the language clear? Any chance of misunderstanding the requirement statements?
- Have you prioritised all of the requirements – MoSCow or similar.
This reality check is very useful before you step into the next set of activities and will save you time later on.
While you take this time to assess the requirements it’s worth while also establishing a set of project principles and/or a benefits tracking process. I hear you say – ‘what on earth is this for?’
Think about the future you. You have selected the solution which ‘fits’ your business. You are in implementation mode. The pressure is on. There will be countless deadlines, business change, data collection, testing, training, the list goes on. The clock will be ticking! During implementation you will find yourself under pressure to make decisions quickly. Decisions which could have a major affect on the performance, usability and effectiveness of your new HR System.
Here are a two approaches which should help with this.
- Look back at the data you collected on solution benefits. What are the stated benefits for the project? Will the decisions you make during implementation have a negative impact on the benefits? If you are interested in benefits realization and all that is involved please check out the following article by the PMI as a good starting point.
- Create/agree the project principles with your Project Manager (if you have one)! The principles shouldn’t be long or particularly onerous (4 or 5 bullets) as they are more like an aid memoir for when you are in the thick of things. Some examples below,
- Ease of use and accessibility is paramount
- Automate ahead of manual intervention
- Use configuration and functionality ahead of customization
- Simplification of process
Will the decisions you make during implementation provide short term solutions to project difficulties but result in long term consequence for the business such as loss of functionality, quality, benefits?
What is the point of the project if the benefits you wished to attain have been lost/eroded along the way?