T-shaped Skills

A T-shaped person has deep skill in one area (the vertical bar) and enough competence across the team’s other work to contribute there too (the horizontal bar). Scott Ambler’s name for this is the generalizing specialist. On a stream-aligned team, a backend developer who can write end-to-end tests, read the deployment pipeline, and run a customer interview is T-shaped. A backend developer who only knows backend is a queue waiting to form.

We care about T-shaped skillsets because handoffs between specialists are where flow dies. Teams don’t grow T-shapes through training courses. They grow them by working together on the same thing. The sequence matters: first make the team self-sufficient by removing outside dependencies, then remove the silos inside it. In a dojo challenge we start with a skills matrix, ask the team what T-shaped would mean for them, and use mob programming and pairing to close the gaps. The goal isn’t a team where everyone can do everything. It’s a team where no single absence stops the work.

Resources

• Scott Ambler, “Generalizing Specialists: Improving Your IT Career Skills” (Agile Modeling)
• Shifting Left to a T-shaped Team — one team’s path from a dev and test split to shared stories
• Small, Cross-functional Teams — the team shape T-skills make possible
• Teaming — why the team, not the individual, is the unit of performance