Developer Handover Checklist

Every now and again you need to hand something over (code, thingamabobs, whatnot) to someone. At these times it can be good to have a checklist to go through. This is the list that I tend to use. All points are optional and users should strive for good enough. I've based it on architectural views as defined by Kruchten and others (C4 or some other scheme will work just as well).

Item

Description

Example

Business Case

An overview of the major business cases that motivate the existence of the solution.

Our customers must be able to make "claims" when they receive a defective gizmo from us.

Conceptual Model and Processes

Walkthrough of the conceptual model that is used in the solution. This includes the various business entities and the processes involved.

Entities: claim, receiver, productProcesses: make a claim, close a claim, refute a claim

Functional/UC View

A walkthrough of the functional view and the use case view with one or two typical use cases and also the more complex use cases that need to be explained in more detail.