Perhaps Kanban is better suited towards long-lived product development than Scrum. Perhaps there is indeed a natural progression of engineering teams adopting Scrum, then moving to Kanban.
Ditching Scrum for Kanban — The best decision we’ve made as a team
Grant Ammons

We found the discipline of Scrum very useful while we were building our Internet dating platform but as we transitioned from “build” to “maintain / enhance”, we kept bumping into the scheduling aspects of Scrum and decided to move to Kanban.

We kept the daily stand ups (although we do them asynchronously via as we are all remote working). We no longer have any formal process around “grooming” or “retrospectives” — instead we do those as and when we feel the need. Our release schedule is usually somewhere between two and four weeks but occasionally we’ll run to six weeks — removing the fixed cycle has been very liberating! We can also release much more often if we want to: I think we’ve done up to three production releases in a day, but having a couple of releases in a week, to get features out to users faster when _we_ want to, without disrupting a rigid “sprint” cycle is also very freeing!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.