Many organisations don’t really want to change how they do business and believe that they can continue in the way they always have while still getting better at delivering software. […]
Both as a 1 hour ScrumPulse and a team based workshop for the Dutch ALM UG I did sessions entitled Scaling Professional Scrum with Visual Studio Team Services. I showed how to use Team Services in the scope of multiple collaborative teams (or a Nexus) working on a single product.
Once you have Professional Scrum Teams you can focus on enhancing the communication lines that are a necessity of Scaling Software Delivery. Nexus is a framework for using Scrum to scale Scrum from Scrum.org and Ken Schwaber.
Are you doing mechanical Scrum? Also called flaccid Scrum, amateur Scrum, or by-the-book Scrum; all are equally ineffective. If you are not able to ship twice the features in half the time that you used to, then you are probably doing mechanical Scrum.
The insufficiency of Scrum is a fallacy perpetrated by teams that don’t step up their practices in concert with their planning and don’t really want to make it work anyway. You can fail doing Kanban, XP or Merese and SSADM just as easily. The goal of Agile is to have you fail sooner and for it to cost less.