Integration Watch: Defect tracking springs to life



Email    print   
November 15, 2009 —  (Page 1 of 2)
If interest in technology were mapped to a terrain, it would be notable for its steep peaks and deep valleys. The areas of intense interest, such as Web 2.0 programming, Web frameworks, dynamic languages and concurrency, would be towering peaks; the valleys, where advances are few and the interest they generate is low, would comprise defect-tracking systems (DTS), source code management (SCM) systems, and debuggers.

But every once in a while, sleepy sectors stir to life, even spring to life. For example, I was a Jolt judge for years in the SCM category. We prayed for the most minor of innovations from year to year so that we’d have some reason to pick one of the perennial contenders.

Then, out of the blue, SCM tools became a hotbed of innovation for one year—2005—when there appeared in quick succession Bazaar, Mercurial and Git. And SCM was changed forever.

DTS has not enjoyed a renaissance quite like that of SCM. However, this year, I’ve seen more activity in this sector than usual. There have been new products entering the space and important new releases from market leaders. Before getting into these changes, I need to discuss why this market remains persistently sleepy. The reason is homegrown systems.

Almost all DTS vendors I speak with aver that their biggest competitor is not another vendor, but homebrewed systems. These range from spreadsheets and simple databases to large monstrosities that are tended by a team of programmers and administrators. It is one sector of technology where the buy-don’t-build-infrastructure dictum has not been widely accepted. And in almost all cases, this works to the detriment of the IT organization.

There are manifold reasons why writing your own DTS system is a poor idea:

•    Your developers are not producing while they’re building DTS functionality that duplicates commercial offerings.
•    The final product is likely to be highly customized to your needs but exceedingly brittle. Any change will require coding, rather than configuration.
•    Scalability is hard to establish.
•    Import and export options, support for industry-standard protocols, and hooks to other tools are rarely implemented—and when implemented are generally only the subset the organization needs right then.



Related Search Term(s): defect tracking, SCM

Pages 1 2 


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


Comments


11/15/2009 10:53:48 AM EST

Also worth mentioning in the space is devshop, which I ran across the other day. I haven't gotten a chance to play with it yet but from then intro video it seems like it has some really slick features like adjusting task estimates based in prior estimation errors.

United StatesAntonio Salazar Cardozo


Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Atlassian throws its weight behind Mercurial SCM
Development process tool company buys Bitbucket, the Mercurial-based code repository 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