Kanban vs. Scrum: Devlog Progress Tracking Showdown

Posted by Gemma Ellison

August 4, 2025

Kanban vs. Scrum: Devlog Progress Tracking Showdown

Indie game development is a wild ride. You juggle coding, art, sound, and marketing, often solo. That’s why choosing the right progress tracking method for your devlog is crucial. Over-planning and rigid methodologies can kill creativity. Let’s dive into Kanban and Scrum to see how they can be adapted for indie game devs.

Kanban: Visualizing Your Workflow

Kanban is a visual system for managing your work. It focuses on visualizing your workflow, limiting work in progress (WIP), and continuous improvement. The core idea is to move tasks through a board, typically with columns like “To Do,” “In Progress,” and “Done.”

Think of it as a visual to-do list that reflects the actual state of your tasks. No sprints, no fixed roles. Just constant flow.

For solo devs, Kanban is incredibly flexible. It allows you to react to changing priorities without the overhead of formal meetings and planning.

Kanban’s core principles:

Visualize the workflow: Use a board (physical or digital) to see your tasks.
Limit work in progress: Focus on finishing tasks before starting new ones.
Manage flow: Keep tasks moving smoothly through the workflow.
Continuous improvement: Regularly review your process and make adjustments.

Strengths:

Highly adaptable to changing priorities.
Simple to set up and use.
Good for solo developers or small, self-organizing teams.

Weaknesses:

Can lack structure if not managed well.
Requires discipline to limit WIP.
May not be ideal for projects with strict deadlines.

Adapting Kanban for Indie Game Dev:

Customize columns: Tailor the columns to your specific needs (e.g., “Concept,” “Prototyping,” “Art,” “Programming,” “Sound,” “Testing,” “Polish”).
Limit WIP: Don’t start new features until existing ones are complete. This avoids context switching and improves focus.
Prioritize ruthlessly: Constantly re-evaluate your backlog based on playtesting feedback and market demands.
Embrace imperfection: Don’t get bogged down in perfecting every detail. Focus on getting a playable build out and iterating.

Kanban Template Example:

To Do: Implement enemy AI, create title screen art, design level 2.
In Progress: Animating player character, composing background music.
Testing: Level 1 gameplay.
Done: Player movement implemented, basic UI created.

Scrum: Iterative Development with Sprints

Scrum is an iterative framework that uses short cycles called sprints (typically 1-4 weeks) to deliver incremental pieces of functionality. It involves specific roles (Product Owner, Scrum Master, Development Team) and ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective).

Scrum aims for structured development and predictable delivery. It promotes teamwork, accountability, and continuous learning.

For solo developers, Scrum can be adapted to provide structure and focus, especially when facing larger projects. You can act as all three roles, adapting the ceremonies to fit your workflow.

Scrum’s core principles:

Iterative development: Work in short sprints to deliver incremental value.
Self-organizing teams: Empower the development team to make decisions.
Continuous improvement: Regularly review the process and make adjustments.
Timeboxing: Allocate fixed time periods for tasks and ceremonies.

Strengths:

Provides structure and predictability.
Encourages collaboration and communication (if working in a team).
Good for projects with clear goals and requirements.

Weaknesses:

Can be too rigid for highly experimental projects.
Requires commitment to ceremonies and planning.
May be overkill for small projects or solo developers.

Adapting Scrum for Indie Game Dev:

Short sprints: Keep sprints to 1-2 weeks to maintain focus and agility.
Simplify roles: As a solo dev, you’re all roles!
Streamline ceremonies: Replace lengthy meetings with short, focused check-ins with yourself.
Focus on a Minimum Viable Product (MVP): Prioritize the core features needed to make the game playable.
Embrace imperfection: Don’t be afraid to release incomplete features and iterate based on player feedback.

Scrum Template Example:

Sprint Goal: Implement basic combat system and create one playable level.
Sprint Backlog: Implement player attack animations, create enemy AI, design level layout, add basic sound effects.
Daily Scrum (Daily Check-in): What did I do yesterday? What will I do today? Are there any impediments?
Sprint Review: Playtest the completed level and gather feedback.
Sprint Retrospective: What went well? What could be improved?

Kanban vs. Scrum: Which is Right for You?

The best approach depends on your individual needs and project.

Choose Kanban if: You prefer flexibility, have rapidly changing priorities, and work best with a visual workflow. It’s often a great starting point for solo devs.
Choose Scrum if: You need more structure, want to deliver incremental value regularly, and benefit from defined roles and ceremonies. Adapt it by shortening sprints and simplifying roles when working solo.

Common Pitfalls and How to Avoid Them:

Over-planning: Don’t spend too much time planning upfront. Embrace iterative development and adjust your plans as you go.
Scope creep: Avoid adding new features mid-sprint (Scrum) or without careful consideration (Kanban). Focus on delivering core functionality first.
Feeling overwhelmed: Break down large tasks into smaller, manageable chunks. Celebrate small victories to maintain motivation.
Ignoring feedback: Playtest your game early and often. Use player feedback to guide your development decisions.

Documenting Your Journey: The Devlog Advantage

As you experiment with Kanban or Scrum (or a hybrid!), documenting your process is crucial. This is where your devlog comes in.

A consistent devlog is a powerful tool. It tracks progress, promotes your game, and provides valuable insights. It’s also a great way to stay motivated by seeing how far you’ve come.

Embrace imperfection in your devlog. Don’t be afraid to share your struggles and mistakes. Authenticity builds trust with your audience.

Remember, documenting your process, both for your team and yourself, forms the basis for your devlog and helps in retrospectives. It can even aid in project planning and forecasting.

Ready to capture and learn from your daily work? Start tracking your game development progress with our game dev journal tool today!game dev journal tool It’s designed to help you stay organized, reflect on your progress, and create compelling devlogs.