Tracking decisions from a document review meeting is lacking

USE CASE: WHAT DO YOU WANT TO DO?

Track decisions made in a document review meeting & notify the developer

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

Someone from the meeting should communicate the decisions made to everyone so that issues can be addressed and followup review meetings can assess the state of the outstanding issues.

CURRENT BEHAVIOR

verbal agreement

EXPECTED BEHAVIOR

written agreement in the change control system

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

Use the tasks in the pull request with some official label. Also use the issue tracking system when issues are unrelated to the current code changes.

FILES AFFECTED (where the changes will be implemented) - developers only

SCMP_Treeview3.doc document_review_meeting_guidelines.txt document_review_form.txt

LEVEL OF EFFORT - developers only

medium

COMMENTS

Comments (5)