Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Programming IT Technology

Web 2.0 Lessons For Corporate Dev Teams 142

Posted by CmdrTaco
from the august-came-early-this-year dept.
jcatcw writes "Quick, incremental updates, along with heavy user involvement, are key characteristics of the emerging software development methods championed by a new generation of Web 2.0 start-ups. A survey conducted for Computerworld showed that an overwhelming majority of the respondents said that traditional corporate development teams could benefit from Web 2.0 techniques, specifically the incremental feature releases, quick user feedback loops and quality assurance programs that include users. Fifty seven percent of the respondents said problem-solving and analytical skills will be key requirements for next generation developers. The bottom-line: corporate development teams need to get to know their users."
This discussion has been archived. No new comments can be posted.

Web 2.0 Lessons For Corporate Dev Teams

Comments Filter:
  • Prior art (Score:5, Informative)

    by heffrey (229704) on Monday July 21, 2008 @01:37PM (#24277423)

    This is called "agile development" and pre-dates Web 2.0 by around 10 years. Taco's having a bad day it seems.

  • Re:oh comon (Score:2, Informative)

    by lethian (1288114) on Monday July 21, 2008 @01:53PM (#24277673)
    I believe Meebo.com uses this development method. It seems to work well for them.
  • Re:oh comon (Score:5, Informative)

    by dubl-u (51156) * <2523987012@nOspam.pota.to> on Monday July 21, 2008 @02:33PM (#24278251)

    I wish all this was true. Incremental and fast and includes clients. Sounds like a recipe for disaster to me. Sorry but I really have not seen development teams using such methods successfully.

    Works for me. It requires supporting disciplines, though. In my view, that includes a well-meshed team, a very disciplined product management process, strong automated testing, a relentless devotion to code quality, and continual examination of your architectural choices.

    It also works for plenty of other people. Flickr released every few hours, and they ended up selling for $20m after 18 months of work. YouTube releases once a week for interface changes and once a month for database changes, and they always have. At a billion views a day, I'd call them pretty successful.

You will have a head crash on your private pack.