↓ Skip to main content
eval ( code )

Dev Handbook

Table of Contents

In this section:

What
#

This is a practical guide for anyone leading, or growing into leading, a remote dev team. It covers the stuff that trips teams up the most: writing clear tickets, estimating without lying to yourself, running rituals that people actually find useful, and knowing when “done” really means done.

You don’t need to be a tech lead to get value here. If you’ve ever stared at a ticket wondering what it’s actually asking for, or sat through a standup that felt pointless, this handbook is for you.

Why
#

Most teams don’t have a broken process. They have half a process. Standups that don’t connect to the board. Tickets that don’t describe what “done” looks like. Estimates that nobody trusts, including the person who gave them.

The problem is that each piece was adopted in isolation. Someone read a blog post about standups, someone else copy-pasted a ticket template from a previous job, and now you’ve got a Frankenstein workflow where nothing feeds into anything else.

This handbook explains how all the pieces fit together. Scoping feeds estimation. Estimation sets expectations. Expectations drive standups. Standups surface blockers. The board reflects reality. When one part is out of sync, the whole system drifts. When they connect, the team spends less time talking about the work and more time doing it.