Idea: a sprint that when it delivers its increment, the overall delivered product has reached an important milestone. It could be that it has reached an MVP stage and can be delivered (though would not be commercially successful), or can be deployed and actually deliver new capability.
Sprints are all meant to ‘deliver’ business value, but realistically most of them just showcase the increment. The increment often remains unusable.
There is an implicit assumption that the world stops changing when the Agile-built product is delivered.
The argument for Agile over Waterfall is that the world and the requirements change while the product is being built. Agile actually accommodates this change (true). But the world doesn’t stop changing just because we delivered, so a post project ongoing development may need to be planned for.
More important than rate of learning is ‘are you learning the right thing’?
