The developer shall plan and take part in joint (acquirer/developer)
technical and management reviews in accordance with the following
requirements.
Note: If a system or CSCI is developed in multiple builds, the types of
joint reviews held and the criteria applied will depend on the objectives of
each build. Software products that meet those objectives can be considered
satisfactory even though they are missing information designated for
development in later builds.
5.18.1 Joint technical reviews. The developer shall plan and take part in
joint technical reviews at locations and dates proposed by the developer and
approved by the acquirer. These reviews shall be attended by persons with
technical knowledge of the software products to be reviewed. The reviews shall
focus on in-process and final software products, rather than materials
generated especially for the review. The reviews shall have the following
objectives:
a. Review evolving software products, using as
criteria the software product evaluation criteria in Appendix D
; review and demonstrate proposed
technical solutions; provide insight and obtain feedback on the technical
effort; surface and resolve technical issues.
b. Review project status; surface near- and long-term risks regarding
technical, cost, and schedule issues.
c. Arrive at agreed-upon mitigation strategies for identified risks, within
the authority of those present.
d. Identify risks and issues to be raised at joint management
reviews.
e. Ensure on-going communication between acquirer and developer technical
personnel.
5.18.2 Joint management reviews. The developer shall
plan and take part in joint management reviews at locations and dates proposed
by the developer and approved by the acquirer. These reviews shall be attended
by persons with authority to make cost and schedule decisions and shall have
the following objectives. Examples of such reviews are identified in Appendix
E
.
a. Keep management informed about project status, directions being taken,
technical agreements reached, and overall status of evolving software
products.
b. Resolve issues that could not be resolved at joint technical
reviews.
c. Arrive at agreed-upon mitigation strategies for near- and long-term
risks that could not be resolved at joint technical reviews.
d. Identify and resolve management-level issues and risks not raised at
joint technical reviews.
e. Obtain commitments and acquirer approvals
needed for timely accomplishment of the
project.
