Guest View: The future of quality lies in productivity



Email    print   
May 1, 2008 —  (Page 1 of 3)


Managers push quality on developers the way parents push vegetables on their children. Given a choice, most kids won’t touch a lump of spinach sitting on their dinner plate. But if you blended pureed spinach into the chocolate brownies for which they always reach, your children would get the intended nutrients without your ever having to utter, “Eat your vegetables.”

During the past 20 years in the software industry, quality initiatives have come and gone, along with countless attempts to find a silver-bullet tool that would deliver quality with the click of a button. Unfortunately, there is no silver bullet. Some ideas work in theory, but few have succeeded in practice.

The major problem is that when managers try to improve quality, they unintentionally pile more work on time-starved developers. Quality tasks are introduced in such a way that they require developers to adjust their tried-and-true workflow to take on additional work. Not surprisingly, this usually isn’t well received. If developers don’t believe that learning and applying this new practice will be worth the effort, by relieving them of tedious tasks to allow them to focus on the creative work they enjoy, the practice eventually will decay. The developers probably won’t reject the new initiative outright; they will simply do it less and less until they stop altogether.  

We push these well-meaning quality initiatives without considering their effect on productivity. Quality increases productivity, we assume, but that’s not the case. If you want to introduce a quality initiative, do it in a way that doesn’t disrupt or slow the normal workflow. Otherwise, there’s little chance of achieving a sustainable quality process.

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.



Related Search Term(s): Management, software development

Pages 1 2 3 


Share this link: http://sdt.bz/32062
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
News Briefs: July 15, 2008
Enea is named to the board of CP-TA, Teradata introduces a new version of its data warehousing tool and SOA Software upgraded its Repository Manager to accommodate its Policy Manager software Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb