A practical example of the introduction of code inspection

Since our previous topic with a description of the process of introducing code inspections in our company aroused some interest in the habrasoobschestva, we decided to write an extraordinary continuation. Today we will consider an example of implementing this practice on a specific project.

Consider the introduction of code inspections by the example of the project and the structure of the project team. The team consists of two groups: in one of them there are two developers and a manager, in the other - three developers and a manager. Developers will be denoted by the letter D (Developer), and group leaders by the letter L (Lead).
')
Define the composition of the groups.
Group 1: D_1_1, D_1_2, D_1_3, L_1.
Group 2: D_2_1, D_2_2, L_2.

We fix the inspectors behind the project tree.



trunk / module_1 - group 1 responds.

trunk / module_2 - group 2 responds.

trunk / common - the overall responsibility of both groups, specific inspectors are assigned by the head from among the members of their own group.

The developer writes code that affects the modules of both groups.

1. Developer D_1_2 solves some problem and in the solution process writes code that affects the following paths: trunk / module_1 / dev_1_1, trunk / module_2 / dev_2_3.

2. D_1_2 creates an inspection and adds the following participants.



3. The head of L_2 appoints developer D_2_3 as inspector.

4. The final table of the inspection participants looks like this.

The developer writes code in a common module.

1. Developer D_1_2 solves some problem and in the process of solving it writes code to trunk / common.
2. D_1_2 creates an inspection and adds the following participants.



3. The head of L_1 appoints himself an inspector.
4. The head of L_2 appoints developer D_2_1 as inspector.
5. The final table of the inspection participants looks like this.



Of course, starting the code inspection process within a small group of 6–7 developers is one thing, and scaling up the process to a large project that dozens of developers are working on is a much more difficult task, but still doable.

The next article (as we promised in the first topic ) will be devoted to the process of automation of inspections using CodeCollaborator.
See you again!