Scrumlord: your startup, one sprint at a time
Scrumlord is a free, cozy pixel-art management sim where the sprint board is the game board. Run a tiny startup’s dev team: plan sprints, ship features users want, keep the team from burning out, and grow before the runway ends.
Help: how Scrumlord works
- How a sprint works. Every sprint has four steps: Plan, Sprint days, Ship and Retro. Then it starts again.
- Your first sprints. What matters most early on, and the traps new players fall into.
- Story points and capacity. How much work fits in a sprint, and what eats into it.
- Fuzzy tickets and refining. Fuzzy work takes longer and ships more bugs. Refining makes it clear.
- Energy, stress and morale. Tired, stressed or unhappy people work slower, make more bugs and can quit.
- Who picks up what. Specialists are fastest on their own kind of work. Set what people do when they run out.
- Users, happiness and popularity. Popularity brings people in each day, happiness keeps them, and bugs drive them away.
- What users want and interviews. Interviews tell you exactly what a group of users needs, so you build the right things.
- Releases and what they bring. Why one release brings hundreds of users and another almost none.
- Cash, MRR, burn and runway. Revenue comes in, salaries go out. Runway is how long you can keep going.
- Pricing and marketing. Price sets how much each paying user brings; marketing buys attention.
- Code health and stability. Messy code slows everything and breeds bugs; low stability means outages.
- Foundations. Logins, data storage, an API: what your features stand on. Weak ones make everything worse.
- Bugs and outages. Where bugs come from, what escaped bugs cost, and how outages work.
- CEO patience. How much the CEO trusts your calls. Too low and they start overriding you.
- Stakeholders. The CTO, Support and your Head of Growth or Sales each want something. Keep them on side.
- Goals, reviews and stages. What investors want each quarter, and what happens when you hit or miss it.
- Funding and equity. Raising money buys runway but gives away part of the company.
- The Playbook and focus. Cards you play in Get ready, paid for with focus.
- Code health is low. Get it back above 60 so the team stops slowing down.
- Running out of money. Default dead, runway shrinking: how to buy time.
- Users aren’t growing. A big release brought few users, or signups have stalled.
- Happiness is dropping. Unhappy users leave and stop recommending you.
- The team is stressed or quitting. Burnout and quitting cost more than a slower sprint.
- Too many bugs or outages. Bugs keep escaping, or outages keep happening.
- The CEO is losing patience. Win back trust before they start overriding you.
- Behind on the goal. The quarter review is coming and you’re not there yet.
- Work keeps running over. Tickets don’t finish in the sprint you planned them.
- Someone sits idle. A teammate has nothing to do while work is waiting.
Scrumlord needs JavaScript to play.