agile.flights: Can Renaming Sprints Save Agile?

2026-03-05 | Product Hunt | Official Website

Screenshot Analysis: This is the agile.flights homepage. The large text at the top, "Ship projects, not status updates," defines its positioning. Below is the core Flight Board, where each row is a "Flight" (a project iteration), featuring a flight number (AF-201), title (User Onboarding Redesign), Captain (Alice Chen), and status (IN FLIGHT / TAKEOFF). It looks just like an airport departure board.

Screenshot Analysis: This is the product's full Dashboard view. On the left is the "IN FLIGHT" list, while the right is divided into "TAKEOFF RUNWAY" (Preparing), "EMERGENCY LANDING" (Urgent), and "LANDED RUNWAY" (Delivered). It visualizes project progress using aviation terminology.

30-Second Quick Judgment

What is this App?: A project management tool that replaces Scrum jargon with aviation metaphors—Sprints are Flights, Releases are Landings, Scrum Masters are Captains, and the Backlog is Ground Mechanics.

Is it worth watching?: If you're a solo user or a small team, it's not worth the hassle of migrating. However, the logic behind it—using language everyone understands for project management—is worth considering for PMs and indie hackers. With only 4 votes on PH, the product is in its infancy; just keep an eye on it for now.

Three Questions for You

Is it relevant to me?

Who is the target user?:

• Small to medium teams (5-30 people) tortured by Jira.
• Companies that want non-technical staff (CEO/Sales/Marketing) to understand project progress.
• Teams tired of Scrum rituals (Daily Standups, Retrospectives, Sprint Planning).

Am I the target?: If you often have to explain "what Sprint Velocity is" to your boss, or if your Jira board has become a task graveyard, you might be the target. But if you're a solo dev or your team is already running smoothly, this isn't for you.

When would I use it?:

• Reporting progress to the CEO in weekly meetings—"Flight AF-201 is expected to land Friday" is much easier to grasp than "Sprint 23 has 5 story points left."
• Cross-departmental collaboration, letting Marketing/Sales see dev progress at a glance via the Airport Board.
• Teams that want to skip daily standups but still need visual progress.

Is it useful to me?

ROI Judgment: Not worth it at this stage. The product is too early (4 votes) and lacks a mature ecosystem. However, if you're building a team process from scratch, you can check out the Flights methodology itself (free Medium articles) without necessarily using the tool.

Is it enjoyable?

The "Wow" Factor:

• Intuitive Aviation Metaphors: Saying "The flight hit turbulence and is expected to land late" is a hundred times more vivid than "The Sprint is incomplete and needs to carry over to the next iteration."
• Airport Board: The core view of the product allows you to see the status of all projects at a glance, just like looking at a flight information board at an airport.

The "Aha!" Moment:

From the website: "Your CEO never understood sprint velocity. They instantly understand 'we expect headwinds, but the flight lands Friday.'" — This line hits home for countless PMs tortured by Jira.

Real User Feedback:

The product just launched; zero mentions on Twitter, and discussions are just starting on HN. This is a product that hasn't been user-validated yet. An HN post mentioned: "it's not new; someone tried it back in 2021" — suggesting the community is skeptical of "old concepts in new packaging."

For Indie Hackers

Tech Stack

• Frontend: Web app, dark-themed Dashboard, specific framework not disclosed (Founder Simon Høiberg specializes in React/TypeScript/Node.js).
• Backend: Not disclosed (likely Node.js/TypeScript full-stack based on founder's background).
• AI/Models: No AI features, pure project management tool.
• Infrastructure: SaaS hosted, cloud provider not disclosed.

Core Feature Implementation

Essentially, this is a variant of a Kanban Board. The core logic is straightforward:

1. Each "Flight" is a task container with a timeframe (takeoff/landing date).
2. The Flight Board is a multi-lane Kanban (In Flight / Takeoff Runway / Emergency Landing / Landed).
3. Captain/Crew is the role and permission system.
4. Ground Mechanics is a task list that doesn't belong to any specific Flight.

Technically, there isn't much innovation; the core selling point is "metaphorical design" rather than technical implementation.

Open Source Status

• Is it open source?: No. agile.flights has no public GitHub repository.
• Open Methodology: The Flights methodology itself is public (The Flight Manual), and anyone can use it.
• Similar Open Source Projects: Plane (Open source Jira alternative, 8k+ stars), Taiga, Focalboard.
• Difficulty to build yourself: Low to Medium. An MVP could likely be built in 1-2 person-months. The core is a multi-lane Kanban with roles; the technical barrier is low.

Business Model

• Monetization: Freemium (Free + Upgrades).
• Pricing: Free to start; specific paid pricing not disclosed.
• User Base: Extremely early stage, only 4 PH votes, no public user data.

Giant Risk

High risk. If Jira, Linear, or ClickUp created an "Aviation Theme" template or view, they could achieve 80% of the functionality. The moat for this product isn't technology; it's the evangelism of the methodology and community building. If the Flights methodology doesn't gain enough followers, the tool will struggle to survive.

For Product Managers

Pain Point Analysis

• Problem Solved: Non-technical staff don't understand agile jargon, leading to high cross-departmental communication costs.
• Severity: Moderate, "nice-to-have." Most teams solve this by "making a progress PPT" rather than "changing the terminology." The real pain is Jira's complexity, but lightweight alternatives like Linear already exist.

User Persona

• Ideal User: Tech companies with 10-50 people where the CEO/CTO wants the whole company to see dev progress.
• Use Cases: Cross-departmental meetings, CEO weekly reports, project visualization.

Feature Breakdown

Competitor Comparison

Key Takeaways

1. Metaphorical Design: Replace professional jargon with everyday language to lower cognitive barriers. This can be applied to any SaaS onboarding.
2. Airport Board View: Turn project status into an "at-a-glance" dashboard rather than detail pages requiring multiple clicks.
3. De-ritualization: Don't force daily standups and retrospectives; trust the team to decide their own communication style.

For Tech Bloggers

Founder Story

• Founder: Simon Høiberg, Danish, currently living in Zurich, Switzerland.
• Background: Former Senior Software Engineer at LEGO Group and TV 2 Danmark. Transitioned from a $300K/year freelancer to a SaaS entrepreneur.
• Notable Works: FeedHive (Social media management, $1M+ ARR), Aidbase (AI customer service, $5K MRR in 3 weeks), Galaxies.dev (React Native education, 100k+ developers).
• Why build this?: Created the Flights methodology internally at FeedHive with co-founder Simon Gronborg in 2021. After using it for years and liking the results, he productized it into a standalone tool in 2026.

Controversies / Discussion Angles

• "Old Wine in New Bottles" Debate: What actually changes by calling a Sprint a Flight? Is it the power of language or just self-deception?
• Agile Fatigue: More teams are getting tired of Scrum rituals—is this an industry trend or an isolated phenomenon?
• The Power of Naming: Can good naming really change how a team collaborates? (Ref: OKR vs. KPI naming debate).
• The Serial Entrepreneur's Journey: How Simon Høiberg went from $300K freelancing to $1M ARR SaaS.

Traction Data

• PH Ranking: 4 votes, almost no traction.
• HN Discussion: Show HN post just went up, in the "freshly baked" stage.
• Twitter Discussion: Zero direct mentions.
• Search Trends: Extremely low; the product hasn't entered the public eye yet.

Content Suggestions

• Best Angle: "Why Dev Teams are Ditching Scrum" — Use agile.flights to discuss the broader trend of agile fatigue.
• Trend Jacking: Low opportunity unless the HN post goes viral; otherwise, there's not enough heat for a dedicated article.

For Early Adopters

Pricing Analysis

Getting Started Guide

• Time to Start: Estimated 10-15 minutes (clean interface).
• Learning Curve: Low (if you understand Kanban, it's just different terminology).
• Steps:
  1. Visit agile.flights, click "Start for Free" to register.
  2. Create your first Flight (set title, takeoff/landing dates, assign Captain).
  3. Add Crew members and tasks.
  4. View the global status on the Airport Board.

Pitfalls and Complaints

1. Too Early: The product just launched; features may be incomplete, and bugs are likely.
2. No Integrations: No visible integrations with Slack, GitHub, GitLab, etc.
3. Migration Cost: If you're currently using Jira/Linear, there's no clear data migration path.
4. Small Community: Only a Slack community exists; questions might go unanswered for a while.

Security and Privacy

• Data Storage: Not explicitly stated (SaaS Cloud).
• Privacy Policy: Not prominently displayed on the website.
• Security Audit: No public information.
• Advice: Use with caution for sensitive project data given its early stage.

Alternatives

For Investors

Market Analysis

• Sector Size: Agile project management software market $5.9B in 2025, expected to reach $14.7B by 2032.
• Growth Rate: 13.9% CAGR (2025-2032).
• Drivers: Remote work, AI integration, penetration of agile methodologies into non-tech industries.

Competitive Landscape

Timing Analysis

• Why now?: Agile fatigue is a real trend. More teams are complaining about Scrum rituals on Twitter/HN. The rise of Linear (valuation $4B+) proves there is a massive market for "simplified agile."
• Tech Maturity: Project management tech is very mature; innovation here is in methodology, not tech.
• Market Readiness: Methodology-based products require long-term evangelism. The Flights methodology was proposed in 2021 and hasn't spread widely, suggesting questionable market acceptance.

Team Background

• Founder: Simon Høiberg, serial entrepreneur with successful exit experience.
• Key Achievements: FeedHive $1M+ ARR (bootstrapped), Aidbase $5K MRR in 3 weeks.
• Team Size: Not disclosed, likely a small team or solo.

Funding Status

• Raised: Not disclosed, likely bootstrapped (Simon is famous for bootstrapping).
• Investors: No public information.
• Risk: Low product differentiation; core selling point (metaphorical naming) is easily copied.

Conclusion

One-line Judgment: The Flights methodology is an interesting idea, but as a tool, it's too early and lacks differentiation. It's currently better as a Medium article to read than a tool to use.

Resource Links

2026-03-05 | Trend-Tracker v7.3