There could be multiple reasons for "cancellation"
1. Change in business priorities
2. Stakeholder concerns on sprint outcome
3. Resource issues (that cannot be immediately resolved)
4. Organization request (something outside the control of the project)
5. Realization of false estimate (difference big enough to stop and re-plan the sprint)
6. Team request for termination ( for reasons of miss-understanding on scope or approach/technical debt that might take considerable time to resolve)
7. Product Owner request for termination (scope/quality related concerns)
I guess depending on the scenario in hand the Product owner or Scrum Master can take a call. The word "cancellation" though might send a wrong message; idea should be to carry forward the learnings and assets created by such incomplete sprint. I am not sure but "closed with exceptions" where the exceptions are clearly defined and incomplete work carried forward to subsequent sprints or iterations.
Saving Changes...
