We used to have yearly releases and waterfall projects. Then we moved to monthly releases and Scrum fit just perfectly.

The Scrum Guide defines the Sprint as a fixed-length event of one month or less and as the heartbeat of Scrum: a continuous cycle of planning, doing, review, retro and repeat. With monthly releases, it is usually the release which is demonstrated, reviewed and celebrated in the Sprint Review.

But if we now move into the devops age of continuous integration and delivery, with possibly hundreds of releases every single day, is then the scrum sprint still the right heartbeat? Or should we aim for uninterrupted flow with Kanban instead? Or quarterly goal-setting with OKRs? Or both?