InfoQ

News

Well Formed Teams: Helping Teams Thrive, not just Survive

Posted by Mark Levison on Mar 25, 2008

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

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

Brian Marick on 4 Challenges and 5 Guiding Values of Agile Software Development

Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).

Are You a Software Architect?

The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?

Agile – A Way of Life and Pragmatic Use of Authority

The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.

Getting Started with Grails, Second Edition

"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?

Using ITIL V3 as a Foundation for SOA Governance

Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.

Adrian Colyer on AspectJ, tc Server and dm Server

SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.

Adam Wiggins on Heroku

Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.

SOA as an Architectural Pattern: Best Practices in Software Architecture

For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.