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.
I value your opinion, even if I do not agree with it. The argument of "Scrum being poorly implemented" is brought again and again.
It's just another one of these go-to killer arguments.
If Scrum is so mega simple, why do we see endless cases of it failing to being implemented correctly?
Maybe we should start thinking of a framework, that people can actually implement and make successful, without requiring an entire army of coaches and consultants, who make a ton of money from it.
I'd love if you'd continue the discussion over at Agile Overflow.
Just wanted to jump in and let you know that I do read your feedback and * very much * appreciate it. I'm quite busy with responding over at Agile Overflow but will eventually comment back here, too.
I'm running Germany's largest native mobile development studio and am excited about Swift. With this initiative, we try to become a great source for quality links to Swift tutorials, discussions, open source projects and other content related to Swift development. Would love if you help spreading the word. Also on ADN (swiftdev) and Twitter (swiftdev_tips).