“Can we release this feature?” is usually a question answered by humans, not machines. From what I have seen around, even teams that practice continuous deployment seem to take a step back to consider whether they are ready to expose new functionality to their users. My impression is that “release decision” time might vary from a couple of hours to days or longer. Surely, a stable, meaningful deployment pipeline and a team’s certain autonomy level are prerequisites to take a decision. But I was wondering, what other activities might influence such a decision and how we could reduce their time span?
Here is a list of the things I came up with.