[asalazar]

In either Scrum or Kanban, it's important to separate your development cycles from when you release or deploy cycle.

For example: In Kanban, our developers work in a flow model to get anything and everything they can get done as fast as they can get it done (regardless of when the release is planned). We manage the work by using work in progress limits. However, we have a public releases that are scheduled every two weeks. So on that scheduled release date, we take all the completed tasks lump them into a release. Nothing holds up a release. For high priority feature, we'll do a hot fix. For big announcements, we'll usually schedule it after we've completed most of the work.

Scrum is the same in this regard at most companies. A public release could happen after 1, 2, or 200 sprints. It really just depends on what you're trying to do.

In the Apple AppStore model, Kanban or Scrum should have no impact on how you deploy. You deploy when you're ready. Kanban no Scrum guarantee that it'll happen by a certain date.