Abstract: Who says you need "stable" teams in order to build a successful software company? While the addition or removal of one person from a team means you have a "new team", there is a myth out there about "stable" teams. When your team compositions change it doesn't mean you're doing it "wrong" - it's just a different way of working. We've thrived through dynamic reteaming - the act of moving team members around teams in different ways. Even with changeable teams we still deliver value weekly to our customers. For the past 9 years, from startup to public company, we've learned a lot about reteaming. In this talk I'll share the what, why and how about reteaming with you.
Lessons Learned from Your Experience: - When one new person joins or leaves a team, you have a new team.
- It's valid and not an anti-pattern to have your teams change.
- The rate of team change can be tuned like a volume control.
- Changing teams can be "perfectly normal". So can moving from desk to desk.
- The coach's role is to deliberately help the team gel and get up to speed as quickly as possible.
- Understanding change theory is helpful to teach when you team and reteam.
- If you know and care about the people you work with, everything else comes easier.
- Focusing on the fulfillment of team members often initiates changes in teams.
- Feedback loops at the person level, individual team level, multiple team level, and organizational level supports reteaming.
Attachments:
