A cross-functional team brings together engineers, designers, analysts, and other roles to coordinate toward shared goals. For a software engineering manager, building one means aligning people, responsibilities, communication, decisions, and measures of success. section 9.2 section 9.5
Build a cohesive team by working through these practical responsibilities:
- Clarify and align on goals, mission, roles, and required skills. section 9.2 section 9.5
- Establish communication practices, team ceremonies, decision-making rules, and continuous feedback. section 9.2 section 9.5
- Expect conflict, listen for different perspectives, find common ground, and let the team shape workable solutions. section 9.2 section 9.5
- Align nontechnical partners on project goals and explain why operational excellence and technical debt deserve balanced priority. section 9.4 section 9.5
A team moving from conflict to collaboration
A newly assembled team first agrees on its mission, roles, agile approach, and ceremonies. When disagreements arise, members discuss perspectives and negotiate a joint resolution rather than assuming harmony. Over time, these agreements become a working norm, while success is tracked through appropriate metrics. section 9.2 section 9.5
The Forming-Storming-Norming-Performing model for team development
Use the Forming-Storming-Norming-Performing model to recognize a team’s development stage and choose appropriate support. section 9.2
