Choo will be doing a feasibility study later this summer. Pros and cons of using the database were discussed. We agreed that there is sufficient good use of the database in OPUS that we should not try to eradicate its use completely, but that we should probably schedule a project to get rid of unnecessary relations. The most important result of the development cycle discussion was the generation of a checklist to be followed throughout code development, review, and testing. This checklist is going to be put on the DPT Web pages, and will be made available in a team CMS library for extraction into the OPR, to remind developers what documentation and activities they should complete.
Testers also have some responsibilities in the checklist.
Testing was discussed at length. We recognize that the DPT documentation is not in good shape right now. A task force was formed before the retreat to address documentation. It had made some good progress, but full implementation is not yet complete. The retreat served to give the entire team a forum to determine what should go on our Web pages, although exact formats and other details were left to the task force.