Agile is simply a way of working where big jobs are broken into small, finishable pieces, the team checks in briefly every day, and everyone sees progress on one board. Scrum is the most popular recipe for doing that — it gives us the words you’ll see in Sprintf: epics, stories, cycles and the board. No software jargon required.
A project is a client engagement, like Northside Merch Capsule. Inside it, epics group the chapters of work — say Apparel artwork or Sampling & press.
Epics are too big to finish in one go. They’re how you keep the map tidy.
A story is one piece of work small enough to finish and check — “Front print tee artwork in 3 colourways”. Each has a clear done check-list so there’s no arguing about whether it’s finished.
Bugs, quick tasks and research jobs sit here too. That’s your backlog.
A cycle (Scrum calls it a sprint) is a fixed two-week run where the team commits to finishing a chosen set of stories — “Ship print-ready apparel artwork and approve strike-offs.”
Each cycle has one goal, so the team always knows what “winning” looks like.
One cycle pulls ready stories from several epics and even several projects — the board simply shows everything the studio has committed to right now. When a story is done, points are tallied so you can see the cycle filling up toward its goal.
Every day starts with a stand-up — a 10-minute huddle, often standing. Each person answers three things: what I finished yesterday, what I’m doing today, and anything blocking me (a missing sample, an unapproved proof, a delayed client answer). Blockers get an owner immediately.
Work moves left to right: To do → In progress → Review → Done. At a glance you can see who has too much on, what’s stuck in review, and how close the cycle is to its goal — no chasing people for status.
Stories carry points — a rough size (1 = tiny, 8 = a chunky job), not a time estimate. Each person has a capacity per cycle, so you can spot an overloaded week before it happens instead of discovering it on deadline day.
Everything not yet in a cycle lives in the backlog, ranked most-important-first. The creative director keeps it ordered; at the start of each cycle the top items are pulled in. New client requests never interrupt the current cycle — they join the queue for the next one.
| Scrum says | In the studio | What they do |
|---|---|---|
| Product Owner | Creative Director | Decides what matters most, ranks the job queue, briefs the team and shields them from mid-cycle changes. |
| Scrum Master | Lead Designer / Account Manager | Runs the rhythm — check-ins, cycle planning, unblocking people so work keeps moving. |
| Developers | Designers, artworkers & printers | The makers. Estimate the work, do it, and move it across the board. |
| Stakeholders | Clients & production partners | See progress on the board, give feedback at the end of each cycle — not mid-cycle. |
Your workspace is already loaded with a studio’s worth of real examples — cycles running right now on four client projects. Open the board and trace a job from story to done.