Scrum and Kanban, one honest chart
BurnUp puts every piece of work on one typed ladder, from epic down to subtask. Run it as Scrum sprints or a continuous Kanban board, see added scope on the burnup instead of losing it, and get a daily progress digest in Discord.
Free plan: 1 project and up to 5 members.
How it works
Five steps, the same path every project takes in BurnUp.
Create the project as Scrum or Kanban. BurnUp seeds statuses, item types and sensible defaults for that way of working.
Add epics, features, stories, tasks and subtasks. Each gets a short key like BRN-142 that stays stable.
Rank the backlog, pull work into a sprint, then move cards across the board or edit inline in the list.
Completed work and total scope are two separate lines, so scope added mid-sprint is visible, not hidden.
A daily digest posts progress, blocked and overdue work to your team’s Discord channel.
Typed hierarchy
Work items have types, and types have rules. A subtask can’t sit under an epic by accident, and progress rolls up from children to parents.
Bug and Spike sit alongside the ladder for defects and research.
Templates
You pick the method when you create a project, and it stays fixed. Each template shows only the tabs, fields and reports that fit how that team works.
Sprints, story points and a burnup that tracks scope.
A continuous board with no sprint ceremony.
Both get Board, List and Summary views, work logs, comments and the two-column item drawer.
Views and sprints
Fewer views, done properly. Board and List cover daily work; Backlog and Summary cover planning and status.
A column per status with your own names, colours and WIP limits. Drag cards; filter by assignee, type, label, priority or text.
Configurable columns, grouping with sums, sorting and inline edits. Expand a parent to see its children in place.
Rank-ordered work with sprint containers above it. Drag items into a sprint and see committed points against recent velocity.
Status, priority, item types, workload and recent activity for the whole project on one page.
Plan
Name the sprint, set a goal and dates, pull ranked work in.
Start
The committed scope becomes a baseline that can’t be edited later.
Track
Re-estimates count as scope change, and every change is logged.
Close
See completed, carried, added and removed work. Unfinished items carry over.
Reporting
Burndown charts hide added work inside one falling line. A burnup keeps completed work and total scope apart, so you can see whether the team slowed down or the target moved.
Sprint burnup, 10 working days
Unit: points
Illustrative chart with sample data, not real customer numbers.
| Day | Total scope | Completed |
|---|---|---|
| 1 | 40 | 0 |
| 2 | 40 | 4 |
| 3 | 40 | 9 |
| 4 | 48 | 13 |
| 5 | 48 | 18 |
| 6 | 48 | 24 |
| 7 | 53 | 28 |
| 8 | 53 | 34 |
| 9 | 53 | 40 |
| 10 | 53 | 45 |
Scope grew twice this sprint. On a burndown, that looks like a slow week.
Scrum projects also get burndown, velocity across the last sprints, and status and workload breakdowns. Kanban projects get a flow report.
Daily digest
Connect a Discord webhook in project settings. Every day at the hour you choose, BurnUp posts a short summary with a link back to the dashboard.
If Discord rejects the webhook three times in a row, BurnUp pauses the digest and tells you in settings.
Day to day
Type BRN-142 or part of a title to open any item.
Everything assigned to you, grouped by overdue, today, this week and later.
Several people per item, each as owner, developer, reviewer or QA.
Log time spent and time remaining on any item, with a note.
Mark items as blocks, relates to or duplicates. Blocked cards show a badge.
Markdown comments and a full activity history on every item.
Attach files and add external links to any item.
Acceptance criteria as a checklist on stories.
Pricing
Every workspace starts on Free. Prices are in US dollars.
$0
For a small team trying BurnUp on one project.
$4
per member / month
For teams running several projects.
$12
per member / month
For organisations with several teams.
Custom
For larger organisations with security needs.
Custom terms. A sales contact is coming soon.
Yearly billing is coming soon.
A project management tool for software teams. Work lives in a typed Epic → Feature → Story → Task → Subtask hierarchy, projects run as Scrum or Kanban, progress is reported as a burnup, and a daily digest goes to Discord.
A chart with two lines: work completed and total scope. When work is added to a sprint the scope line rises, so you can tell a slow week from a moving target. Scrum projects get a burndown and velocity chart too.
No. The method is chosen when the project is created and stays fixed, because sprints, points and reports depend on it. You can create another project with the other template.
Add a Discord webhook in the project’s settings and pick the hour. BurnUp posts once a day in the project’s timezone, plus messages when a sprint starts or closes. You can send a test first.
Not yet. Discord is the only digest channel in the first release.
Not yet. Imports are not part of the first release.
One Space, one Team Space, one project and up to five members.
Per member per month, in US dollars, for the whole workspace. Yearly billing is coming soon.
Create a workspace, pick Scrum or Kanban, and add your first epic.