Well, as the Manifesto says, "Business people and developers must work together daily throughout the project." But Scrum's approach to this is overly simplisti

Well, as the Manifesto says, "Business people and developers must work together daily throughout the project." But Scrum's approach to this is overly simplistic (product owners?), backlog reprioritisation is not part of Scrum, and in any case you really ought to have some control over priorities because doing certain stories in the wrong order will reduce productivity. The problem that I'm pointing out is that Scrum has become synonymous with Agile in many quarters, and yet it is far from a complete solution to software project management. It's not that Scrum is no good, it's that it's not enough (or, in some cases, too much). When I've been forced to use some BigCo's rigid version of "Scrum", it's always been a nightmare. Of course it was, because rigid is the opposite of agile.