Every planning poker round in AgileKit now times itself

AgileKit 2.13 puts a clock on the poker board that starts and stops with the round. Here it is in the demo, at the top left. Custom number decks now average too, and a double-click can't wipe your results.

Slide text

AgileKit v2.13.0

Every poker round now times itself.

A clock bound to the round, number decks that average, and a New Round button that waits.

1 2 3 5 8 13 21 34 55 89

The timer shows how long the team has spent on this ticket, and you don't have to start it. Blue is voting, up to the reveal. Green is discussion, until the room moves on. If you hide the timer, the time is still tracked.

Slide text

AgileKit v2.13.0

Time on this ticket, split in two.

Voting

start of the round to the reveal

Discussion

reveal until the room moves on

1 2 3 5 8 13 21 34 55 89

It replaces the manual stopwatch. Only 21 percent of poker rooms ever started that one, and a reset threw its reading away. Now every round keeps a record, Quick Votes included. That covers most rounds, because 78 percent of poker rooms never create an issue.

When you want a limit, flip the shared sand timer. Pick 1, 2, 3 or 5 minutes, or add a minute. At zero it turns amber and counts overtime, but it never reveals the cards or plays a sound. Pauses, empty rooms and long quiet stretches come out of the time.

Custom decks used to be marked as not numeric, so they never averaged. Now a new room with a deck of plain numbers averages like a preset. Votes of 2, 2 and 8 give an average of 4, a median of 2, and 67 percent agreement. A card like 2d now counts as a word, not a number.

New Round appears right where Reveal was. So after a reveal it now holds for 3 seconds, and a stray second click lands on a disabled button instead of wiping the results. Then it's ready.

Slide text

AgileKit v2.13.0

New Round waits 3 seconds after a reveal.

Just revealed

A few seconds later

1 2 3 5 8 13 21 34 55 89

Two failures now explain themselves. With Jira auto-push on, room settings show how the last estimate push went, and why one wasn't pushed. And when Convex was slow, app pages used to hang. Now a signed-in page waits at most 2.5 seconds, and anything else lands here, with Try again.

Access got tighter. Only people in a room can now read its issue list and the issue it's voting on. And after sign-in, you go back only to a page on AgileKit. A link that tries to send you elsewhere lands on the home page.

In retros, a refused sticky edit reopens with what you typed. Spotlighting an unvoted topic is now a detour, so Next picks up where the walk left off. And while writing, you stack only your own stickies.

The release notes don't list any breaking changes. If you host AgileKit yourself, the round clock adds new tables, so deploy the Convex backend with the app. On Vercel the README's build command does it; anywhere else, run npx convex deploy first. One limit is by design: time belongs to the round and the ticket, never to a voter. Every poker round now times itself.

Slide text

AgileKit v2.13.0

No breaking changes. Deploy the backend too.

Self-hosted, outside Vercel

npx convex deploy

before you start the app. New tables hold the round clock.

Time belongs to the round and the ticket, never to a voter.

1 2 3 5 8 13 21 34 55 89