First, or Best, to Market?



Email    print   
September 15, 2004 —  (Page 1 of 2)
How important is the notion of "first to market?" I had intended, in this column, to review VisiComp's RetroVue debugger, but unfortunately, the installed (as compared to demo'd) version was disappointing. RetroVue is a wonderful idea: a debugger that keeps a history of your execution so that you can definitively answer the question: "How did that happen?" But the shipped product simply is not good enough to be thoroughly tested and reviewed; my guess is that they were so interested in being first to market, they released too early, rendering a potentially great product disappointing. Rather than discuss RetroVue, then, let's talk about the first-to-market issue.

Putting things into perspective: Of the billion-dollar products that are endemic on today's PCs (spreadsheets, databases, word processors and operating systems), can you name any product leaders in these categories who were first to market? The first-to-market PC-based products in these categories were VisiCalc, DBASE and WordStar, and CP/M. None of these products (or the companies that created them) exist today. Being first to market often does nothing but prepare the marketplace to accept the second-to-market products. Nonetheless, the gospel of first to market pushes people to release too early.

But don't you have to establish a "beach head?" Can't you fix the problems in version 2? People subjected to a bad version 1 won't try version 2. The competition won't be sitting on its hands waiting for you to get your act together, after all. Your potential customers, remembering their experience, will try the competition first, and people will stay with the first solid product they find.

So, "first to market" doesn't matter. "Successful in the marketplace" does. And it can't hurt to get to market as quickly as possible. So how do you quickly develop a successful product? I'll answer that question with another: What does a successful version 1.0 release look like?

First and foremost, no obvious bugs. Bugs are endless, but your product will simply fail if your schedule is more important than the bug count. The best way to deal with this problem is continuous testing. I'm a strong believer of Test-Driven Development (TDD), which advocates writing tests before you write the code you're testing. TDD alone cut my development time by at least half. Without automated regression testing in place, it's simply not possible to refactor your code (improve it without changing functionality). There are lots of tools to help in testing. Erich Gamma's JUnit (www.junit.org) and its clones are everywhere. Find information about TDD atwww.agiledata.org/essays/tdd.htmlandwww.testdriven.com.




Pages 1 2 


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

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Zeichick’s Take: Looking for the best of the best of the best
It's time once again for readers to send in nominees for the SD Times 100 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