Entries tagged with “Collaboration Explained”.


When Agile teams start to plateau (or worse yet slide back to the old ways), I often hear this complaint:

“There is too much time in meetings with Agile Software Development, we give up!”

I usually follow that up with a question: What are you doing to fix that?

An overabundance of meeting time is a problem that many organizations face, but I’d argue that Agile practices are the solution instead of the cause. collab-explained

If I can get the team to ask me for suggestions, I always point them to my friend Jean Tabaka’s great reference book on running Agile meetings – called Collaboration Explained. But today I saw yet another wonderful nugget from Seth Godin about general meetings.

Seth Godin’s Suggestions on Serious Meeting Practices

Many of his suggestions relate to the practices of Agile and are disciplines we use at Rally to keep from meeting to death.  Seth’s portion in quotes below: 

  • Remove all the chairs from the conference room. I’m serious.
    New employees to an Agile team or company often laugh at the idea of a daily stand-up meeting, but literally standing during the meeting encourages people to be concise, attentive and then get on with their work. The best stand-ups at our company happen at around 9:00 am daily.
  • Understand that all problems are not the same. So why are your meetings? Does every issue deserve an hour? Why is there a default length?
    Agile helps us drive this discipline. Stand-up meetings are less than 15 minutes, iteration planning is a half-day for a new team and 1-2 hours for seasoned team.  Release planning is a 4 to 8 hours and my require a part of second day to handle dependencies across multiple synchronized teams. Allocate the right time for the right purpose, and bring in a professional Agile facilitator (or assign a neutral party from another department if you don’t have the budget) to keep the goals of the meeting moving. Having a agenda with time limits per section helps. So does a big buzzer (we have one of these at each table of attendees) to hit when people get off topic.
  • If someone is more than two minutes later than the last person to the meeting, they have to pay a fine of $10 to the coffee fund.
    We do this at our executive stand-up meetings (with a slightly lighter sentence), and recommend customers do the same. Late attendees pay $1; if you’re late AND the last one in the door, it’s $5.
  • “Require preparation. Give people things to read or do before the meeting, and if they don’t, kick them out.”
    Before release planning, we create a collaborative web site where materials are stored. All pre-reading is assigned in advance, and all attendees have to load their slides to the site before the meeting begins. We even have a “no thumb drive” rule to discourage last-minute slide creation.

So what’s my point? Don’t blame the methods and practices for your lack of personal discipline and commitment to get better.

If you are going to win in this global economy, you have to find ways to constantly improve, and Lean and Agile development are proven cures. It is too easy to give up, so instead stand-up and, as Christopher Avery teaches, take some personal responsibility to make it better – start from within!

Do you have other meeting guidelines that you’ve used successfully? How much of your company’s meeting addiction gets blamed on Agile practices? How has your organization adapted to better meeting discipline?

Yesterday evening, I was listening to “Marketplace” on National Public Radio and a segment on “Choosing the Best Business Books”.

Kai Ryssdal, interviewing Jack Covert and Todd Sattersten, asked the two if there is one book they’d recommend to survive a downturn economy. The two have just authored The 100 Best Business Books of All Time so they seemed like the right people to ask.  Their answer surprised me in a particularly wonderful way. SPOILER: it wasn’t my book Collaboration Explained :-)

But before I tell you which book it was, let me tell you a little about what made me so happy and amazed.

I teach a class called “Collaboration Explained” through Rally’s Agile University. In this class about facilitating Agile software teams to be truly collaborative, I also touch into how to tell when I team really isn’t collaborative. It could be about the project’s or organization’s leadership; it could be a fundamentally toxic environment.

Whatever the cause, I talk about (1) recognizing certain dysfunctions, (2) why we should care about them in Agile software development, and (3) what to do about them.

This brings us back to the book recommended by Covert and Sattersten. Both my source on Agile team dysfunctions and the business book they recommended for this difficult economy are the same: The Five Dysfunctions of a Team: A Leadership Fable by Patrick M. Lencioni.

What? A book about teams and their dysfunctions as THE business book for surviving a downturn economy? Yes.cm-capture-2

Teams in dysfunction can’t perform. And teams that can’t perform can’t be productive. Non-productive teams eat away at organizational performance.

Think about a team you have been on that just never seemed to gel. Stuck in what is sometimes called “Storming”, it just never seemed to be able to pull it together.


Thinking about that team, do some of these descriptions sound familiar?

  • Absence of trust
  • Fear of conflict
  • Lack of commitment
  • Avoidance of accountability
  • Inattention to results

As Lencioni in his fable will tell you, these dysfunctions build on one another; that is, until you resolve a fundamental absence of trust, you won’t be able to tackle a fear of conflict. And so on.  Individuals on teams stuck in these dysfunctions  “act out” in ways that evidence just how pernicious the damage can be from these untreated team ailments:

  • Invulnerability
  • Artificial harmony
  • Ambiguity
  • Low Standards
  • Status and Ego

So, back to “Marketplace”, Kai Ryssdal, Jack Covert and Todd Sattersten. Covert and Sattersten believe in the power of this business fable during this downturn economy because of the power and importance of teams in bringing economies back to life. If you are looking to Agile and how it can cut costs for your organization, consider the power of your teams. Work to engender trust and promote an ability to have constructive conflict. Empower your teams and amplify the learning that teams bring to organizations. And, consider that THE book recommended for all businesses by Covert and Sattersten, not just for software teams, in this downturn economy is a book that directly addresses team dysfunctions.

Cut costs, yes. But don’t just cut groups without consideration of Lencioni’s advice. Work to move dysfunctional teams to becoming high-performing. Maintain and nurture those teams that continue to gel and perform. That is how to survive this economy.

Further Reading: