I almost lost a client last Ramadan after promising a MVP launch in two sprints. I’d forgotten most of us in the UAE don’t stop working during Eid. That week, I realized traditional Agile — the meetings, the ceremonies — doesn’t scale down to solo freelance work unless you’re willing to twist it until it snaps. Here’s what I’ve built after shipping 40+ projects alone in Abu Dhabi: a framework that feels like Agile, but doesn't choke on the fact that my “team” is one overcaffeinated dev with too many Slack channels open.
Breaking Down Solo Sprints
Three years ago, I tried a 2-week sprint for a limo booking platform (Tawasul Limo) and immediately hit a wall. I’d blocked 10 hours for a feature, then spent 6 debugging Firebase auth on iOS — which I hadn’t accounted for in planning. My time-tracking tool? Toggl Track spit out reports showing 40% of my time went to “unplanned overhead.” That won’t fly when your client in Dubai expects daily updates.
Now I do 1-week sprints, no exceptions. Here’s the structure:
- Backlog grooming every Friday — Notion board with all tasks, no vague “build dashboard” tasks. If it can’t be done in a day, it gets split.
- Daily standups at 9:03 AM — Yes, I do them alone. No, I don’t video myself. I write a 3-line update in Slack’s “send to self” then move on.
- Hard deadline Friday at 5 PM — Deliver something. Even if it’s partial. Forces real prioritization.
Tools That Replace the Team
Agile assumes you’ve got people to delegate to. When you’re solo, the wrong tools make you nuts. Here’s what works:
- •GitHub Projects for sprint planning. I treat issues like tickets, even writing “as a user” statements in descriptions. Overkill? Ask me how I kept my sanity during that 11-project quarter in 2023.
- •Linear for tracking blockers. It’s lighter than Jira but still gives me that “status column” dopamine hit.
- •Toggl Track for time tracking. Not because I bill hourly (I mostly fixed-price), but because I need to see where my estimates are trash. Spoiler: It’s always authentication and client feedback cycles.
The Client Who Broke My Sprint
Last year, a construction company in Abu Dhabi wanted their site rebuilt. They signed off on 3 sprints, then suddenly added 6 more features mid-project. Classic. I tried squeezing them into the next sprint until I realized their “priority” features were actually just things their CEO had stumbled onto during a Zoom call.
So I pulled a tactic from Lean: added a “client backlog” column in Linear. Every new request from them went there until sprint planning day. It’s been magic. Forced us to prioritize, and cut their scope creep by 60% without a single awkward conversation.
Timeboxing in the UAE Context
This part’s tricky. Clients here expect speed — I once had a request for “urgent” changes at 2 AM UAE time that would’ve been due before my alarm. So I built “flex zones” into my sprint schedule:
- •48-hour buffer at the end of each sprint. Not for slacking — for the inevitable WhatsApp ping asking to “just tweak the hero text.”
- •Fixed client meetings at 8 AM and 4 PM UAE time, so their morning rush doesn’t bleed into my workflow.
When Ramadan hits? I default to 4-day sprints. Most clients expect downtime, but the ones who push still get progress — just within shorter, realistic windows.
Retrospectives Without the Ceremony
You don’t need a facilitation guide to ask two questions post-sprint:
- What actually took longer than expected?
- What didn't we need at all?
For the MVP that missed its Ramadan deadline, the answer was “too many animations” — the client had forgotten their target audience (UAE residents booking Eid travel) wanted functional, not fancy. We cut three days of polish and hit the real deadline: first business day after Eid.
When This All Slides
I’ll be real — solo sprints blow up all the time. Just last month, my build for a React Native app (Greeny Corner) kept breaking after upgrading to Expo SDK 54. Three mornings disappeared chasing a Metro bundler bug that affected only iOS 17.3 (not on simulator docs!) So the sprint delivered, but the client saw delayed results.
Did I stick to Agile “rules”? Nope. Did I communicate the problem clearly, reprioritize deliverables, and get the app to UAE App Store by week two? Yeah.
Agile isn’t about process purity. It’s surviving reality as a one-person delivery machine.
I’ve kept freelancing sustainable in the GCC using this approach. If you’re drowning in solo workflow chaos and want to talk shop — or need to ship something real without corporate BS — hit up sarahprofile.com/contact.