- If management has instituted an acceptance criteria - such as no new static analysis defects, then naturally developers will be evaluated based on whether they fix static analysis defects. A developer analysis gives power to the developers to find and fix problems locally before it becomes publicly visible in a system analysis.
- Finding and fixing problems before check-in makes the codeline higher quality. Rather than checking in potential bugs, the code can be cleaned earlier. Everyone pulls from higher quality code, particularly in agile and continuous integration environments.
- Giving developers analysis results right when they want it increases efficiency. Rather than waiting for the nightly or even weekly results, minimizes context switching. In addition, fixing a problem can generate another problem. Being able to iterate multiple times quickly at one time is much more efficient than fixing and then waiting a day or even a week to see if no new problem has been created.
Desktop analysis is also an extra flow that requires additional time and training. However, many would say that it is a small price to pay given the benefits.