
- Linear
- Scrum
Linear is a brilliant tool. Here is when it is not your tool
Linear is fast, polished and loved by product teams. But it has no free viewer seat and is built for one kind of team. Here is when a different tool fits better.
The Scrumpy blog
Practical writing on sprint planning, backlogs and running an agile team, from the people building a scrum tool you will actually enjoy.

Linear is fast, polished and loved by product teams. But it has no free viewer seat and is built for one kind of team. Here is when a different tool fits better.

Zenhub adds real scrum reporting to GitHub issues, but it works only with GitHub and bills for every seat. Here is the lock-in to weigh before you commit.

How long should a sprint be? The Scrum Guide caps it at a month, but the real answer is a trade-off between fast feedback and meeting overhead. Here is how to choose and commit.

GitHub Projects lives right next to your code and handles iterations, but has no native burndown or velocity. Here is where a scrum team hits its limits.

Notion has a real native Sprints feature now, but no story points, velocity or burndown. Here is how far it takes a scrum team and exactly where it stops.

Burn-up and burndown charts both track a sprint but answer different questions. Here is how they differ, why a changing scope exposes the gap, and which one to trust.

How to write a user story that is clear enough to build: the As a / I want / so that format, when to drop it, writing acceptance criteria, and splitting stories that are too big.

Monday.com looks affordable per seat, but a three-seat minimum and a separate product for real scrum change the math. Here is the honest total for a small team.

What a definition of done and a definition of ready actually are, how they differ from acceptance criteria, and how to keep both short enough that a team will use them.

Asana approximates scrum with templates and custom fields, but has no native story points, sprint object or automated velocity. Here is what that costs a scrum team.

Trello is a joy for simple kanban, but it has no native sprints, story points, velocity or burndown. Here is what changes when your team needs real scrum.

A guide to the sprint retrospective that leads to real change: a simple format, the one rule that keeps it honest, and how to avoid the same complaints every sprint.

A practical guide to the daily standup: what it is really for, how to keep it short, why the three questions go wrong, and how to make it useful for remote teams.

Jira, Linear and Zenhub charge a full seat for anyone who just wants to view the board. Here is why read-only access should be free, and which tools get it right.

A practical guide to backlog refinement: what it is, how often to do it, what a refined item looks like, and how to stop your backlog turning into a dumping ground.

ClickUp bundles docs, whiteboards, dashboards and sprints into one app. Here is why that breadth turns into overwhelm for scrum teams, and when a focused tool wins.

Do you need scrum as a solo developer or a two-person team? What is worth keeping, what is pure ceremony overhead, and how to run a light board on your own.

Scrum vs Kanban explained simply: how they really differ, when each one fits, whether you can mix them, and how to choose without overthinking the framework.

Give any external system a team-scoped API key and let it create stories in your backlog. Perfect for turning a support form or ticket inbox into ready-to-work stories, with the requester tracked automatically.

Story points explained without the jargon: what they are, why teams use them instead of hours, how to start estimating, and the mistakes that make them useless.

Scrumpy now has an AI writing assistant built into the board. Turn rough notes into clear stories, dictate by voice, and teach it your team's style. Included, not a paid add-on.

Jira too complicated for your team? Here is why it feels heavy, what it really costs, and how to move to a simpler scrum tool without losing a single issue.

A practical sprint planning checklist and meeting agenda: what to do before, during and after, how long it should take, and a worked example you can copy.

If your scrum board forces horizontal scrolling or hides columns once you have too many, it is working against you. Here is what a board should do with many columns instead.