Skip to main content

Before Scaling Up - consider...

Before one scales up their functioning teams (I'm assuming one would not want to scale up non-functioning teams - yet I've seen that done) one should look for alternatives to the scaling problem.
"Scaling Agile methods is the last thing you should do" —@martinfowler, 2003

This scaling problem has been studied:

"In 1957, British naval historian and management satirist Northcote Parkinson [known for Parkinson's law: “work expands to fill the time available for its completion”] painted a cynical picture of a typical committee: It starts with four or five members, quickly grows to nine or ten, and, once it balloons to 20 and beyond, meetings become an utter waste of time – and all the important work is done before and after meetings by four or five most influential members."

Scaling up Excellence

Why Big Teams Suck by Robert Sutton is a Stanford Professor and co-author (with Huggy Rao) of Scaling Up Excellence: Getting to More without Settling for Less.

Studied in Academia

"After devoting nearly 50 years to studying team performance, the late Harvard researcher J. Richard Hackman concluded that four to six members is the team best size for most tasks, that no work team should have more than 10 members, and that performance problems and interpersonal friction increase 'exponentially as team size increases'.”

Studied in the Military

"Some organizations learn about the drawbacks of oversized groups the hard way. Retired Marine Captain and former U.S. Senator James H. Webb explained why the “fire team” – the basic combat fighting unit – shrunk from 12 to 4 during War II. Webb wrote in the Marine Corp Gazette that this “12 man mob” was “immensely difficult” for Marine squad leaders to control under the stress and confusion of battle. Coordination problems were rampant and close relationships – where soldiers fight for their buddies – were tougher to maintain in 12-man teams."

Studied in Health Care

"A Harvard Business School study by Melissa Valentine and Amy Edmondson of a large hospital’s emergency department [...] The crowd of 30 or so doctors and nurses who staffed the department at any given time were divided into multiple six person “pods,” each led by a senior doctor or “attending physician.” After the change, information about patients flowed more quickly and accurately and personal relationships improved markedly. Smaller teams reduced confusion and discomfort about who to ask for help and updates."

I think the general lesson learned is to not scale up, because the systems and structures that created and support the current organization will not bare the stress of scaling up.

Some alternatives to Scaling Agile:

Scaling Agile – the Easy Way by Arlo Belshee

Try to re-structure the organization in a way that doesn't require efficiency of scale to achieve the goal. For example WL Gore's organizational pattern a team based flat lattice.

Or Semco, "a Brazilian conglomerate that specializes in complex technologies and services. Semco is a self-managed company. Workers at Semco choose what they do as well as where and when they do it. They even choose their own salaries. Subordinates review their supervisors and elect corporate leadership. They also initiate moves into new businesses and out of old ones. The company is run like a democracy." -- Podular organization: a business within the business written by Dave Gray.

Try a fundamentally radical idea like Holacracy.  "Holacracy is a real-world-tested social technology for agile and purposeful organization. It radically changes how an organization is structured, how decisions are made, and how power is distributed."

Take a lesson from the US Government's FBI Case Management system.

Before you consider the leading market agile/scrum scaling tool-sets like SAFe, DAD etc. try this alternative approach:  Open Agile Adoptions by Dan Mezick author of The Culture Game.

“Scaling is actually a problem of less,” says Sutton in The Do’s and Don’ts of Rapid Scaling for Startups. “There are lots of things that used to work that don’t work anymore, so you have to get rid of them. There are probably a bunch of things you’ve always done that slowed you down without you realizing it.”
See Also:
The Founder Effect
Comparing Scaling Agile Frameworks - CIO 
The Agile Late Majority has different needs
The Scaled Agile Framework (SAFe) – A Review by Agile Scout
SAFe - but not good enough  by Ron Jeffries
Scaling Scrum: SAFe, DAD, or LeSS? by Peter Stevens
Scaling Agile Development LeSS - PDF by Larman & Vodde
IBM's Disciplined Agile Delivery DAD by Scott Ambler
Scaled Agile Framework SAFE by Dean Leffingwell
A Scaled Agile Framework® (SAFe™) Case Study by Brad Swanson
Large Scale Scrum (LeSS) @ J.P. Morgan by Craig Larman and Matt Winn
Case Study of a Difficult Federal Government Scrum Project: FBI Sentinel by M. James
Kanban and its flight levels by Klaus Leopold
Agility Adoption Rather Than Agile At Scale by Oana Juncu
The Folly of Scaling Agile by Rachel Davies
Speaking on SAFe: Thoughts from my Leading Scaled Agile Framework course  by Andrew Clear
Enterprise Agile: Are you Ready by Scott Ambler - DAD slides from Agile2014
LeSS vs SAFe case study at Nokia by Gosei (Ari Tikka & Ran Nyman)
Moving Past the Scaling Myth by Michael Feathers
LeSS is More - SolutionsIQ Agile Amped talk at Agile2015 by Bas Vodde & Craig Larmann
Descaling Organizations with LeSS  by Viktor Grgic
Large Agile Projects by Martin Fowler
SAFe: the infantilism of management by Dave Snowden
Post a Comment

Most Popular on Agile Complexification Inverter

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.

In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.

Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    To Do
    Work In P…

The Case Against Scrum's Sprint Practice - Another Look

In the excellently written article  Dark Scrum:  The Case Against the Sprint, Ron Jeffries' does a wonderful job of explaining a common problem of Scrum's mainstay practice, the Sprint.  As I read the article I could only think of many managers I've seen over my years that didn't trust Scrum, the teams, or the coaching to deliver.  And feeling pressure to make deadlines imposed from little information (desire more than empirical evidence) had reverted to past heavy handed pressure techniques to make a deadline.  After all it was their career that was on the line.

To summarize (and you would do better to just click the link and read it):  As an exercise in explaining the inverse of "Good Scrum", Ron uses the term "Dark Scrum".  In this inverted world, Ron makes the case that the Sprint is a bad practice, because a manager expecting the common faster progress (Jeff Sutherland's statement “Twice the Work in Half the Time”) will demand that result.…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?

Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What is your Engagement Model?

Jim Harter states in his article from Gallup:
According to our recent State of the Global Workplace report, 85% of employees are not engaged or actively disengaged at work. The economic consequences of this global "norm" are approximately $7 trillion in lost productivity. Eighteen percent are actively disengaged in their work and workplace, while 67% are "not engaged." This latter group makes up the majority of the workforce -- they are not your worst performers, but they are indifferent to your organization. They give you their time, but not their best effort nor their best ideas. They likely come to work wanting to make a difference --- but nobody has ever asked them to use their strengths to make the organization better.
Is this analysis a cart and horse locating problem?  Do we need better diagrams of which comes first?
When we get performance management right, engagement will naturally rise. Performance management is a trailing tool (not a leading indicator or …

Committed Sardines Game

The Committed Sardine By Ian Jukes 
A blue whale is the largest mammal on earth. The adult blue whale is the length of 2½ Greyhound buses and weighs more than a fully loaded 737. A little known fact is that a blue whale is so large that when it decides to turnaround, it can take 3 to 5 minutes to turn 180 degrees in the opposite direction.

As a result, some people have drawn a strong parallel between blue whales and our school system. It just seems to take forever to turn them around. There as some people who just don’t believe the public school system can be turned around.

But compare the way a blue whale turns around (slowly) with how a school of. . . Sardines – which is the same or even greater mass than a blue whale. . . A school of sardines can almost turn instantly around – how do they do it?

The answer is simple. If you take a careful look at a school of sardines you will notice that although all the fish appear to be swimming in the same direction, at any one time, there will b…