13. Ad hoc
Just ask someone
Takes only a few minutes
Happens everywhere
Little impact beyond problem
Completely informal
13
14. Peer deskcheck / passaround
Asking someone for input
Can be done asynchronous
Author is not present
Good for mentoring and coaching
Very informal
14
15. Pair programming
Agile approach
Driver and navigator
Rapid iterations
Cultural change needed
Informal review
15
16. Walkthrough
Author explains code
Code reading
Ideal to present and educate
Risk of overlooking critical code
Informal, no defined process
16
17. Team review
Used to judge product
Check against specifications
Preparation needed
Review collects data and input
Planned and structured
17
18. Inspection
Most formal approach
Industry standard
Specific roles and trained inspectors
Checklist
Moderated review
18
19. “Inspection Walkthrough”
Reader doesn‘t know code
Experienced dev for „eagle eye“ view
Author explains and answers questions
Specific code section
No leads involved
19
21. Egoless!
My ego is not tied to my „perfect“
or „imperfect“ work product.
21
22. Avoid the dragons
No fingerpointing
Leave the egos at the door
Resistance to change
Lack of knowledge
Cultural issues
22
23. Some things to keep in mind
Three to seven participants
Not longer than two hours
Manager should be involved in planning
Find problems, not solutions
Review coverage vs. project size
23