Requirements and testing can be quite challenging. Neither needs to be overcomplicated or tedious. With the proper preparation, you can create solid requirements and test plans to ensure your HCM Implementation is successful. Let’s explore what that means.
A successful project starts with accurate requirements.
Gather all your policy documentation to get started and provide that upfront to your implementation team. Ensure you have the proper subject matter experts and they are ready to discuss requirements. Come prepared for your requirements gathering session with relevant information to discuss your organization’s needs and wants.
Who, What, When?
- What are all your inputs and outputs? What information comes into the HCM, what goes out, and to where?
- Who performs which daily/weekly/monthly functions?
- When do these actions need to be completed?
- Identify specific processes, like regulatory, legal requirements, and location-specific requirements.
- What kind of analytics, data and reports do you need?
- What issues have you been struggling with?
Being diligent upfront will pay off. Poorly defined or incomplete requirements will result in difficulties during testing and problems later. Once determined, the requirements are the basis for what you will validate (test) during implementation.
You defined it. Now test it!
As soon as you finish defining your organization’s requirements, start planning your testing and writing your test cases.
Testing, or rather validation, is another critical phase in the project. When the software is ready, you must be prepared to hit the ground running and maximize the time you spend testing and validating results.
How do I start?
Identify everyone who will be part of your validation team upfront. Testers can come from each part of your organization, and diversity of roles is critical. Including your Subject Matter Experts as part of this team is a great idea. Outline expectations for each team member and ensure they allocate enough time to perform testing. Make sure each team member has attended the training for their role.
Schedule testers’ time to perform the testing. Dedicated time is best, but often, the testers still need to do their regular jobs and will need to set aside the time to test. Another tactic is to work together. Schedule a conference room and have the testers in the same room. Not only does it provide support, but it can also make it fun.
What’s a Test Scenario?
Below is a sample matrix of test scenarios with their expected outcomes. The areas to test will come from your requirements. The test cases should be detailed, describing the steps and the expected result. Writing up all the necessary test cases can take some time, so allocate the time and delegate areas or sections of the requirements to various testers.
Test end to end.
Run through scenarios covering all systems from the beginning of a total workflow to the result. Single tasks often function as expected, and testers may not find complex issues until moving to subsequent steps in the process. If possible, use data and scenarios from your current system or business process for input to test the new system. This method allows you to compare your current system’s results with the new one and analyze any differences.
Provide Details!
When reporting issues, ensure you provide all the details. Details include the steps taken, data you used as input, which requirement is not satisfied and what the expected outcome should have been. Also, prioritize the issue—focus on fixing things that block progress first.
Stay Focused.
It is important to note that you are validating requirements, not testing the software. Focus on the expected results first and aesthetics second. Continue prioritizing necessary functionality against “nice to haves” as you progress in the testing phase. This prioritization will minimize the risk of essential functionality not working once your HCM system is in production.
What you don’t find in testing will undoubtedly be found after you go live. Testing is not something you can skip or skimp on. Solid requirements and comprehensive testing will ensure that your project is a success.
Further Reading: “The Best Steps to Great User Acceptance Testing!”
At HRchitect, we are passionate about working with our clients to ensure they reach their goals with their HCM Implementation. Contact us to schedule a time to discuss your HCM needs, including Systems Assessments, Change Management, Concierge-Managed Support and Implementation Services.
About the Author
David Glassman PMP has eight years of experience performing Software Quality Assurance. And over 26 years as a Project Manager, much of that in the HCM and Workforce world. His consulting experience includes testing software and managing development, IT, and implementation projects. David has been a certified Project Management Professional (PMP) since 2004. He is a San Jose State University graduate with a degree in Business-Information Resource Management.
When David isn’t working with his clients, he is an AYSO Soccer Referee and Regional Referee Administrator. Learn more about David on LinkedIn.