Skip to end of metadata
Go to start of metadata

Most people, whan asked, agree that releasing often is a good thing. Unfortunately, most people will also say that in their particular project it is not possible to release often. The reasons they provide will vary but often there is an underlying assumption that a great deal of functionality must be developed before anything can be released. Replacement projects are particularly prone to this kind of thinking, often driven by promises of Painless transition and big bang release strategies.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jun 21, 2010

    One thing to note in these environments is that frequent releases will fail if the organization is actively working against a frequent release strategy, as expressed in "It won't work here". Care must be taken in introducing such changes in hostile envoironments