How a Freelance Art Director Runs Agile Sprints Solo

Last month, three AI image generation projects blew up at the same time. One was package design for a local brewery in Minneapolis, another was branding for a New York startup, and the last was a generative AI art series I'd been experimenting with on my own. Monday morning, when I opened my laptop, my mind went blank. How am I supposed to juggle all of these at once? That's when I remembered the Agile sprints I'd picked up during my agency days. Even though it was just me, not a team.

How I Use Two-Week Sprints as a Solo Practitioner

At the agency, there was a scrum master, and five of us gathered for daily stand-ups. If you try to follow that exact format by yourself, you end up with ritual and no substance. Here's how I actually do it.

• Sprints always start on Monday morning. I sit down with coffee and write on a single sheet of paper what I finished and what I fell behind on over the past two weeks. I use paper instead of a digital tool because the second I turn on a screen, Slack notifications steal my attention.
• Sprint duration is exactly 14 days. I tried one-week cycles at first, but reviewing AI model outputs and working in client feedback takes at least two days, so one-week sprints were too tight.
• Each sprint goal is exactly one per project. For the brewery project, I'd set something specific like "Complete 3 can label mockups." A goal like "Make progress on the design" has no clear endpoint and leaves me anxious on Friday night.

How I Set Up My Kanban Board

I've tried a bunch of Kanban board tools, but I settled on Notion. The reason is simple: I can attach AI prompt logs, client comments, and reference images all within a single card.

I use only four columns: Backlog, This Sprint, In Progress, and Done. I originally created a "Review" column too, but when you work alone, the only reviewer is yourself, so moving cards straight from In Progress to Done turned out to be more realistic. For cards that need client feedback, I add "WAIT" to the beginning of the card title so they stand out visually.

One rule: No more than three cards in In Progress at any time. Beyond that, the context-switching cost gets brutal. This is especially true for tasks involving AI model pipelines — if the flow gets interrupted during prompt setup, result curation, or post-processing, you have to rebuild your feel for it from scratch.

The Strange Habit of Doing Sprint Reviews for Myself

When the two weeks are up, I set aside 30 minutes on Friday afternoon and go through all the completed cards. I write down in three lines what went well, where bottlenecks happened, and what to change in the next sprint. It felt awkward at first — like talking to myself. But after a few months, patterns started showing up. I had a tendency to run too many experiments in the first week and then scramble to meet deadlines in the second. Once I spotted that, I started limiting experimental work to Tuesday of the second week and dedicating the rest to refinement and delivery.

Why Agile Works for a Solo Art Director

It's not because it's some grand framework. It's because the question "What am I going to finish in these two weeks?" keeps me oriented every single day. When you freelance, nobody reminds you of your deadlines. Winters in Minneapolis are long, and when you work alone from home, your sense of time gets hazy. Sprints fill that gap.

AI projects are especially prone to scope creep. You want to run the prompt one more time, swap out the model one more time, and there are endless moments where the output is "almost there, just a little more." Having a sprint end date gives you a real reason to cut that temptation short. You just say, "I'll put it in the next sprint's backlog." Knowing when to stop is a skill, too.

Even as I write this, there are seven cards piled up in Backlog on my Notion board. Next Monday morning, I'll brew my coffee and move three or four of them into This Sprint. That's how my next two weeks begin.