Plan sprints around merged code.
Backlogs, story points, velocity and burndown, connected to GitHub and GitLab. Status follows pull requests, so your sprint chart reflects work that shipped.
| NF-176 Checkout address form | 5 pts | PR #482 merged |
| NF-201 Order tracking map view | 8 pts | PR #489 open |
Backlog grooming
Rank, estimate and split stories. Drag the top of the backlog into the next sprint.
Story points or hours
Estimate the way your team already does. Mix both if you have to.
PR-linked status
Open a PR with NF-201 in the branch and the task moves to review. Merge it and it moves to done.
Burndown and burnup
Daily charts that show scope added mid-sprint as its own line, so creep is visible.
Velocity
Rolling averages from completed sprints help you commit to what the team can really finish.
Retro notes
Capture what went well and what to change, linked to the sprint it came from.
Groom
Estimate and rank the backlog with the product owner.
Commit
Pull stories in until committed points meet team capacity.
Build
Branches and PRs update task status on their own.
Review
Close the sprint. Unfinished work carries over with a note.
The sprint is done when the code is merged, not when someone drags a card.
Sprint Planner reads capacity from the Workload View, so planning starts with who is actually available: leave, part-time hours and other projects are already counted.
Pull request links work both ways. From a task you can see the PR, its review status and checks. From the sprint you can see which stories have no code yet with two days to go.
At the end of each sprint, the AI Daily Brief writes a short sprint summary: what shipped, what carried over and why, with links to every task and PR it mentions.
Tomorrow's paper could be about your team.
- Project Boards and Task List
- Import from Jira, Trello or Excel
- No card needed to start
Bigger team? Connect Team