Scrum, Kanban… or Firehouse?
Presenting an Agile Alternative for Startups
Scrum and Kanban are excellent Agile frameworks widely used in software development. Each brings value in different ways: Scrum is highly effective for project-based work with structured sprints, while Kanban excels in managing continuous, ongoing work with a focus on flow. However, after working with two startups, I believe there’s a need for an Agile methodology that more closely resembles the dynamic and adaptive nature of a firehouse responding to emergencies. Startups, after all, often feel like they’re constantly “fighting fires.”
Below, I’ll break down the differences and explain why the Firehouse Methodology might be the better approach for startups navigating rapid growth, shifting priorities, and the unpredictability of development cycles.
| Feature | Scrum | Kanban | Firehouse |
|---|---|---|---|
| Structure | Fixed, with roles and sprints | Flexible, continuous flow | Fixed, but with adaptable roles |
| Planning | Sprint-based | Task-based, continuous | Project-based with adaptable tasks |
| Roles | Defined roles | No defined roles | Defined roles that adapt based on needs |
| Tracking | Sprint Backlog & Burndown Chart | Kanban Board & WIP limits | Kanban Board with “Situation Radio” communication |
| Flexibility | Limited during sprints | High; tasks reprioritizable | High; tasks and roles can be adapted quickly |
| Best For | Project-based work | Ongoing work, support, maintenance | Startups dealing with rapid, unpredictable changes |
Structure: Fixed but Flexible Like a Firehouse
In a startup, the team is typically small, often including founders with the vision, a CTO or technical lead, and an outsourced development team. In the Firehouse Methodology, we define roles similar to those in a firehouse:
- Chief – The founder or visionary, responsible for the overarching project vision and defining what “completion” looks like.
- Captain – Often the CTO, who translates the project vision into actionable tasks, assigns these to the team, and monitors progress.
- Firefighters – The development team, whose role is to carry out tasks, report progress, and tackle any “fires” as they arise.
This firehouse-style structure ensures that everyone has clear roles while maintaining the flexibility to jump in and help where needed. Like firefighters, team members should constantly assess their contributions, anticipate challenges, and be ready to support each other.
Why Firehouse Terminology? Because, much like fighting a fire, startup development rarely goes as planned. Unexpected challenges are inevitable, and flexibility is crucial. In this structure, everyone understands the entire project and can step in to help when issues arise, breaking down silos and encourages a true sense of teamwork.
Planning: Structured Yet Adaptable
In a startup, there’s usually a clear vision but an ever-changing roadmap. With the Firehouse Methodology, planning incorporates flexibility from the outset. Just as firefighters arrive at a blaze with an initial strategy but adapt to circumstances, the startup team must be prepared to adjust as issues arise.
The Chief and Captain should anticipate potential challenges in the planning phase and outline adaptive options for each task. Although they might not know the specific adjustments needed, they establish an environment ready for the unknown.
When the inevitable issues arise, communication flows clearly and transparently across all levels. This allows everyone, including Firefighters, to have input on how to tackle challenges as they emerge. It’s a whole-team approach where every voice matters, enabling more informed, responsive planning.
Roles: Defined with Built-in Flexibility
Roles in the Firehouse Methodology provide a clear hierarchy, yet they allow for flexibility when required.
- Clear Responsibilities: Each role (Chief, Captain, Firefighter) has specific responsibilities, making decision-making smoother.
- Global Awareness: Team members stay aware of the overall project and each other’s work, creating a shared understanding of the “big picture.”
- Cross-Functional Support: Unlike in more rigid frameworks, anyone can jump in to assist others as needed. If a Firefighter is overwhelmed, others can help, avoiding bottlenecks.
This adaptability in roles helps prevent delays and keeps quality high, addressing a common problem in startups where rapid development often leads to unfinished or buggy features. This framework encourages high-quality work and a collaborative culture, ensuring the team delivers a sustainable, polished product.
Tracking: Kanban Board with “Situation Radio”
A Kanban board is an effective tracking tool for startups, and Trello is a popular choice that integrates well with the Firehouse approach. However, in addition to using a Kanban board, the Firehouse Methodology emphasises broadcast communication—an ongoing “Situation Radio.”
This means creating a live, open communication channel (e.g., a Discord voice channel) that keeps all team members informed of ongoing issues, even when they’re not directly involved. This mirrors how firefighters stay in constant radio contact, enabling the whole team to hear and respond to updates in real-time.
Unlike traditional communication, where team members only see updates when they check the Kanban board, this “Situation Radio” makes it easy for everyone to stay aware of emerging challenges and contribute to solving them faster.
Important Note: For efficiency, team members should mute their microphones unless they’re actively participating in a conversation to avoid unnecessary noise.
Flexibility: The Foundation of Firehouse
In the Firehouse Methodology, flexibility is key. Startups need adaptability across roles, tasks, and even team attitudes.
- Flexible Roles: As outlined, roles are defined but flexible. Members pitch in wherever needed to keep the project moving smoothly.
- Adaptable Tasks: Tasks can be redefined based on new insights or shifting priorities. This helps maintain alignment with the project’s goals, even as they evolve.
- Mindset Flexibility: It’s important to encourage a collaborative attitude. Even leaders need to stay open to input from others. A rigid “this is my role” mindset can stifle innovation and productivity. For example, if a Chief or Captain is unintentionally causing a bottleneck, they need to adapt and listen to feedback from team members to avoid creating further obstacles.
By balancing defined responsibilities with a flexible, team-oriented mindset, the Firehouse Methodology supports startup teams in navigating unknowns more effectively. It ensures that each team member is empowered to contribute, keeping the project agile and responsive.
Conclusion: Why Firehouse?
In a startup, navigating the unexpected is as constant as it is in firefighting. The Firehouse Methodology recognises this, structuring the team to act with both foresight and flexibility. With this approach, you can:
- Maintain a clear yet flexible organisational structure.
- Keep a broad view of project goals with a Kanban board and live “Situation Radio” communication.
- Empower every team member to take action, support others, and adapt to evolving challenges.
When a “fire” (unexpected issue) emerges, everyone is informed and can act quickly to resolve it. The Firehouse Methodology isn’t just a workflow—it’s a way to keep your team aligned, adaptable, and resilient, ensuring that no matter what surprises arise, you’re ready to tackle them as a cohesive unit.
