Intention for responsible handover - handover @ ウィキ

Hiro has been in charge of account settlement system for many years, but he recognizes that his change is about to be near soon

Specifications and program design documents to be handed over exist, but old information, unnecessary information, etc. remain. If Hiro just takes over as it is, he can not succeed the necessary knowledge efficiently to the successor.

Hiro has not received the appointment yet, but has the consciousness as above.
It is possible for Hiro to make modifications for handover documents between work.
Since old information and unnecessary information might be necessary, it can be kept without deleting it.

Think handover as a project and consider it as a life cycle of selection of necessary knowledge (request definition), concept of the document (design), creation of handover document (implementation), information update of the created document (maintenance)

Hiro thought what kind of information and documentation in the financial system should be handed over to the upcoming personnel change. He created documents and made modifications as soon as corrections occurred to the created documents.
As a result, Hiro had sufficient responsibility for handover and was able to do it systematically. Since Hiro constantly maintenance the handover documents, he was able to deal with sudden personnel changes.

Update history or Quick correspondence for the review are used to support responsible projects.
Sometimes a third party urges the responsible project to be executed by using Timing of appointment.
With this pattern, the predecessor always prepares to hand over the document. It helps in executing patterns that require time such as Incremental takeover or Mentor for successor .