During the Build and Fix as well as the Shipment stages you can expect to receive feedback regarding your reviews, releases and shipments and you will need to demonstrate progress towards fixing any prioritised changes and fixes required to the shipment. You will assign priorities to the incidents and high priority incidents need to be fixed prior to lower priority fixes unless of course the area of change required is already undergoing fix work and is an agreed straightforward change. It is important to differentiate high priority incidents from Emergency fixes. Emergency fixes are changes required to post implementation shipments.

We manage the fix process using the Build and Fix List which is described in detail elsewhere in the Toolkit. However, this is an uncomplicated fit for purpose artefact that works and gets demonstrated to all the attendees of the Daily Forum. For the sake of simplicity we suggest using the SeSiSNo incident statuses as used in Emergency Incident Management.