My company uses what one could describe as 'move fast and break things', but it comes with a few very important provisos including;
* Not for mission critical applications
* Very robust plans and technology in place for fast rollout and rollback
* A very solid automated test procedure so minimal user testing is required for each release
* A very good change documentation procedure (linking client requests, project management and code versioning together into something that makes some semblance of sense).
It works very well in certain markets - we provide technical solutions for very non-technical (marketing and design) clients, and they are guaranteed to change their minds 20 times before the end of the project, demand things go live at a moments notice and generally ignore our advice whenever possible, so we have a development lifecycle that deals with this very well, and we manage their expectations with regards to bugs appropriately.
I can see the point in scrum, but I don't think I've ever seen a situation where it couldn't be handled in a more flexible, slightly less smug/self-satisfied manner. Scrum Master...