Case study · Engineering · Small development team
From ad-hoc coding to a team that outlasts its members
A capable team whose practice lived in people's heads. We gave it the habits of a larger engineering organization, scaled to its size.
Situation
A small development team shipped real work, but its practice lived in individual heads. Code sat on personal machines or a shared folder, changes went live unreviewed, and tasks were tracked in chat. Each departure took knowledge with it, and each new hire started from scratch.
Approach
We introduced the practice of larger engineering organizations, scaled to the team's size:
- Git as the single source of truth, with a simple branching model
- A code-review habit: every change read by a second person before it merges
- Jira for visible work, with a lightweight sprint rhythm of planning, standups and retrospectives
- Written conventions and onboarding notes, so how the team works is documented rather than remembered
Outcome
Work became visible, reviewable and repeatable. New members could onboard from documentation instead of shadowing, and the team kept its pace when people moved on.