Knowledge Sharing Pattern Language

Problem	The delivery of (intermediate) work results between the customer and the supplier has not been organized or is not working well.
Initial Context	A new project has been started and Shared Understanding (KSP05) exists between the customer and the supplier about the expected results.
Roles	A Project Manager representing the project and a customer contact person accepting the work results.
Forces	Based on the shared understanding of what the work results from the project shall be, the ways of delivering the work results must be defined, for example, by using certain configuration management tools.
Solution	Define together with the customer the releasing procedure and tools. Suggest the organization's standard if applicable. It is adequate to define this once if there are not bigger changes during the project affecting this. Based on what has been agreed on with the customer, plan internally, how the releases are implemented. Look also at possibilities to automate this procedure (including required testing) and initiate actions for that. Prepare releases. Release can here mean from one to many artifacts planned to be delivered to the customer. It can be a large software release or a single document. Prepare the releases according to the procedure. Internal review. Internally accept releases and initiate transfer of those to the customer. Deliver to the customer and Receive Delivery. The customer evaluates the release and gives feedback. In the case of official delivery, the feedback shall include approval (or complaint). Process feedback. Initiate actions if any additional actions are required based on the feedback. In case the customer also delivers something to the supplier, this procedure should work also for that. Just to change the role names.
Resulting Context	A project where the customer and the organization effectively share work-result knowledge between each other.
Instances	The procedure definition to be implemented at least once for every project. During project realization the releasing to be implemented once per each relevant (document and/or software) release. One potential pitfall is that releasing needs to be made often, but the procedure required for it is too massive and too time consuming.
Process Connection	Project Management.