liveBook · Manning

Switching

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Switching is a reteaming pattern in which a team member moves between teams to spread knowledge or vary the person's work.

Switching is a dynamic reteaming pattern: a team member moves between teams to spread knowledge, vary work, and improve retention. It can refresh collaboration while making team output and estimation less consistent. section 11.4.3

Use switching as an adaptive practice rather than a fixed rotation:

  • Experiment carefully and gradually, considering switching frequency, subdomain complexity, and each person’s preferences. section 11.4.3
  • Include the people involved in decisions and create opportunities for feedback. section 11.4.3
  • Expect conventional story-point productivity comparisons to become unreliable when team membership changes. section 11.4.3

Monthly domain switching

A developer from each team switches to another team every month. Short team changes can spread knowledge and make work feel fresh, especially through pair programming with different colleagues. section 11.4.3

Figure 11.11 Every month a developer from each team switched to another team in the domain.

Visualizes a monthly arrangement in which one developer from every team switches to another team within the domain. section 11.4.3

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Defines the pattern and discusses cadence, subdomain complexity, preferences, feedback, and estimation effects without prescribing a fixed rotation.
Examples
Shows monthly developer movement between teams and short assignments involving pair programming with different colleagues.
What you can do after
Apply it through gradual experiments that include participants, gather feedback, and account for changing estimation reliability.
How it connects
Connects dynamic reteaming with knowledge sharing, pair programming, retention, and team productivity measurement.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.