Agile for One
Almost everything written about Agile assumes a room. A team around a board, a Scrum Master keeping time, planning poker cards going up in unison. My operation has none of that. Most days, the team is me — running short-term rentals in Atlanta, handling guest messages, cleaner schedules, maintenance, pricing, and the books. So the honest question is: what does Agile even mean when the standup has one chair?
More than you’d expect. But not all of it. Solo Agile is mostly an editing job — keeping the parts that manage the work and cutting the parts that were only ever managing the people.
What survives
A visible board. If the work only exists in my head, it competes with everything else in my head, and the loudest task wins instead of the most important one. My board is nothing fancy — columns for what’s coming, what’s in progress, what’s waiting on someone else, and what’s done. Guest issue, turnover prep, a repair quote, quarterly taxes: all on the board. The point isn’t the tool. The point is that on a tired Friday afternoon, I can see the whole operation at a glance instead of reconstructing it from memory and inbox guilt.
A work-in-progress limit of one or two. Teams limit WIP to stop context-switching. Solo, the same math applies harder, because there’s nobody to absorb the spillover. When I catch myself with five things half-started — a reply drafted but not sent, a supply order open in a tab, a cleaner schedule half-updated — nothing is actually moving. One active task, one on deck. Everything else waits on the board, written down, where it can’t nag me. Multitasking for a team of one is just slow-tasking with better branding.
A short weekly review, run like a real meeting. Thirty minutes, same time every week, with an agenda: what got done, what’s stuck, what’s coming in the next two weeks. It feels faintly ridiculous to hold a meeting with yourself — right up until you skip it three weeks running and realize you’re operating entirely on whatever shouted loudest. The agenda matters. Without one, the “review” becomes scrolling your messages and calling it planning.
A written definition of done. On a team, other people check your work. Solo, you are the check, and “done” quietly drifts: the listing update is done except for the photos, the expense log is done except for two receipts. I keep a short checklist for the recurring jobs — a turnover isn’t done until the clean is confirmed, supplies are restocked, and the next guest has the door code. Done means the same thing on a good week and a bad one because it’s written down, not because I feel thorough that day.
Sprints matched to the season. My work has seasons — summer bookings, holiday surges, the quieter stretches in between. Long improvement projects don’t fit in peak season, so I don’t schedule them there. Renovations, system cleanups, and process fixes go in the slow weeks, in two-week sprints with a clear finish line. Peak-season sprints shrink to one week and cover operations only. A cadence that ignores your busy season isn’t discipline; it’s a plan to feel behind four months a year.
What gets cut
Estimation rituals built for teams exist to align a room full of people — story points, poker, t-shirt sizes. Alone, I estimate in the only unit that matters: hours of my week. A task gets a rough time guess and a deadline. That’s it.
Standups performed for an audience of zero. If I want a daily check-in, the board gives me one in ninety seconds — what’s in progress, what’s blocked. No ceremony required.
Any artifact nobody will ever read. Burndown charts for one person. Velocity reports to an audience of me. If a document doesn’t change a decision I make, it doesn’t get produced. Process theater is still theater when the audience is just you, and it costs the same hours.
The auditor’s footnote
Here’s the twist nobody mentions about working solo: in an audit, the person doing the work and the person controlling the work are supposed to be different people. When you’re a team of one, you’re both — which means the controls have to live on paper instead of in a second pair of eyes. So I write things down. Decisions, prices I quoted, why I chose a vendor, what “done” meant for that job. Future me is the auditor, and she has no memory of my good intentions. The board, the checklists, the review notes — that’s the audit trail, and it’s what makes one person running an operation different from one person just being busy.
The weekly rhythm, on one page
- Monday, 30 minutes: Weekly review. Check the board against the calendar — bookings, turnovers, deadlines. Pick the week’s sprint goal: one main thing, not five.
- Daily, 5 minutes: Look at the board. One task in progress, one on deck. Move cards, don’t carry them in your head.
- Midweek, 10 minutes: Check the “waiting on” column. Anything sitting there more than three days gets a follow-up message today.
- Friday, 15 minutes: Definition-of-done sweep. Close out or honestly re-date everything in progress. Note one thing that went wrong and one fix for it — two sentences in the review notes.
- Monthly, 1 hour: Season check. What’s the next busy stretch, and what has to be true before it starts? Schedule slow-season projects into the slow weeks now, while you’re calm enough to mean it.
That’s the whole system: a board, a limit, a checklist, a half hour a week. Everything else in the Agile toolkit was built for coordinating other people — and on the days the team grows, it can come back. Until then, the parts that remain earn their keep every single week.