A couple arguments in favour of inspections, Fagan-style: - Although it takes a brutal-seeming amount of time, many teams get a net time savings thanks to earl

A couple arguments in favour of inspections, Fagan-style: - Although it takes a brutal-seeming amount of time, many teams get a net time savings thanks to earlier bug detection. - It's a learning experience for everyone involved, so there is a deeper preventative aspect. This can be especially valuable for the new members of your team as you grow. If you do inspections, and find just one bug that would have been nasty down the line, it's easy to emotionally understand the benefits. Without that experience it's hard to be convinced that it really works. Then again, you feel awful when you go through a 2-hour inspection with four people and don't find anything severe. Be careful with Fridays, especially in the afternoon. In my experience meetings of any sort don't go well at that time. I'd suggest other weekdays around 10am or 2pm. These seem to be ideal for some reason. As for frequency of inspections, it depends on how much code you're churning out. I personally think it's reasonable to only inspect particularly challenging, complex, difficult-to-test or critical aspects of the system.