This is a great overview of different release management strategies and the practical implications: https://www.youtube.com/watch?v=IKsQsxubuAA https://www.yout

This is a great overview of different release management strategies and the practical implications: https://www.youtube.com/watch?v=IKsQsxubuAA https://www.youtube.com/watch?v=IKsQsxubuAA Not part of the talk: if you have more than 3 people involved you probably need a release schedule in terms of either scope or time. I'd personally advise you to have one even if you only have 1 person, just for a mental target if nothing else. The talk goes into studies of projects which did scope based releases and got horrible results in practice. All the ones in the talk switched to time based releases and were much happier. Also, in a software project, you can only fix either scope or time, but not both. Also, if you want to ship in a timely manner, you probably want to fix one of them, not let both float. Edit: it looks like this is his paper on the topic: http://www.cyrius.com/publications/michlmayr_fitzgerald-time_based_release_management.pdf http://www.cyrius.com/publications/michlmayr_fitzgerald-time...