> I think it’s interesting because the feature of the sprint you appear to like is that it completely removes small a agility. Ideally, at the end of a sprint

> I think it’s interesting because the feature of the sprint you appear to like is that it completely removes small a agility. Ideally, at the end of a sprint you'll have a concrete deliverable. Because this deliverable is concrete and not ongoing, the team should (theoretically) be able to switch entirely to a different project (or priority) afterward when business circumstances demand it. That's where the "agility" comes in. If, on the other hand, the work is being produced as a continuous flow--without hard cut-offs--then there's no set point where the team can switch priorities without leaving behind a half-finished state. Obviously, YMMV on how this all shakes out in practice.