Agile Teams and The Breakfast Club

The Breakfast Club

One of the iconic movies of the 1980s was The Breakfast Club, which told the story of five very different teenagers who were forced to come into school one Saturday to serve detention.  Recently I’ve been working at a large insurance company helping them to adopt the Disciplined Agile (DA) toolkit.  One of people whom I’m working with has a Breakfast Club poster on the wall near her work area and it got me thinking about some of the dynamics that I’ve seen watching agile teams form and eventually gel.  Here are my thoughts.

At the start of the movie the kids didn’t really like each other, they were very different from one another, they certainly didn’t want to be there, and they were each coming to the group with their own point of view and background.  Sadly, I’ve seen more than one software project team that was put together like this.  As the movie progressed they began to really talk with one another and their stories started to emerge.  They started to work together, hijinks ensued, and they bonded as a group.  As part of their punishment they were each asked to write an essay describing what they learned from their detention.  Instead they wrote a single letter, which follows, that they submitted as a team.

“Dear Mr. Vernon:

We accept the fact that we had to sacrifice a whole Saturday in detention for whatever it was we did wrong, but we think you’re crazy to make us write an essay telling you who we think we are. You see us as you want to see us… In the simplest terms and the most convenient definitions. But what we found out is that each one of us is a brain… …and an athlete… …and a basket case… …a princess… …and a criminal.

Does that answer your question? Sincerely yours, the Breakfast Club."

So how does this relate to agile teams?

  1. You often build teams from specialists.  Although we ideally recommend that you build teams from multi-disciplinary, T-skilled generalizing specialists, the reality is that many organizations are staffed with specialized people.  We like to say that you go to war with the army that you’ve got, or in other words you need to make do with what you have.  If all you have are specialized staff then that’s the people you have to form teams.  The good news is that you can help people to evolve from being specialists into generalizing specialists via building a cross-functional whole team, enabling and promote non-solo collaborative work within the team, and by training and coaching people.
  2. It takes time for a team to gel.  In the movie the “team” gelled in a single day, but it’s rarely that fast in practice.  It often takes weeks, and sometimes months, for a team to really get to the point where they’re working together effectively (yet another reason to move towards stable solution delivery teams).
  3. Co-location shortens the time it takes to gel.  When we’re co-located, everyone works together in the same room, it is much easier and much more likely that we will collaborate with one another.  Not only does this increased interaction help us to get the work done it also helps us to gel as a team faster.
  4. We’re not as different from each other as we think.  One of the lessons that the kids learned in the movie is that each one of them had a bit of an athlete, a brain, a criminal, and so on in them.  Similarly, we’re not just programmers, or architects, or analysts but instead we all have some of those skills in us and we can certainly get better at the skills that we are weak on.
  5. We are still different.  Every single person is a unique individual.  This implies that we must be flexible in the way that we collaborate with one another, that people simply aren’t “cogs in the corporate machine.”  We should also respect the fact that we each bring something of value to the team, a revelation that the kids in the movie stumbled upon when they had to work together to not get caught by Mr. Vernon (there were a few hijinks in the movie).
  6. Working together as a team produces better results than a group of individuals.  As Alistair Cockburn likes to say, software development is a team sport.  In the movie the kids all got caught doing something on their own, hence the punishment of a Saturday in detention, yet together they managed to have a fair bit of fun as a team.  Similarly, you may be the best programmer in the world, but it behooves you to work with people who can help you to understand the requirements, design the solution, validate the solution, and so on.
  7. We can all learn from each other.  Everyone has value to bring to the team and everyone has areas where they are weak on that could be improved.  By working closely together we can learn from each other and get better both as individuals and as a team.

The Breakfast Club is a great movie.  If you haven’t seen it, or haven’t seen it lately, then I highly suggest watching it again.

Have any Question or Comment?

6 comments on “Agile Teams and The Breakfast Club

John Gagon

A fave movie and a great analogy! The team members (line workers) are more often faced with turnover and regular team churn so it’s very applicable. There’s the flip side on how to loosen up the encrusted cronies in an organization. Maybe a follow up could be done there.

Agile environments are good at building the disparate and diverse team because of various ideas and ideals. You could say the Breakfast Club found some success in co-location (and more importantly, that communication over processes)


John, great point about co-location. I’ve updated the blog accordingly.

John Gagon

Thank you. I could also see some “paired shennaniganning” but that might require too obscure a coinage.

Rachel Soskin

Scott, like most of us, you are a true child of the eighties and I salute you. I do agree that The Breakfast Club may be a stretch, but I do not agree about the hairstyles – my wild girls were the envy of many in the 80s! Yes, I may be an old fogey, but when I first started working, in the UK in the late 80s early 90s, we were all co-located teams, working together, with desks pushed together, we all answered each other’s phones, made each other coffee, and there were whiteboards everywhere! We all wore many hats, depending on what was necessary at the time, to get the job done. We all created chunks of functionality, from beginning to end. But, it wasn’t called “agile”. Amazing, isn’t it? It seems we have come full circle!

Joe Butson

Been there done that Rachel with RUP Teams in Toronto! Thanks for sharing your story + the big hair 😉

It has always amazed me how colocated teams who valued each other’s skills would find common ground quickly and produce results rapidly when they worked together.

Love the “The Breakfast Club” movie analogy Scott! So 80’s! And great tunes!

I have a “Gettysburg” agile analogy I have been meaning to write about one day!


I’d also add that having a shared vision (in the case of the movie, a common “enemy”) and constraints (in the movie, they were limited by the availability of resources) can help in forging a good team.


Leave a Reply to John Gagon Cancel reply

Your email address will not be published. Required fields are marked *