Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage News Aspects of Staffing Agile Teams

Aspects of Staffing Agile Teams


Blog posts by Esther Derby and Mike Cohn focus on two different aspects of the staffing of Agile teams.

In her blog post, Derby makes a case for stability with respect to Agile team membership. According to Derby, moving people into and out of teams has negative affects that include miscommunication, misunderstanding, and lack of mutual accountability. She writes:

Team members can't be mutually accountable if they don't know who makes up "we" when they commit to deliver.

Mike Cohn asserts that, despite the self-organizing nature of Agile teams, the teams themselves should not possess the exclusive right to remove their own members. According to Cohn, the leadership of the organization must itself take responsibility for team composition.

Cohn bases his assertion, in part, on the work of Glenda Eoyang, referring specifically to her Container-Difference-Exchange (CDE) model of self-organization. According to Cohn, one of the responsibilities of leaders is to exert infuence over Agile teams by making adjustments to the team's boundaries, as established by the organization. He writes:

For example, over time and through attrition a team might have become too homogeneous. An astute product owner, functional manager, or even ScrumMaster might counter that by adding two new team members with radically different backgrounds, skills, decision-making styles, or so on. Doesn't it seem possible—likely even, in this example—that a team might have a knee-jerk reaction and vote the new, nonconforming individuals off the team, negating the work of the leader who deliberately added them? Ultimate authority for team composition, therefore, must reside with the leadership of the organization.
We need your feedback

How might we improve InfoQ for you

Thank you for being an InfoQ reader.

Each year, we seek feedback from our readers to help us improve InfoQ. Would you mind spending 2 minutes to share your feedback in our short survey? Your feedback will directly help us continually evolve how we support you.

Take the Survey

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Don't mess with the membership

    by Esther Derby,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I agree that only a manager can fire someone. That's a legal matter.

    As for the situation Mike describes, I would approach it differently. I would talk to the team about what I've observed, and the impact the homogeneity is having on results. And I'd involve them in solving the problem. One solution might be increasing differences within the team by adding new members. A savvy manager would use a collaborative hiring process so that the team has some investment in integrating the new team members.

    BTW: Where did the practice of voting someone off the team come from? That may be a good formula for reality TV shows, but not so good for psychological safety on a team.

    Esther Derby ||

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.