AI sprint planning, from backlog to release.

Run Scrum the way world-class engineering teams do: a groomed backlog, epics, capacity-aware planning, a board wired to your pull requests, honest velocity, retros that lead to action, and releases that write their own notes.

Book a demo Explore Kroolo Work

68%

Sprint 14 · 8 days left

Ship risk scoring to beta

On track

Committed

42 pts

Done

29 pts

Capacity

88%

GITHUB · LIVE

PR #482 merged into main. Risk score API moved to Done. Cycle time 1.8 days.

✦ AI

One blocked story could push 8 points to Sprint 15. Want a re-plan?

To Do2

Add audit export

Platform3A

Fix login timeout

Onboarding2I

In Progress2 / 3

Risk score API

Risk engine#4825J

Card tokenisation

Payments#479Blocked8K

In Review1

Notification settings

Onboarding#4812C

Done2

Onboarding checklist

Onboarding#4703A

SSO error copy

Platform#4681I

The whole cycle

Every ceremony, in one place.

Kroolo Sprints follow the rhythm your team already runs, so nobody needs a new process.

01

Groom

Refine and estimate the backlog

02

Plan

Commit to what fits capacity

03

Build

Work the board, merge PRs

04

Review

Demo and share the sprint report

05

Retro

Agree actions, carry them forward

06

Release

Ship with notes written for you

Backlog and grooming

A backlog your team trusts.

Capture everything, rank it, estimate it, and pull the next sprint from the top.

Drag to rank, with epics, priority and estimates in view

Story points, hours or t-shirt sizes, your choice

Filter by epic, label or owner, and send stories straight to a sprint

Epic: All ▾FilterSearch backlogSprint 15 · 18 pts

⋮⋮As a user I can reset my password by SMSOnboardingHigh5

⋮⋮Tokenise stored cardsPaymentsUrgent8

⋮⋮Score transactions in real timeRisk engineHigh13

⋮⋮Export audit log as CSVPlatformMedium3

⋮⋮Dark mode for the mobile appPlatformLow5

S11S12S13S14S15S16S17S18

Onboarding

10 of 14 stories done

72%

Payments

9 of 22 stories done

45%

Risk engine

8 of 31 stories done

30%

Platform

8 of 9 stories done

88%

Epics and roadmap

Zoom out from stories to the roadmap.

Group stories into epics and see how far each one has come, sprint by sprint.

Epic progress rolls up from its stories automatically

A roadmap across sprints shows what lands when

Re-order epics and watch the plan update

Sprint planning

Commit to what fits, not what hopes.

Set the sprint goal, pull stories from the backlog and see capacity as you plan.

Capacity per person, adjusted for time off

Over-commitment flagged before the sprint starts

Carry-over stories handled in one click

Sprint 15 · Oct 26 – Nov 8

Goal: beta-ready risk scoring

42 of 40 pts

AAnn

9 / 10 pts

CClive

8 / 8 pts

IIan

11 / 8 pts

JJulia

7 / 10 pts

SSuzie

7 / 10 pts

Ian is over capacity by 3 points. Move a story to Suzie?

To Do2

Add audit export

Platform3A

Fix login timeout

Onboarding2I

In Progress2 / 3

Risk score API

Risk engine#4825J

Card tokenisation

Payments#479Blocked8K

In Review1

Notification settings

Onboarding#4812C

Done2

Onboarding checklist

Onboarding#4703A

SSO error copy

Platform#4681I

The sprint board

A board that knows what your code is doing.

Move work across columns, with swimlanes, WIP limits and blockers built in.

Swimlanes by epic, assignee or priority

WIP limits and blocked flags keep flow honest

Pull request status shown on the card itself

Engineering metrics

Velocity you can plan with.

Burndown, velocity, cycle time and scope change from the same data your team already updates.

Burndown and velocity for every sprint

Cycle time and lead time from PR and status events

Scope change and carry-over, so planning gets honest

Velocity

36 pts

Cycle time

1.8 d

Lead time

4.2 d

Scope change

+3 pts

Carry-over

2 stories

Burndown

Velocity by sprint

S9S10S11S12S13S14

GitHubGitLabBitbucket

Activity on KRL-482 · Risk score API

Branch created · feature/risk-score

Linked to KRL-482, moved to In Progress

PR #482 opened

Card moved to In Review

PR #482 merged

Card moved to Done, cycle time 1.8 days

Git integrations

Your repo and your sprint, in sync.

Connect GitHub, GitLab or Bitbucket and let engineering activity update the board for you.

Branches, commits and pull requests link to stories automatically

Status moves with the PR: opened, in review, merged

Cycle time and PR throughput appear in sprint metrics

Releases

Ship with notes already written.

Group merged work into a release, and let Kroolo draft the changelog from the pull requests.

Releases built from merged PRs and finished stories

AI-drafted release notes you edit and publish

A checklist so nothing is forgotten on release day

Release

v2.8.0

Ready to ship

✦ Release notes, drafted by AI. This release adds real-time risk scoring and card tokenisation, plus a refreshed notification settings page and a fix for SSO errors.

#482Risk score APIFeature

#479Card tokenisationFeature

#481Notification settingsImprovement

#468SSO error copyFix

Publish notesRelease checklist 5 of 6

Went well

Pairing on the risk API▲ 6

Fast PR reviews▲ 4

To improve

Late scope changes▲ 7

Flaky tests in CI▲ 5

Actions

Freeze scope after day 3▲ 0

Fix flaky tests▲ 0

✦ AI sprint review: 29 of 42 points done, velocity steady.Create tasks

Reviews and retrospectives

Retros that lead to action.

Collect feedback, vote, and turn the actions into tasks that carry into the next sprint.

Went well, to improve and action columns, with voting

Actions become tasks with owners and due dates

An AI sprint review summarises what shipped

Ask AI

Your scrum master, always on.

Ask about scope, blockers and risk, and let AI write the standup and the sprint review.

“Will we finish the sprint?” answered from live data

Standup and review summaries written for you

Suggested re-plans when work is at risk

Will we finish Sprint 14?

Probably, with one risk. 29 of 42 points are done and the burndown is on pace. Card tokenisation (8 pts) is blocked on a vendor key and would slip to Sprint 15.

Draft standup summaryRe-plan sprint

Automate the ceremony

Let the sprint run itself.

Rules handle the repetitive parts of every sprint.

RULEOn

Start the next sprint

When a sprint closes, create and open the next one.

RULEOn

Carry over unfinished work

Move incomplete stories to the next sprint with a note.

RULEOn

Move on PR events

Opened moves to In Review, merged moves to Done.

RULEOn

Notify on blockers

Alert the channel when a story is flagged blocked.

Why teams switch

One home for the sprint, not four tools.

Separate toolsKroolo Sprints

Backlog and boardA trackerBacklog, epics and board

Code activityCopy links by handGitHub, GitLab, Bitbucket

MetricsA spreadsheetBuilt-in velocity and burndown

RetrosA whiteboard toolRetro board with actions

Release notesWritten by handDrafted from PRs

FAQs on Kroolo Sprints

Do Sprints support Scrum and Kanban?

Yes. Run time-boxed sprints with a backlog, or use the board continuously with WIP limits.

Which Git providers connect?

GitHub, GitLab and Bitbucket. Branches, commits and pull requests link to stories and update their status.

Can I estimate in hours instead of points?

Yes. Teams can estimate in story points, hours or t-shirt sizes.

How do epics work?

Group stories into epics and see progress roll up across sprints on the roadmap.

Can AI write release notes?

Yes. Kroolo drafts release notes from merged pull requests and finished stories, and you edit before publishing.

Run your next sprint in Kroolo.

Start free, or see it on your own projects in a demo.

Book a demo Explore Kroolo Work

Explore

More Kroolo Work features

Kroolo Work overview