L2: Project Review Record guidance

1. Purpose of the Project Review Record document

This document is updated incrementally at the end of each increment. It is used to capture feedback from the review of the solution; to capture learning points; and, if appropriate, to describe benefits. Typically the analyst in the project is responsible to keep it up to date and to align with project management tools (e.g. ActiveCollab, Jira) used by the development team and by the lab and project managers to monitor progress, guide communication with partners, check deadlines are respected, track time estimates on a task and against the overall project budget. The template can be shared with partners in its entirety and/or following each review meeting with partners, shared as a snippet recording progress for each specific increment.

2. Completing the Project Review Record

2.1. REQUIREMENTS

In this section the prioritised high level requirements extracted from the Product quote and/or as modified at the kick off meeting are added as reference to guide the timebox and increment plans.

2.2. RELATED RESOURCES

If applicable, a list of links to other documents or resources such as Product quote or external sites of reference are added here.

2.3. INCREMENT

2.3.1. Timebox Plan

For those cases where the development of an increment has been plotted in a defined timebox across the duration of the project, information on dates can be added here.

2.3.2. Timebox Review Record

Here dates of review meetings (whether internal to the development team or with partners) for the increment can be recorded.

2.3.3. Review of the delivered solution

This section typically contains two lists, one which records and confirms what has been delivered and one on what has not yet been tackled. These lists of requirements (with sub-requirements as appropriate) should align both with the reference requirements above as well as any additions in the task management tool being used by the development team.

2.3.4. Learning points

This section is filled in during internal and partners-facing review meetings. It is typically focused on the process, practices employed, contributing roles and responsibilities, important changes to the solution architecture and design process. It also represents a record of decisions taken, reprioritisation of requirements when needed and any other important concise documentation on project development.

2.3.5. Research benefits

The benefits that should accrue incrementally from the solution delivered are listed here and summarised to the partner, if appropriate, during the review meeting when the increment is discussed.

Copyright Agile Business Consortium Limited.

Download Fig. 5