PMs and Their Teams: Temporary or Permanent?
One of the core elements of agile is the concept of stable teams. Individuals come together to work on a project, but when that project is complete, they remain together and move on to the next initiative. The idea is that the individuals learn each other’s strengths and weaknesses and are able to become productive more quickly because there is less need for the team to develop and people to figure out their roles.
It works, and it’s something that is becoming more common as agile teams—especially in the software development arena—move more to a product-based model. I still think there are benefits to introducing new people to teams in order to keep ideas fresh and prevent teams from becoming stagnated, but I recognize that it’s a balance that needs to be found between stability and those fresh ideas.
Stable teams have historically been less common in traditional project delivery environments, although it’s not uncommon for a few team members to be part of a number of different projects. Often these individuals are performing related roles where the benefits of familiarity and understanding are more obvious (examples might include a project manager and business analyst or marketing and sales specialists).
However, in recent years I’ve seen an increase in the use of stable teams in traditionally delivered projects, perhaps as a
Please log in or sign up below to read the rest of the article.