Form Second Cross-Functional Team out of Partly Layer-Team and First-Team Members
%% TODO: Or $following$ team
Alternative to Form Second Team out of Only Layer-Team Members
After the first Cross-Functional Team(s) have been formed out of Layer-Team Members, to from the next teams basically two different approaches can be taken: Either we will take someone out of the first new team to be part of the second new team, or not. The advantage of sending a first member to the second team is that the experience of doing the change the first time can thus be transported to the second team. The disadvantage is that we have rip apart the relatively newly formed first team and send it again into a storming-forming-norming-performing cycle.
- Choose (at least) one person from the first cross-functional team.
- You’ll want the “teachers” here—the people that like to pass on knowledge to peers.
- Fill up the second cross-functional team with members from the layer teams.
- Check that all the required knowledge is present in the team. So if no UI expert has come from the first team, send someone from the old UI layer team.
- Form a new team of less than ca. nine people.
- Let the new team take responsibility for a new bounded context.
- Let the rest of the teams organized as they are. They should already be shrinking in a significant way.