liveBook · Manning

Team

As explained in Lead Developer Career Guide

A group of software professionals responsible for designing, building, testing, and maintaining software.

A development team is the group doing the technical work of a software project. A lead developer helps that group deliver quality work: setting direction, facilitating communication, gathering feedback, and clearing obstacles. The lead’s success depends on the team’s success, not just on their own output. section 1.1.3

The development team is part of a wider project team. Project managers help organize priorities and schedules; QA checks whether work meets requirements; clients and stakeholders provide needs and feedback. The lead developer connects these groups, using developers’ input to estimate work and weigh priorities. section 1.2.2

To help a team work well:

  • Make questions welcome, and help people find the right contacts in QA, DevOps, project management, or design. section 7.3.1
  • Prioritize important tasks, unblock work, and compare planned tasks with completed work while watching quality and technical debt. section 1.1.3
  • Give specific feedback rather than routinely redoing someone else’s work; support should help teammates improve. section 10.5.4

When priorities change

A developer may need to stop work on a feature. Give them time to reach a sensible stopping point, document what remains, and check in their work so they or a teammate can resume it later. section 1.2.2

Team-building also includes hiring people who meet technical needs and can collaborate. Across projects, keep communication open, seek help beyond the development team, and make it easier for each person to contribute. section 12.3.2 section 7.3.1

How Lead Developer Career Guide covers it

How deep it goes
Develops practical guidance on communication, priorities, support, and hiring rather than a formal model of team structure.
Examples
Uses a changing-priorities handoff and a leader’s counterproductive rewriting of a teammate’s work.
What it assumes
Assumes experience developing software while introducing the communication and leadership skills needed to lead other developers.
What you can do after
Practice/perform team leadership by clearing obstacles, connecting colleagues, and giving feedback without taking over their work.
How it connects
Links team effectiveness to lead development, project management, quality assurance, stakeholder communication, technical debt, and hiring.

Also explained in

Compare how 2 books explain team →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.