Swizec Teller - a geek with a hatswizec.com

Senior Mindset Book

Get promoted, earn a bigger salary, work for top companies

Senior Engineer Mindset cover
Learn more

    Sprint vs Shape Up vs Kanban

    Whenever I talk about sprints, someone mentions Shape Up and how it's so much better. Same thing, different name 🤷

    Shape Up suggests 9 week iteration cycles followed by 3 week cool-down periods for self-directed work. This is great!

    So you have a 9 week [business] sprint followed by a 3 week [technical] sprint. How is that different?

    Ignore the names, focus on the iteration cycles.

    Iteration cycles work

    All these methodologies are exactly the same idea. It’s all about "Hey we shouldn’t lock ourselves in the basement for months and code in silence with zero input from users or stakeholders. What if we build things, show them, get feedback, and iterate?"

    Kick the can style

    And yes sprints when done well offer a mix of intensity followed by cool down. That's just basic burnout management – Peak Performance is a good book on this.

    To grow you need periods of high intensity followed by periods of recovery and consolidation. Any athlete can tell you this. It's even how we build successful systems – Ball of Mud first, fix later.

    AND when you get it right, there’s plenty of time for self-directed work. You need slack in the system otherwise it breaks down. This is just basic lean :) (or queue theory)

    Yes, yes there is also kanban. The same thing applies: Successful projects will have iteration cycles and unsuccessful projects will linger In Progress for months.

    Well-done sprints are nice

    All the best engineers I know create iteration cycles and ask for feedback every week or two. Even if it's under 1 kanban ticket that takes 9 weeks.

    The benefit of sprints is teaching this behavior to less experienced engineers (and stakeholders). They:

    Plus sprints are not dogmatic. They're guidelines.

    Do 1 week, do 3 weeks, 9 weeks is fine. The point is to ship regularly and get feedback.

    And hey guess what, projects can span multiple sprints. It's fine. At least you ship something :)

    Cheers,
    ~Swizec

    Published on March 26th, 2025 in Teamwork, Mindset, Scaling Fast Book, Reader Questions

    Did you enjoy this article?

    Continue reading about Sprint vs Shape Up vs Kanban

    Semantically similar articles hand-picked by GPT-4

    Senior Mindset Book

    Get promoted, earn a bigger salary, work for top companies

    Learn more

    Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.

    Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.

    Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.

    Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev

    Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization

    Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections

    Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created by Swizec with ❤️