> I agree, but is there a way that could happen without slowing the process to a crawl? I don't see why a more rigorous release process would slow progress dow

> I agree, but is there a way that could happen without slowing the process to a crawl? I don't see why a more rigorous release process would slow progress down at all. All the iterations that lead to progress should be done on test vehicles, not customer vehicles. "Move fast and break things" is a development model that should only be applied to low-importance, low-risk systems. Most software development work occurs on such systems, and I think that narrows the perspective of the software development community as a whole.