4. Defining your Workflow

This document describes several forms of Crucible Workflow in detail. Depending on the size of your team, there are four different ways that a development team could use Crucible for code reviews. Choose the workflow which suits your team.

Lightweight Code Commenting with Crucible (individual)

1. Author commits new work.
2. Author creates the review, and adds comments using the easy web interface.
3. Author summarises and closes the review, saving the code comments in Crucible's database, which is stored outside the repository.
   
   

One-to-One Reviews (Agile Pair)

1. Author creates the review.
2. Author invites reviewer to take part in the review.
3. Reviewer creates comments on the code.
4. Author responds to reviewer comments.
5. Follow-up comments are made if necessary.
6. Reviewer finishes own review process.
7. Author summarizes and closes the review.

For more information, see Getting Started with Crucible. The one-to-one review process with Crucible is covered in detail in this document.

One-to-Many Reviews Without a Moderator (Agile Team)

1. Author creates the review.
2. Author invites colleagues to take part in the review.
3. Colleagues respond with comments.
4. Author responds to reviewer comments.
5. Follow-up comments are made if necessary.
6. Colleagues complete their reviews.
7. Author summarises and closes the review.
   
   

Formal Group Reviews (CMM Team)

1. Author creates the review.
2. Moderator invites colleagues to take part the review.
3. Colleagues respond with comments.
4. Author responds to reviewer comments.
5. Follow-up comments are made if necessary.
6. Each discussion point is settled by the Moderator.
7. Moderator summarises and closes the review.
   
   To see a simple example of how to use Crucible with two people, see Getting Started with Crucible.