Board and sprints
Stories sit in columns by status, each with an id, an epic, and points. The sprint shows points done and the days left.
Story tracking for small product teams.Run the sprint on a board. Ship from a release train.
ByteBoard gives each project a board for the current sprint, a roadmap for later work, and a release train for what ships next. Specs and notes go in the project wiki.
Free for up to 10 users. No plan has a seat minimum.
The screens your team works in during a sprint
Each project has a board for this sprint and a roadmap for what comes after. Releases line up on a release train, and the team writes things down in the wiki.
Roadmap
The roadmap puts later work on a timeline with point progress, so the team can see what comes after this sprint.
Release train
Releases line up by date. Each one lists its version, its stories, and the points done. Ship marks it as shipped.
Burndown and dashboard
The sprint dashboard counts stories, blocked and overdue work, and points done, next to a burndown and workload by person.
Wiki
Each project has a wiki. Specs and meeting notes sit in the same project as the board and the stories they describe.
Keyboard-first
The board, the story page, and the command palette work from the keyboard, so you can get through a sprint without the mouse.
How a story moves from the board to a release
Board and sprints
Each column on the board is a status, and the sprint holds the stories the team took into this cycle. The board also shows the sprint name, points completed against points in the sprint, and days left. Open a story to see its own page, with type, priority, assignee, epic, release, and due date.
Roadmap
The roadmap puts the work planned after this sprint on a timeline, with point progress for each piece. It lives in the same project as the board, so the team can look ahead to the next cycle without switching tools.
Release train
The release train orders releases by date, so the team can see what goes out next and what follows it. Each release has a version, a date, the stories on it, and the points done so far. Ship marks a release as shipped.
Burndown and dashboard
The dashboard covers the current sprint. It counts stories, flags what is blocked, overdue, or unassigned, and puts points done next to a burndown of the work left. Work at risk and workload by person show where the sprint could slip and who is carrying too much.
Wiki
The wiki lives in the same project as the board. That is where the team writes the spec before a sprint and the notes after a release. When someone opens a story and needs the background, it is in the same project instead of a separate docs tool.
Keyboard-first
You can move around the board and work through a story page without touching the mouse. The command palette lets you reach the rest of the project by typing. It suits people who already spend the day in an editor and would rather type than click.
Per-user pricing, about 25% less than Jira
You pay for the people on your team, with no seat minimum and no add-on fees. Team and Business start with a 14-day Business trial that does not need a credit card.
Free
$0
Team
$6$7.50 monthly
Business
$11$14 monthly
Enterprise
Custom
Open a board and start a sprint.
The Free plan covers up to 10 users and 3 projects. If you already have an account, sign in instead.