The agile project management tool that is just a fast issue tracker

Search for an agile project management tool and the results tell you what the category has become: Jira, Asana, monday, ClickUp, Zenhub, Azure DevOps, each pitched as a platform that can do everything a whole company might ever need. Backlogs and boards, yes, but also timelines, portfolios, dashboards, resource planning, forms, docs, goals, and a marketplace of add-ons on top. The tool grew to fit every team in the building, and somewhere in there the actual job (track the work, run the sprint, ship) got buried under the parts you will never touch.

This post makes the opposite case. For most software teams, the right agile tool is the small one: a fast issue tracker with real, time-boxed sprints and a real command line, and nothing else you have to configure, grow into, or pay for before it helps you. Agile was supposed to be lightweight. The tooling forgot.

#What "agile project management tool" usually means, and why that is the problem

The phrase covers a wide spread. On one end you have Jira, the industry standard for software teams: deeply customizable, built for Scrum and Kanban and scaled frameworks like SAFe, and heavy enough that it needs an administrator. On the other you have the everything-apps (ClickUp, monday, Asana) that market ten different views and pitch themselves to marketing, ops, and HR as much as to engineering. What they share is a direction: more surface, more configuration, more that has to be set up before the thing does its one job.

The result is a familiar tax. The board is fine, it is always fine, but it arrives wrapped in a planning suite you did not ask for. New engineers spend their first week learning the tool instead of the codebase. Half the fields on an issue are mandatory and nobody remembers why. The dashboard reports up to someone who does not read it. None of that moves a card from To Do to Done, and all of it is friction on the one workflow you actually run every day.

Agile methodology is deliberately minimal: short iterations, working software, respond to change. The tooling that grew up around it went the other way, and "agile project management tool" now mostly means "a large platform that happens to include a board."

#The smaller thing: a tracker, not a platform

Here is the version worth wanting. An agile tool is doing its job when it gives you exactly four things and gets out of the way:

• Issues you can create in a second. A title, an owner, a priority, an estimate if you use them. Not a fifteen-field intake form.
• A board and a list over the same work. Board when you want the at-a-glance flow, list when you want to scan and sort. Same issues, two layouts, no migration between them.
• Real sprints. A time-boxed cycle with a start and an end that scopes the board to this iteration, not the entire backlog. That boundary is what makes a board agile rather than an endless pile.
• A way to drive all of it without the mouse. A real command line, so filing and updating work is something you can script, not a chore you click through.

Notice what is not on that list: roadmaps, portfolios, resource-allocation grids, burndown dashboards, goal-tracking, a docs wiki. Those are the features that turn a tracker into a platform, and a platform is a different, heavier thing than most engineering teams need. The smaller tool is not a stripped-down version of the big one. It is the correct size, chosen on purpose.

This is the honest place to say what Radial actually ships, because "just a fast issue tracker" has to mean something concrete. Radial gives you issues, board and list layouts, Cycles (time-boxed sprints with a start and an end), estimates, a triage step for unsorted work, priorities, projects, and Git integrations that link branches, commits, and PRs to issues. That is a genuine agile workflow: plan the cycle, run the board, ship, reset. Radial does not ship burndown or velocity charts, scrum dashboards, roadmaps, timelines, milestones, or a portfolio suite, and that is a design decision, not a backlog we are racing to clear. If a burndown chart reporting up to leadership is load-bearing for your team, Radial is honestly the wrong tool and Jira exists for exactly that. If what you want is the board and the sprint minus the everything-suite, that is the whole product.

#The part almost no agile tool gets right: the command line

Sprints and boards are table stakes. The thing that separates a tracker you fight from a tracker you forget you are using is whether you can drive it from where you already work: the terminal.

When the board lives behind a web app you can only click, keeping it current is manual labor. Someone drags a card in a meeting; someone updates a status after the fact; the board drifts from reality between standups. When the tracker has a first-class CLI, the board updates itself as a byproduct of the work, because filing and moving issues is just another command in the same shell where you run your tests and your git.

Every Radial command takes --json, and issues carry a --cycle, so you can file work straight onto the current sprint and read the board back as data:

# File an issue onto sprint 14's board, high priority, with an estimate
radial create "Rate-limit the export endpoint" -t ENG -p high --cycle 14 --estimate 3 --json

# Read that sprint's in-progress work back as JSON you can pipe anywhere
radial list --cycle 14 --status "in progress" --json

Because --json is on everything and the cycle is just a flag, the board stops being a place you visit and becomes something you script. A CI job files a failing-build issue directly onto the sprint. A pre-commit hook checks what is on your plate this cycle. And your coding agent does the same operations over MCP, filing and moving cards using the identical API a human uses. Every credential is a client of the API, not a billed seat, so your agents ride free: there is no per-agent charge for letting Claude Code or Codex keep the board current.

#The bill should be boring too

Agile pricing has quietly gotten complicated. Most tools are per seat per month, and most now meter AI work on top of that, a credit allowance per seat, a separate charge for the agent that touches the board, a tier you get bumped into when your team grows. The number you sign up for stops being the number you pay.

Radial is one number: $50 per user, per year, flat, billed annually, locked at the rate you join. No per-agent seats, no AI credits, no usage meter, because there is no AI in the product to meter. That is backed by the Plain Software Pledge, written down: the day Radial ships a copilot, meters your usage, or charges you for AI you did not ask for, your subscription is free. This is not anti-AI. Your agent doing real work on the board is exactly the point. The intelligence lives in your agent, over the CLI and MCP, not billed inside the tracker.

#FAQ

#What is an agile project management tool?

An agile project management tool is software that helps a team plan, track, and deliver work iteratively, using frameworks like Scrum or Kanban. In practice that means a backlog, a board (columns for status, cards for issues), and time-boxed sprints, so the team can see what is queued, in progress, and shipped this iteration. The category ranges from focused issue trackers to large everything-platforms that bundle roadmaps, dashboards, and resource planning on top of the board.

#What are the top agile project management tools?

The tools that dominate the category are Jira (the customizable industry standard for software teams), Asana and monday and ClickUp (broad everything-suites that serve many departments), and developer-centric options like Zenhub (GitHub-integrated) and Azure DevOps (tied to the Microsoft stack). They differ mostly in how much surface they add around the board. Radial sits at the focused end on purpose: a fast issue tracker with real sprints and a first-class CLI, without the portfolio and dashboard suite.

#Do you need a heavyweight tool to run agile?

No. Agile methodology is deliberately minimal, short iterations, working software, responding to change, and the tooling only needs to support that: issues, a board, and a time-boxed sprint. Heavyweight platforms add roadmaps, dashboards, and resource planning that most engineering teams never use, and that surface becomes setup cost and ongoing friction. A focused tracker with real Cycles covers the actual agile workflow with far less to configure.

#What is the difference between a scrum board and a kanban board in an agile tool?

Both are column-and-card boards; the difference is the time-box. A kanban board is continuous, work flows in and out with no reset. A scrum board is scoped to a sprint: you pull a fixed set of work onto it at the start of the cycle and reset at the end. A good agile tool gives you both layouts over the same issues so you do not have to choose upfront. Radial covers this with board and list layouts plus Cycles; see a fast board and real sprints, without the scrum tax for the full breakdown.

#Can you drive an agile tool from the command line?

Most cannot, at least not as a first-class path. Radial can: every command takes --json and issues carry a --cycle flag, so you can file, list, and update work on the current sprint from the terminal, a CI job, or a git hook, and read the board back as structured data. Your coding agent can perform the same operations over MCP using the identical API, and because agents are clients rather than billed seats, they ride free.

#The short version

Most agile project management tools grew into platforms: a board wrapped in a planning suite you have to configure, grow into, and pay a climbing bill for. The smaller thing is often the right thing, a fast issue tracker with real sprints and a real command line, sized to the job instead of the org chart. Radial ships issues, board and list layouts, Cycles, estimates, projects, and Git integrations, scriptable from the terminal and drivable by your agents, at one flat locked $50 per user per year with no AI meter. It does not ship burndown charts, roadmaps, or dashboards, on purpose.

See the one number on pricing, or read how the same CLI turns the tracker into something you script in engineering project management without the overhead.