What We've Learned Running Agile Teams Across Time Zones
Agile works beautifully on paper. In practice, at scale, across time zones, with clients who have never used it before — it's a different story. After three years of running agile delivery for clients in Japan, Singapore, and Vietnam, ICTI has accumulated a set of hard-won lessons that go far beyond the textbook.
The Ceremonies That Actually Matter
Most teams run all the ceremonies — daily standup, sprint planning, review, retro — but treat them as boxes to check rather than as tools for communication. The ceremonies that consistently generate value in our experience are sprint planning and retrospectives. Everything else is useful but secondary.
Sprint planning done properly takes time and generates clarity. Teams that rush planning spend the rest of the sprint clarifying requirements in Slack. Teams that invest in planning ship more cleanly, with fewer mid-sprint scope changes, and with developers who understand the why behind each task — not just the what.
Retrospectives as a Learning Engine
A retrospective where the team talks but nothing changes is not a retrospective; it's a venting session. The discipline of assigning owners to action items and reviewing completion at the start of the next retro is what turns a retrospective into a genuine improvement engine. We track retro action completion rate as a team health metric — a consistently low rate is an early warning sign of a team that is going through the motions.
Scaling Without Losing Agility
- Keep team size at 6-8 people maximum; larger teams should be split into squads with a shared backlog
- Synchronize sprint cadences across squads so integration points are predictable
- Designate one person as the cross-squad coordination lead; do not make this the product owner