- ✓Tuckman's model of team development identifies four stages: forming, storming, norming, and performing, each with distinct characteristics and challenges.
- ✓Clear role definition within a team reduces overlap and conflict, and ensures that all necessary functions are covered.
- ✓Effective communication and psychological safety are the foundations of high-performing teams, allowing members to share ideas and raise concerns without fear.
- ✓Conflict in teams is inevitable but can be managed constructively through active listening, compromise, and focus on shared goals.
- ✓Remote and hybrid working arrangements have introduced new dynamics into team working that require deliberate communication and collaboration practices.
Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.
Start learning →Alex: Today we're covering team working dynamics, which is a crucial professional skill given that almost all real computing work happens in teams. Sam, where do we start?
Sam: Let's start with Tuckman's model of team development, because it gives a really useful framework for understanding what teams go through. Tuckman identified four stages: forming, storming, norming, and performing. Most groups go through all four, though not always smoothly or in a straight line.
Alex: Can you describe what happens at each stage?
Sam: In forming, the team is new. People are polite, a bit tentative, figuring out the landscape. Nobody wants to rock the boat. Then storming kicks in, and this is where conflict emerges. People have different working styles, different priorities, different opinions about how things should be done, and those differences start to surface. It can feel uncomfortable, but it's a necessary part of team development.
Alex: And norming and performing?
Sam: In norming, the team starts to resolve its conflicts and establish shared norms: agreed ways of working, communication patterns, role clarity. There's more trust and collaboration. Then in performing, the team is operating at its best: effective, motivated, and able to tackle complex problems with high cohesion and minimal friction. Not every team gets there, and teams can regress to earlier stages when significant changes occur, like new members joining.
Alex: What roles typically exist within a computing project team?
Sam: Roles vary by project and organisation, but common ones include a project manager or team lead who coordinates the work and manages relationships with stakeholders; developers who write the code; a systems analyst or business analyst who bridges the gap between business requirements and technical solutions; a tester who ensures quality; and often a product owner who represents the interests of the end users. Larger teams might have dedicated designers, security specialists, and DevOps engineers.
Alex: What makes a computing team function well?
Sam: Several things. Clear roles and responsibilities so that everyone knows what they're accountable for and who to go to for what. Good communication norms, whether that's daily stand-up meetings, a shared project management tool, or a communication platform like Slack. Psychological safety, which is the feeling that you can speak up, admit mistakes, and ask questions without fear of being judged or punished. This last one is hugely important for team performance and has been validated by research including Google's Project Aristotle.
Alex: How do you handle conflict in a team constructively?
Sam: The key is to address conflicts about work and process rather than letting them become personal. Focus on the issue, not the person. Listen actively to understand the other perspective before responding. Seek common ground: usually people who disagree have more shared goals than they realise and are just disagreeing about how to achieve them. Where genuine disagreement remains, bring it to the team lead or use a structured decision-making process rather than letting it fester.
Alex: And remote teams? That seems like it adds another layer of complexity.
Sam: Significantly. Without the informal interactions of sharing an office, you have to be much more deliberate about communication and team cohesion. Clear written communication becomes even more important. Video calls help maintain human connection. Regular check-ins, both for work and for wellbeing, are important. And being mindful of time zone differences for globally distributed teams adds another layer of planning.
Alex: Brilliant. Thanks Sam. In the next lesson we're covering CPD and how to manage your own professional development.