Releasing early and often... how it failed for us

Re:Releasing early and often... how it failed for us by gnaritas on Thursday March 12, 2009 @11:35AM (#513556)

It was not started by 37signals, it was popularized by them. The practice has been around much longer as part of extreme programming, as have most of the things they preach.

The 37signals guys are great marketers but about the only thing unique to come from them, the only practice they actually created, was convention over configuration as a core principle. Everything else they just picked up and repackaged from existing extreme programming principles.

[ Parent | on HN ]

Re:Releasing early and often... how it failed for us by spolsky on Thursday March 12, 2009 @01:09PM (#513711)

It's way earlier than Extreme Programming. Believe it or not, it was once considered a part of Object Oriented Programming. Here's an article from IBM Systems Journal 1993 where I first learned the idea of ship early and often:

http://www.research.ibm.com/journal/sj/323/ibmsj3203E.pdf [PDF]

[ Parent | on HN ]

Re:Releasing early and often... how it failed for us by jhancock on Friday March 13, 2009 @04:14AM (#514637)

I'll add that "Extreme Programming" and other forms of Agile is mostly a buzzword/re-branding to wrapper quite a few "best practices" from the OOP world. Which is appropriate since so many of the early agile manifesto folk were the same ones that pioneered the OOP best practices.

[ Parent | on HN ]

Re:Releasing early and often... how it failed for us by gnaritas on Friday March 13, 2009 @01:08AM (#514530)

Oh I believe it, I wasn't trying to imply the practice came from extreme programming, only that that's where I encountered it first.

[ Parent | on HN ]