InfoQ

News

Well Formed Teams: Helping Teams Thrive, not just Survive

Posted by Mark Levison on Mar 25, 2008 12:10 AM

Community
Agile
Topics
Teamwork ,
Leadership ,
Collaboration
Tags
Self-organizing Team ,
Continuous Improvement ,
Complementary Practices ,
Information Radiators ,
Co-Located Teams ,
Coaching and Mentoring

In a recent AgileJournal article, Doug Shimp, Managing Partner with 3Back and Samall Hazziez, Senior Managing Partner for the Preferred Professionals Business Group, have written about what it takes to enable high-performing "Well Formed Teams" to thrive.

The authors have observed a number of characteristics that enable Well Formed Teams:

  • Process: Scrum, Lean and XP. In addition some of the more traditional processes RUP, PMBOK, …
  • Environmental enablers: collocated teams, team rooms, visible charts, white boards, …

However on their own, the principles and practices may burden a team with too much process and information. Instead the authors recommend we focus on what makes teams thrive. In their experience these can be broken down into "3+2".

3 principles:

Let the product lead - always pay attention to the needs of the product. Any time the team considers adopting a new practice or idea ask the question how does this serve the needs of the product.

One bite at a time - Each item of work should be broken up into small enough pieces to eat. Most of us bite of larger chunks than we can chew. Breaking tasks down into smaller parts means that we can get them done in smaller timeboxed cycles.

Keep it visible - one of the most obvious principles it is rarely done well. When we cannot see what our team mates are working on, we cannot see where to apply our own efforts. The result we struggle. With increased visibility we increase the chances that other team members will step in with useful ideas that help solve our problems.

+2 practices:

Conversation and Structure - these are used to balance the three principles above. "The conversation requires enough structure from an established protocol so that we can communicate effectively. … The conversation is necessary for humans to establish rapport so that we can create, contribute and share deep meaningful understanding."

How can you tell if you have a well formed team? In the opinion of the authors they exhibit some of these characteristics:

  • Follow Agile and Lean principles
  • Co-located
  • Team members show a high state of rapport.
  • Team members contribute thoughts and share ideas equally. There is no ownership of ideas.
  • Brainstorming as a group
  • Self assign work
  • Have a good understanding of business objectives and are focused on delivering features that match the business priority
  • The good of the team is placed ahead of the individuals
  • New skills are acquired quickly and as needed to help the team
  • Team members challenge each other to bring out their best
  • Hyper-productivity - where hyper productive is sustained productivity at least 4 times the industry average. (Jeff Sutherland CTO of PatientKeeper and co-Inventor of Scrum).

Well Formed Teams are valuable to the business because they're nimble and able to adapt to the constantly changing business landscape.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Watch Thread Reply

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.