Parasoft CEO Adam Kolawa writes
A good workflow can make or break a quality initiative. For example, assume that someone delivers a mandate: “All code must be peer-reviewed.” If the development manager responsible for implementing the peer code review interprets that as meaning, “No developer can check in code before it is reviewed,” he is creating a tremendous roadblock in the developers’ natural workflow. This is a prime example of a quality initiative that would hurt productivity...
Read the complete The future of quality lies in productivity article to learn a more productive, less painful approach to peer code reviews.
You can also access this article at the Parasoft Resource Centers for:
Thursday, August 6, 2009
Subscribe to:
Comments (Atom)
