The other ritual

Sam’s team gets interrupted for a living, servers being machines that misbehave on no schedule and with no regard for anybody’s committed fortnight, so the platform team runs the other flavour. A two-week promise is a promise the pager will break. They stopped making it.

kanbanConcept · lights on your mapkanbanThe agile flavour with no cycles at all: a continuous board with limits on how much may be in progress at once. Pull the next ticket when your hands are free. Suits interrupt-driven work the way scrum suits a cadence. has no sprints, no committed fortnight, no drumbeat. There is a board. The board has columns, the columns have tickets, and the one iron rule, the only rule kanban truly insists on, is a hard limit on how much may be in progress at any moment. Finish something. Pull the next thing. When a server catches fire, the fire is the next thing, and no sprint goal has been betrayed, since none was made.

One company, two rituals, both correct, and the correctness is the lesson: scrum suits work you can promise by the fortnight, kanban suits work that arrives shouting. Neither converts the other. The fluency move has nothing to do with knowing which is better. Clock which one a team runs within a minute of joining their meeting, and read their calendar accordingly.

What both teams share

Every few weeks, each team sits down to examine not the product but itself. That meeting is the retroConcept · lights on your mapretroThe retrospective, held at each cycle’s end: what went well, what hurt, what one or two things to change. The self-correcting loop that makes agile agile, run blameless by convention.: what went well, what hurt, what one thing changes next cycle. The merge-conflict Wednesday from week three surfaces in Race Experience’s retro, and the days-long-branch rule Finn’s week-old branch had quietly outgrown tightens to smaller branches, merged daily. The process debugged itself. That loop, more than any standup, is what the manifesto was actually about.

And both teams steer by the roadmapConcept · lights on your maproadmapThe long-view plan: what the team intends to build over coming quarters, at milestone resolution. A statement of intent rather than a contract, revised as reality votes., the quarter-scale statement of intent where cheer messages, the projected-finish model, and race day itself sit in one ordered line. Dana redraws it monthly. It is a plan the way a weather forecast is a promise, and everyone treats both accordingly.

Rituals carry the days. What carries the years is written down, and that is next.