Comparing Approaches to Scaling Agile
Reedy Feggins 120000A43D Visits (11433)
A few weeks ago during an agile adoption seminar with a program manager considering using agile, I was asked to evaluate approaches to scaling agile practices to support adoption by a large program for their enterprise. This program had already adopted some basic agile practices (such as daily meetings, stories and Scrum) but felt they weren’t getting the benefits that other, smaller teams, got from “going agile”.
At first I thought this would be an easy exercise, given over the years I have had to assist several large customers with overcoming some of their critical issues with scaling agile but as I researches each approach and thought about some of the common challenges that many large teams face from my past experiences, coming up with a single recommendations became harder and harder. Based on my own personal experience, I decided to start by limiting my initial focus to comparing the following agile approaches: Scrum, DAD (Disciplined Agile Delivery), Scaled Agile Framework (SAFe), Large (LeSS).
The chart below summarizes my comparsion , as it’s too early for me to make recommendations for all situations or conclusions.
And after some thought, also decided to include Rational Unified Process and Waterfall, as most managers are familiar with these approaches, to assist teams understand my thought processes for comparison purposes. As Ken Schwaber, mentioned in a recent article on Scaling Scrum, scaling requires concerted effort by an organization. The leaders should start thinking about answering these questions: