The Hidden Life of Groups

room: Windsor East, M — time: Wednesday 16:00-17:30
Average Rating: -

Software development is performed by groups of individuals. When individuals become a members of a group, behavior changes. The group becomes focal and the individuals become background. The group behaves as a system and exhibits system-level behavior. Groups as a system exhibit primitive emotional behaviors that can derail the group from its stated primary task.

Group relations theory says that a group behaves as a system—and that the primary task of the group is survival. Although this primary task is frequently masked, survival as a group becomes the primary preoccupation— and latent motivating force— for all group members.

Understanding the undercurrent of group-level emotional behaviors manifested by all groups is important to effective Agile practice because these behaviors are a source of tremendous quantities of waste. Agile team members who understand group relations theory can more quickly pool their rational thinking, combine their skills, solve problems, and perform complex decision-making. Group relations theory helps explain the astonishing success of Scrum’s simple ground rules.

Under group relations theory, the group has a dual identity. The first identity is the work group, who are assembled to execute on the stated task. The second identity, the basic-assumption group, exhibits and manifests the latent aspect of group life. The combined wishes, fears, defenses, impulses and projections of the individuals in the group constitute the goals and objectives of the basic-assumption group.

A tension exists between the work group and the basic-assumption group. The behavior of the basic-assumption group has the potential to generate tremendous amounts of waste, while the behavior of the work group is capable of very high productivity. Basic-assumption behaviors can be minimized through the rigorous enforcement of simple ground rules and associated group norms. This is precisely how Agile methods like Scrum actually work.

Software development occurs in groups. Group relations theory helps explain the group-level sources of waste in software development. Attend this session to participate in a deep-dive into the application of group relations theory in your Agile practices.

Process/Mechanics

30 minutes: Introducing Group Relations Theory: Core Concepts

15 minutes: Questions and answers dialogue

30 minutes: Applied Group Relations in Agile Practice: The Scrum Case Study

15 minutes: Questions and answers dialogue

In this session you learn:

  • The history, development and premises of group relations theory. Groups defined.
  • The difference between stated (conscious) tasks and latent (unconscious) tasks that are universal in all groups
  • How the hidden undercurrent of emotional life inherent in all groups automatically generates waste
  • The four basic assumptions : Dependence, Fight/Flight, Pairing, and Oneness
  • How the four basic assumptions affect leadership and authority in all self-organizing teams. How genuine Agile methods manage group-relations effects in these teams
  • How genuine Agile methods like Scrum actively manage the hidden life of groups
  • How SDLC/waterfall methods actively encourage the irrational wishes, fears, defenses, impulses and projections of teams—thereby leading to absolutely huge amounts of waste
  • How Scrum’s clear and simple ground rules effectively manage the tension between the work group and the basic-assumption group by managing the focus of attention. The role of cognition in group relations
  • How to apply group relations theory immediately in your Agile practice.
  • Sources of more information on applying group relations theory in your Agile practices

Resources and Links:

Group Relations Theory
www.grouprelations.com

Complex Adaptive Systems

Jeff Sutherland on Complex Adaptive Systems
http://jeffsutherland.com/scrum/2007/11/is-it-scrum-or-lean.html

See also, from this presenter:

‘Paying’ Attention to Agile: Inattentional Blindness with Examples
http://submissions.agile2008.org/node/695