Well, as far as I understood, Scrum's fundamental principle dictates that the team delivers working software at the end of every Sprint.
This has partially to do with not over committing at the beginning, but if the team fails to judge correctly, it has to do what needs to be done to fulfil its promises.
Unfortunately, this clear obligation gets forgotten to often – as I pointed out in the original post.
This has partially to do with not over committing at the beginning, but if the team fails to judge correctly, it has to do what needs to be done to fulfil its promises.
Unfortunately, this clear obligation gets forgotten to often – as I pointed out in the original post.
You seem to second my point.