Country: Mexico
You are in the Mexico edition. Type your country to switch.
Nigeria
The Americas
Loading every country…
No country matches. Check the spelling, or choose "Any country" for the Global edition.
You are learning in the Mexico edition, with examples in pesos and from Mexico.
Your learning profile
Human resources and technology · Lesson 5 of 9
Implementing an HR system
Implementation is where an HR system succeeds or fails. This lesson covers the governance and decision rights a project needs, lays out the phases on a worked timeline, plans data migration with cleansing and mock conversions, distinguishes the types of testing including payroll parallel runs, and follows cut-over, go-live and hypercare through to the common points of failure.
This lesson is complete in writing. A video for it is on its way.
What you will learn
- By the end you can describe the governance an HR system implementation needs and who decides what.
- You can name the phases from design to hypercare and lay them out on a realistic timeline.
- You can plan a data migration with cleansing and mock conversions, and measure its quality.
- You can distinguish the types of testing, plan a cut-over and recognise the common points of failure.
Key terms in this lesson
- Project sponsor
- The senior person who owns the business need for a project, secures its funding, champions it in the organisation and makes decisions beyond the project manager's authority.
- Change control
- The formal process by which a proposed change to a project's scope, schedule or budget is recorded, assessed for impact, approved or rejected, and then built into the plan.
- Data migration
- Moving records, history, balances and reference data from old systems into a new one by extracting, mapping, cleansing, loading and verifying them.
- Mock conversion
- A full rehearsal of a data migration into a test copy of the new system, measured and reconciled like the real load so problems are found in time.
- Parallel run
- Processing the same pay period in the old and new systems from the same inputs and comparing every result until the differences are explained and within tolerance.
- Cut-over
- The planned, rehearsed sequence of tasks that moves an organisation from the old system to the new one, from the data freeze to opening the new system to users.
- Hypercare
- A period of intensive support immediately after go-live, with extra staff on hand to resolve issues quickly while users settle into the new way of working.
- Lessons-learned review
- A structured meeting at the end of a project, or a phase, where the team records what went well, what did not and what the next project should do differently.
- Step 1: Governance and sponsorship, not started
- Step 2: The phases and a worked timeline, not started
- Step 3: Data migration and cleansing, not started
- Step 4: Testing: types and who does them, not started
- Step 5: Cut-over planning and go-live, not started
- Step 6: Hypercare and the common failure points, not started
About 12 min of reading
Step 1 of 6
Governance and sponsorship
Opening this step…
Step 2 of 6
The phases and a worked timeline
This step opens when you finish the one above.
Step 3 of 6
Data migration and cleansing
This step opens when you finish the one above.
Step 4 of 6
Testing: types and who does them
This step opens when you finish the one above.
Step 5 of 6
Cut-over planning and go-live
This step opens when you finish the one above.
Step 6 of 6
Hypercare and the common failure points
This step opens when you finish the one above.
Key takeaways
The key takeaways open when you finish every step.
Lesson quiz
5 questions. You need 85% to pass.
The quiz opens when you finish every step.
Read first
Stockertim Learn is education. It explains how investing works and never recommends buying or selling anything.
Popular in Mexico: Financial markets law and regulation: foundationsProtect your money and accounts