BUPreview
Open in TheBrain

Offboarding

Was ich solltest Du vor deinem Verlassen noch klären?

Was mir wichtig wäre, ist der aktuelle Stand zum Wissenstransfer und handover. Also wie steht es sowohl mit Aufgaben, an denen Du noch mitgewirkt hast und um die Fähigkeit der anderen Deine Aufgabenfelder (halbwegs ) vernünftig zu übernehmen.

Das war die Liste die wir mal erstellt hatten und dann in ein übergreifendes Dokument eingebarbeitet hatten: Knowledge Transition Plan.docx Könntest Du dieses Dokument aktualisieren und mir kurz Bescheid geben wie es aussieht mit dem Wissenstransfer?

Knowledge Transition Plan.docx

03_Offboarding

This page contains steps to take when a person leaves different circles. The circles are named in the section titel. Notice, that a person can only leave a single circle (for example by switching from Team ConTra to Team ConDa), multiple or all Circles (for example when leaving the project). Please execute all actions corresponding to all circles left by the person.

The steps only need to be taken corresponding to the circles left by the person when still being part of the Bestand Team. When the person later on continues to leave further circles, it is not the reponsibility of Team Bestand to perform the remaining steps. When for example someone leaves Team ConTra to join Team Neugeschäft, only the steps considering leaving ConTra and Bestand need to be applied. When the person later on leaves FONL as a whole the remaining FONL step is not to be executed by Team Bestand, but by Team Neugeschäft.

Leaving Team ConTra

Remove the person from the Daily Facilitator Table and from the List of potential Daily Facilitators in the Daily Facilitator section of fonl-bestand-scripts repository.

Leaving Team ConDa

Remove the person from the Daily Facilitator Table.

Leaving Team Bestand

If the person is a Backend developer, remove the person from the DevOps@Bestand Calendar. See the bottom of the page on how to achieve this.

If the person is a developer in general, remove the person from the lists of persons in charge for services. There are two lists, which need to be updated for this: Team Bestand and Tribe. Put the freed responsibility for a service on the agenda of the upcoming Dev-Exchange, so that a new person in charge for the service can be found.

Leaving FONL

Remove the persons reference (mostly by e-mail-address) from the FirmenOnline Github Repository. This step applies not only to Devs but also to domain experts and other persons as they are referenced in for example in enviromental configurations. To achieve this, use the Github search function restricted to FONL looking for the name part of the e-mail-address (for example when the person leaving has the e-mail-address extern.walter_steve@allianz.de search for walter_steve). Do not remove the persons reference from the release repositories (the repositories starting with ReleaseDokumentation_).

If the person was a maintainer for one of the microlibraries, which can be found out by looking at this list (TODO), mention the leave in the next CoP Backend and demand a new maintainer to be determined.