What makes a good tech team? (Draft #1)

Tom Szpytman
Mar 24 · 1 min read

Purpose

  • A sense of direction. A goal that the whole team can work towards.
  • A place in which everyone, on each level, can learn and grow.
  • A culture which promotes knowledge sharing.
  • A culture that promotes (timeboxed) investigations.

Leadership

  • A person who acts as the ‘source of truth’. This is a person who, for example, when asked “what’s our coding style?” can guide you to an answer.
  • A facilitator. This is a person who, might not necessarily have as deep a tech knowledge as others, but who knows how to facilitate efficient discussions that lead to actionable outcomes.

Code

  • A branching strategy that works for the team.
  • Rigorous code reviews.
  • Coherent code style.

Process

  • Well organised, clearly written documentation (inc. meetings, processes, investigations etc.).
  • ‘Retrospectives’, or periodic meetings dedicated to addressing any team, or project-wide issues.
  • Periodic 1-on-1 meetings to address individual issues.
  • A work-flow that allows working from home.

Environment

  • A refined, documented, setup process that allows a new starter to get up and running quickly.
  • Well-specced developer machines.
Tom Szpytman

Written by

Full-stack Software Engineer.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade