| Project Name | [HR Tech Implementation Name] |
|---|---|
| Project Manager | [Name] |
| Start Date | [Date] |
| Target End Date | [Date] |
| HR Tech Platform | [Platform Name] |
| Project Mgmt Tool | |
|---|---|
| Comms Tool | |
| Documentation tool/repo |
| Metric | Baseline | Target | Measurement Method |
|---|---|---|---|
| System adoption rate | N/A | 80% first month | Login frequency analytics |
| HR/People Team process efficiency | |||
| Data accuracy | |||
| User satisfaction |
<aside> [Describe the primary goal of implementing this HR technology and the value it will bring to the organisation, whats your north star? Remember, keep the end-user in mind. This will help with user uptake.]
</aside>
| Role | Name | Department | Responsibilities |
|---|---|---|---|
| PeopleOps Lead | HR | Define requirements, validate solutions | |
| Head of IT | IT | Technical implementation, APIs. | |
| End User Representative/Champion | Various | Provide feedback, user testing | |
| End User Representative/Champion | Various | Provide feedback, user testing | |
| End User Representative/Champion | Various | Provide feedback, user testing | |
| Vendor Contact | Tech Provider | Technical support, training |
<aside> [It’s always best to put in a reoccurring meeting, at the same time, for no more than 15 mins to go through what you’ve done, what you’re working on today, and if you have any blockers. If you find that this is too much, you can take it down to once per week.] Meeting Time: [Time] daily/weekly Duration: 15 minutes Questions What did we accomplish yesterday? What are we working on today? Any blockers?
</aside>
[This is where you’d review the sprint and have a Retro on what’s been done so far. There are loads of Retro methods, but to keep it simple you can just stick to what went well, when didn’t go well, and how to improve in the next sprint.]
| Retro Date | Sprint # | What went well? | What didn’t go well? | Improvements/actions for next sprint |
|---|---|---|---|---|
<aside>
[It’s always best to have a checklist to ensure you’re ready for the go-live, this is going to be a big day, so anything you can do to mitigate errors or issues is going to help! These are just some examples but you should create one specific to your own go-live.]