News for hackers. Stuff that matters.
Re:Release Late, Release Rarely (2006) by ams6110 on Tuesday October 13, 2009 @10:19PM (#880517)
And I would add, release early and often only if releasing is easy. I worked in an shop that was trying to be "agile" with an enterprisey consultingware kind of product. They tried to release every 6 weeks or so, but the releases were complicated to deploy and deployments were additionally complicated by their customers' own change management processes that made the releases flow like cold molasses.

They ended up with releases backed up two or three cycles at some customer sites, customers who could not cope and only wanted every other (or every third release), which created a support nightmare and customers who felt the software was in a never ending state of flux.

So, if your releases involve a "download this zip file and extract it here" kind of process, it's a lot more feasible to do the early/often thing. If your releases require dispatching an engineer on a site visit, maybe not such a good idea.

There are no comments on this comment yet.