http://blogs.msdn.com/micahel/archive/2006/05/17/WeightLossForSoftwareDevelopment.aspxMary Poppendieck opened STAR East this morning by asserting that "Your development and testing processes are defective". Mary has long been a proponent of lean software development. She maintains that if you routinely find defects during verificationen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/micahel/archive/2006/05/17/WeightLossForSoftwareDevelopment.aspx#600716Thu, 18 May 2006 09:34:58 GMT91d46819-8472-40ad-a661-2c78acb4018c:600716anuttharaHow is this different from Agile development? In the current feature crew model for Orcas, is this not what we have set out to do? <br> <br>However, I would like to know how you think testers can do software inspection effectively and real world examples if you had any. I am trying to get my team to do code and spec inspection for the coming product cycle and would really love to know any best practice around that.http://blogs.msdn.com/micahel/archive/2006/05/17/WeightLossForSoftwareDevelopment.aspx#601094Thu, 18 May 2006 19:20:06 GMT91d46819-8472-40ad-a661-2c78acb4018c:601094micahelLean is one form of Agile, so in many ways Lean isn't any different than Agile. The new feature crew model that DevDiv has started using is a great move towards Leanness. We still have a ways to go however - especially in the Fix Or Won't Fix Right Now area. <br> <br>There are several good books on code inspections; Keith Stobie has published some great information in this area as well. The way to start, though, is to just start. Grab that spec and go through it line-by-line, by yourself to start with and then in a group. Code can be harder to inspect, just because you have to figure out what it's doing. But that can be a good thing - if you can't figure out what the code is doing then you know something very important about that code! <br> <br>No specific examples come to mind just now, but I'll add them later if I think of any.