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
Collaboration,
Teamwork,
Leadership
Tags
Coaching and Mentoring,
Information Radiators,
Self-organizing Team,
Complementary Practices,
Continuous Improvement,
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

Reply

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.