The Cost of Quality: Agile vs. Traditional PM
Code inspections are viewed as one of the most effective means of quality control among IT developers. They usually involve some sort of manual or static review of software source code before testing. They are an efficient means of finding software defects and result in high-quality software-based products and services. Today, they are a best practice among traditional software developers and explicitly appear as a formal phase or activity in the waterfall life cycle.
However, code inspections are an implicit, often unspoken best practice among agile project management teams. This silence has caused some people to question the quality control of the agile project management paradigm. Surprisingly, agile teams have not forgotten to mind the Ps and Qs of quality engineering--and not only continue to perform code inspections, but perform them more often. This results in even greater quality than traditional project management teams.
Code inspections are an effective means of quality control created by Michael E. Fagan of IBM in 1972. They are highly structured meetings in which a small group of peers are tasked with identifying as many defects as possible by reviewing software source code. Computer program statements are analyzed one at a time to identify as many defects before testing as possible. The use of dynamic debugging and testing alone is an inefficient means
Please log in or sign up below to read the rest of the article.