InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Well Formed Teams: Helping Teams Thrive, not just Survive

Posted by Mark Levison on Mar 25, 2008

Sections
Process & Practices
Topics
Agile ,
Teamwork ,
Collaboration ,
Leadership
Tags
Complementary Practices ,
Co-Located Teams ,
Information Radiators ,
Self-organizing Team ,
Continuous Improvement ,
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.

  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.