Difference between revisions of "Code Review Workflow"
From Agility
| Line 5: | Line 5: | ||
[[File:onetooneworkflow.png|none]]</li> | [[File:onetooneworkflow.png|none]]</li> | ||
| − | <li>Responsibility of task owner ( | + | <li>Responsibility of task owner (Assignee) is to create review and assign to it Reviewer</li> |
<li>There is no general rule for Reviewer selection it is agreement between Task Owner and Reviewer (agreement can be made on Daily)</li> | <li>There is no general rule for Reviewer selection it is agreement between Task Owner and Reviewer (agreement can be made on Daily)</li> | ||
<li>After positive review (or settlement with Reviewer ;-) : | <li>After positive review (or settlement with Reviewer ;-) : | ||
*Reviewer complete review | *Reviewer complete review | ||
| − | * | + | *Task owner close review |
</ol> | </ol> | ||
Latest revision as of 07:26, 13 October 2017
- We are using Crucible software for code review and also for general review of non svn tasks (if required)
- Our workflow is based on One-to-One Reviews (without moderator).
- Responsibility of task owner (Assignee) is to create review and assign to it Reviewer
- There is no general rule for Reviewer selection it is agreement between Task Owner and Reviewer (agreement can be made on Daily)
- After positive review (or settlement with Reviewer ;-) :
- Reviewer complete review
- Task owner close review
