How Work Actually Happens — Agile, Tickets, and the Rhythm of a Team

The first standup

Sylvia had been at the company in Bhubaneswar for exactly four days when she understood that nobody had taught her the most important thing about having a job.

She had joined a product company that built logistics software for regional transporters. She knew how to code. She had been hired because she could code. On her first morning her manager had added her to about nine Slack channels, assigned her a laptop, and pointed her at the codebase. She had spent three days reading code and feeling slightly useless, which is the normal first-week feeling and which nobody had told her was normal.

On the fourth morning, at 9:30, six people gathered near a screen and a seventh joined on video, and her manager said "let's do standup." Each person spoke for about thirty seconds. They used words Sylvia half-recognised. I picked up the SCN-412 spike yesterday, it's blocked on the staging credentials, I'll move to the retry ticket if it's not unblocked by lunch. I'm carrying over the reconciliation story, it's bigger than the points suggested. Nothing from me, I'm on the on-call rotation. It went around the circle. It took four minutes. Then it was Sylvia's turn, and she said, honestly, "I'm still reading the code," and someone said "that's fine, week one," kindly, and the standup ended.

She sat back down and realised she had understood almost none of it. Not the technical parts. The technical parts she could have followed. She had not understood the machinery. What a spike was. Why work had numbers. What "the points suggested" meant. Why nobody seemed to be telling anyone what to do, and yet everyone seemed to know what to do. She had spent four years learning to write code and zero minutes learning the system that decides which code gets written, in what order, by whom, and how a group of people moves together without a teacher at the front of the room telling them when to start.