Feedback Closure

Pam had suggested originally to Susan  that if she gave the info to Pam in a file that it may be quicker to resolve if it had to be rekeyed. However Susan didn't think she would need to correct the 50 records more than once!

So a learn for next year.

• Next year create a file incase it needs re-run as it did this year and resulted in having to manually key them in twice

---

14-Oct-15 HI Anne,

The following Jiras will be carried over to next year. Assuming that no other issues arise with this year's return then the project can be closed - from my point of view anyway.

HRS085-20 - this can be resolved next year and should remove the necessity to load large volumes of updates via spreadsheets.

HRS085-29 - unsure as to the status of this. It happened last year and was resolved but I was not involved with the issue at the time. John might know as indicated on the Jira.

I will consider if there is anything to put into the learns for next year.

Cheers,

Pam

------

27-Oct

Spoke to Susan McK

She has no comments, happy that I include the learn items above.

Also save all the time until we close te project and hte final submission has been completed, as we were caught out last year just before the final submission.

------

Susan McK ,mentioned that at a meeting with Martyn that they both are looking to spread the knowledge. Wrote it in bothe Susan McL and Mike both want it changed.

-------

11-Nov

Susan McL asked for PICCL 7 to be removed from Closure and updated that the 50 rekeying was the only was as there was a file for the 1000, so not a lesson learned just a PICCL

Susan also mentioned that HR are putting in place spreading the knowledge and that Martyn didn't expect to sign off Closure

----

12-Nov

Mike also said contingency in place and the extent of sharing the knowledge in the team will doulve the developers required, so updating the KLP in Clolsure