Page 281 -

TABLE 11-1. Inspection script for multiple organizations (continued)
Name Inspection script for use in multiple organizations
Basic Course of Events 1. Preparation. The moderator distributes a printed or electronic version of the work product
(with line numbers) to each inspector, along with a checklist to aid in the review. Each
inspector reads the work product and identifies any defects that must be resolved,
compiles those defects into a single document, and returns it to the moderator.
2. Compile the draft inspection log. Each list of defects returned by each inspector must be
compared with the others, in order to identify and combine overlapping defects. The
moderator compiles a draft of the inspection log that includes all distinct defects found by
inspectors. The log does not yet contain any solutions to those defects.
3. Identify conflicts. The moderator searches for any defects reported by different inspectors
that contradict each other. For each set of conflicting defects, the moderator holds a discus-
sion(either in person,via teleconferenceorvideoconference,or usingacollaboration tool
like a mailing list or instant message system) between the inspectors who identified those
defects, in order to identify the assumptions behind the defects and resolve them into a
single defect. The inspection log is updated to reflect the combined defects.
4. Identify solutions. The moderator uses the same means to meet with individual inspectors,
to identify solutions to the defects and add those solutions to the inspection log. If more
than one person identified the same defect, they must all be involved in creating the solu-
tion. Inspectors may also identify additional defects that were not originally found, as well
as their solutions.
5. Compile and distribute inspection log. The moderator compiles all solutions identified in
Step 4 into the inspection log. Any defects that were not resolved are left as open issues to
be resolved by the author. The moderator sends the final inspection log to all inspectors
for confirmation. When the inspectors have confirmed that the log is correct, it is sent to
the author of the work product.
6. Rework. The author repairs the defects identified in the inspection meeting.
7. Follow-up. Inspection team members verify that the defects were repaired.
8. Approval. The inspection team approves the work product.
Alternative Paths 1. During Step 5, if one or more team members find errors in the inspection log, the moder-
ator must address those errors before rework can occur. The script returns to Step 2.
Exit Criteria The work product has been approved.
While not every work product can be inspected, every work product in your project
should be reviewed. Use deskchecks to have people in your organization spot-check the
work done by vendors. This will help to find errors early on, and it can also generate con-
fidence within your project team. If you are on top of the errors in your project, you can

quickly correct problems if things start to go off track. There should be no surprises when
delivery time comes.
In addition to inspecting work products, it is important to encourage the team within your
organization to mentor their counterparts in the outsource vendor (and vice versa!). The
more the two teams learn from each other, the less they will make mistakes or blame one
another when things go wrong. The project manager of an outsourced project should try
to create a cohesive team for the project that spans both organizations. While your team
members may be paid by different organizations, they are all working toward the same
goals and should feel comfortable both criticizing and praising each other’s work.

MANAGING AN OUTSOURCED PROJECT 273