3 years ago

Category: Database

This ties in nicely with Agile principals of tight and frequent feedback loops amongst developers, testers and more importantly users. However a team who’s used to releasing less often, who prefers to release well rounded full features worked over weeks if not months, might not jump head first in to this idea.

To understand the value of a new method or tool, you should probably try to put it in a context where its value is not that obvious.

Releasing often doesn’t mean that you go ahead and buy a bunch of tools and services and get them to work.

One of the worst effects of working on lengthy releases is that team members tend to get lost in their own bubble of work.