Two weeks at a time, planned before Monday.
Cycles start on their own, fill up to your team’s capacity by priority and roll unfinished work into the next one. The burn-up tells you on Tuesday what used to surprise you on Friday.
Active cycle
- In progress
22 - In review
11 - Todo
33 - Done
22
Open Issues in the sidebar, finish one, come back: today’s point on the burn-up moves.
Plan by capacity, not by meeting.
Keel pulls in work by priority until the cycle is full, then stops. Change the team’s capacity or skip the carry-over and watch the plan redraw.
Cycle 25 · Nov 16 – Nov 27
- Empty states for the billing portalcarried1 pt
- Move image resizing to the edgecarried3 pt
- Dark mode tokens for chartscarried3 pt
- !TypeError on checkout total2 pt
- Webhook for status changes5 pt
- Remember the last board filter2 pt
- Export a cycle report as PDF5 pt
- Invoice PDF misses the VAT number2 pt
Waiting for Cycle 26
- Bulk edit labels3 pt
- Prefetch the next page of results3 pt
- Pin a project to the sidebar2 pt
- Share a view with a link5 pt
Start, close and roll over, on time, every time.
Set the rhythm once. Keel opens each cycle at 09:00 on your start day and closes it at 18:00 on the last, moving what is left.
Rollover
Friday, 18:00. Nobody copies tickets.
Cycle 244 days left
- Coupon field fix
- Saved cards
- Offline comment queue
- Search flicker
- Billing empty states
Cycle 25
- Status webhook
- Remember board filter
Unfinished: In progress, In review, Todo
Rhythm
Opens 09:00, closes 18:00 the working day before the next.
- C25
- C26
- C27
- C28
- C25 Nov 16 – Nov 27
- C26 Nov 30 – Dec 11
- C27 Dec 14 – Dec 25
- C28 Dec 28 – Jan 8
Know how the last two weeks went, in one screen.
Cycle time, scope creep and throughput, measured from work your team already does. No dashboard project, no spreadsheet on Friday.
Nov 2 – Nov 13
3 issues rolled into Cycle 25. Scope grew 6 points after day one.
- scope
3636 points- completed
3333 points- added mid-cycle
+6+6 points- cycle time
2.42.4 days, median- carried over
33 issues
About cycles.
Plan Cycle 1 before lunch.
Turn cycles on for one team, set the length and the start day. Keel fills the first one from your backlog.