Difference between revisions of "Code Review Workflow"
From Agility
| Line 4: | Line 4: | ||
| − | [[File:onetooneworkflow.png]]</li> | + | [[File:onetooneworkflow.png|none]]</li> |
<li>Responsibility of task owner (developer / tester) is to create review and assign to it Reviewer</li> | <li>Responsibility of task owner (developer / tester) is to create review and assign to it Reviewer</li> | ||
Revision as of 07:20, 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 (developer / tester) 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
- Author close review
