Task reviews are done on Friday meetings or asynchronously. Anyone is welcome to leave review comments on a task's issue.

Initial review

When a programmer thinks a task is done they move it to ready for review. If there is an upcoming Friday review this sprint then the code will be reviewed as a group. If there isn't an upcoming Friday review in this sprint then the task's assignee should ask a teammate to review when it is ready.

If there is no feedback, the task is moved to done and closed at the end of the sprint during the sprint retrospective. If there is feedback, the task goes back to in progress and changed will be made.

Secondary review

If there is no major feedback the task can be done as soon as the changes are made, though anyone can still comment and request changes. If there are significant changes needed, a second review should be done following the initial review procedures.