// description
An Agile framework for managing complex work through time-boxed iterations called sprints (typically 1–4 weeks), regular team ceremonies (stand-ups, sprint planning, retrospectives), and clearly defined roles (Product Owner, Scrum Master, Development Team).
// history
Jeff Sutherland created Scrum in 1993 at Easel Corporation, drawing on a 1986 Harvard Business Review article by Takeuchi and Nonaka that used a rugby "scrum" metaphor for high-performing teams. Sutherland and Ken Schwaber co-presented the first formal Scrum paper in 1995 and co-authored the Scrum Guide, first published in 2010. Scrum is now the most widely used Agile framework, with millions of certified Scrum practitioners globally.
// example
A solo creator planning a new digital product course: sprint 1 — outline all modules and record module 1. Sprint 2 — record modules 2–3, build sales page draft. Sprint 3 — record remaining modules, complete sales page, set up Gumroad. Sprint 4 — launch beta to email list, gather feedback. Each sprint ends with a retrospective: what worked, what didn't, what to change next sprint.
// katharyne's take
I don't do full Scrum because I'm a team of one, but the sprint concept is gold. I do two-week sprints with a very short "what am I actually shipping this fortnight?" list. It forces prioritisation and stops me from having 47 half-finished projects in flight simultaneously (a real problem I have had). The retrospective is the part most people skip — don't skip it. It's where the learning actually happens.
// creative uses
- Plan your next KDP book as a four-sprint project: sprint 1 — niche research and outline, sprint 2 — interior design, sprint 3 — cover and metadata, sprint 4 — upload, keyword testing, and first 30-day review. Each sprint has a specific deliverable so nothing stalls in "nearly done."
- Use sprints for Etsy shop growth: run a two-week sprint with one goal — refresh the five worst-performing listings. Next sprint: add five new listings in a tested niche. Sprint planning stops the scattergun approach of doing everything ineffectively at once.
- Apply the sprint retrospective to your weekly newsletter: after each send, spend 10 minutes noting open rate, click rate, any replies received, and one thing to change next week. That retrospective habit compounds into dramatically better email performance over 12 months.
// quick actions
- Define your next two-week sprint right now. Write three things — not fifteen — that you will complete and ship in the next 14 days. Put them in Notion or a sticky note where you'll see them daily. Nothing else is a priority until those three things are done.
- Set a recurring 20-minute calendar block on the last day of every sprint for your retrospective. Write three sentences: what shipped, what slowed you down, what you'd change. Review these monthly to spot patterns in your own productivity blockers.
- Build a sprint backlog in Notion: a master list of everything you want to create or improve, ranked by impact. Each sprint, pull only the top items. Everything else waits. The backlog prevents shiny object paralysis.
// prompt ideas
Help me plan my next two-week Scrum sprint for my creator business. My top priorities right now are: [list everything on your plate — product work, marketing, admin, community]. Apply sprint planning logic: identify the three to five tasks that will actually ship something real in 14 days, move everything else to the backlog, and give me a sprint goal sentence that describes what "done" looks like at the end of this sprint. Also flag any task that's too vague to be sprint-ready and help me break it down.
Design a solo Scrum system for a creator who produces [KDP books / Etsy digital products / online courses]. I want a lightweight version that fits in Notion: a sprint backlog structure, a two-week sprint planning template, a daily check-in question, and a 20-minute sprint retrospective format. Keep it minimal — I'm a team of one and I need something I'll actually use, not a full agile process built for a software team.
Run a sprint retrospective with me for the last two weeks of my creator work. I'll describe what I worked on: [describe what you did, what shipped, what didn't, and what slowed you down]. Ask me the retrospective questions — what went well, what didn't, what I'd change — then synthesise my answers into three actionable changes for next sprint and identify any pattern that's been a recurring blocker across multiple sprints.