The deployment strategy depends on a lot more than that. Team size, team workload, product nature, customer expectations, average story size and complexity. Ha

The deployment strategy depends on a lot more than that. Team size, team workload, product nature, customer expectations, average story size and complexity. Hard release cadence is amateur hour (outside of major software pieces like operating systems and languages). One release method that I had to install by pulling rank (after non-stop discussions) was the "release when ready" approach. Imagine your scrum board. There is the QA column - all the stories that are currently being QA'ed. Now imagine that during a standup, the QA column is empty - everything has been tested and there are no unstable features in QA. This is when you cut a release. It can be that you release every day, or you may not release for three weeks. It worked without fail, and was insanely flexible, resistant to change in variables.