A software development model in which engineering work is passed continuously across time zones — each shift picking up where the previous one left off — theoretically enabling 24-hour development cycles.
Follow-the-sun development fails in practice when teams have communication infrastructure but no governance infrastructure. Passing work across time zones requires more than a ticket in Jira and a message in Slack. It requires a declared transfer of state: current progress, open questions, blockers, and decision authority. Without that transfer, each shift loses 30 to 90 minutes reconstructing context before it can move.
Why follow-the-sun development matters for distributed teams
Follow-the-sun is the promise. Governance infrastructure is the mechanism. Without the mechanism, the promise delivers 16-hour cycles with 8 hours of waiting — not 24-hour cycles.
The teams that make follow-the-sun work are the ones that have invested in declared handoffs, decision authority mapping, and a query layer that lets the incoming shift ask questions of the outgoing shift's declared state without requiring the outgoing shift to be awake.
Frequently asked questions
Why does follow-the-sun development fail?
Follow-the-sun development fails because most teams have communication infrastructure but no governance infrastructure. They can pass messages across time zones, but they cannot pass working state — blockers, decisions, next actions, and authority. Each shift loses 30-90 minutes reconstructing context, turning a theoretical 24-hour cycle into a 16-hour cycle with delays.
Related terms
Declared handoff
A structured transfer of working state from one engineer — or one shift — to the next, made explicit before the outgoing...
Read definition →Continuity layer
The structural mechanism that ensures work advances across timezone boundaries without loss of context, ownership clarit...
Read definition →Engineering wrap
A structured end-of-shift declaration made by an engineer before going offline. The wrap declares current state, outstan...
Read definition →Get the vocabulary that makes distributed teams work
One email per week on async governance. No spam.
See follow-the-sun development in action.
StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.