Backlog, sprints, code review and releases for a small team. Simple enough to run without a scrum master, with dependencies and milestones when you need them.
The board
Five statuses for a two-week sprint. The cards are examples; your issues drop straight in.
What's inside
One sprint, start to finish
Four groups of starter tasks, linked with dependencies so the release waits on QA.
PlanDay 1
- Sprint planning
- Pull issues from Backlog
- Estimate and assign
- Set the sprint goal
BuildDays 2-8
- Feature work
- Bug fixes
- Code review on every change
- Update docs
TestDays 8-9
- QA pass
- Fix release blockers
- Beta to testers
- ◆ Milestone: Release candidate
ShipDay 10
- Release
- Release notes
- Sprint review
- ◆ Milestone: Shipped
Starter rules
Rules run when a task is added or changes, or when a due date gets close. Rules that assign a person start out assigning you; pick the right teammate in Automations.
Questions
Does Taskift integrate with GitHub?
Not natively yet. You can use the API with a scoped token to read and move tasks from scripts or CI.
Can a coding agent work tasks?
Yes. Give the agent a seat and its own token; it reads tasks, moves cards and comments, and you review its work.
Can I see the sprint on a timeline?
Yes. The Gantt timeline shows every task, its dependencies and the release milestones.
Can I save my own version?
Yes. Save any project as a template and reuse it every sprint.