Short, useful team meetings have three things in common: a written agenda with a time budget per point, a clear end, and an output that someone acts on. Realistic sprint planning has one more: the team commits to what its recent sprints say it can do, adjusted for who is actually available, not to what it hopes to do.
Most teams do not start with long meetings, they drift there: the standup becomes a status report, problems get solved in the circle while six people wait, and planning turns into a negotiation the optimistic estimate wins. This guide walks through the fixes in four steps, using four free tools on kimisuite.com. None of them needs an account.
Step 1: Write the agenda before you send the invite
The Meeting Agenda Generator has six templates: daily standup, sprint retrospective, all-hands, 1:1, sales discovery call and project kickoff. You enter a title, the length of the slot and the facilitator, and copy or download the result as markdown.
The standup template looks like this:
- Yesterday: wins and blocks (5 min)
- Today: priorities (5 min)
- Blockers and asks (5 min)
- One thing nobody knows (a one-minute round)
The retrospective template runs to 42 minutes: set the stage (5), what went well (10), what did not (10), action items that are concrete, owned and time-bound (15), and a quick energy check from 1 to 5 (2).
One detail worth knowing: the section times are fixed per template. The length you type appears in the header, but the sections are not rescaled. If your retro slot is 30 minutes, shorten them by hand before you send the invite. That edit is the point: you decide in advance what gets less time.
Step 2: Keep the standup to 15 minutes
The Scrum Guide (November 2020 version, scrumguides.org) describes the Daily Scrum as "a 15-minute event for the Developers", held "at the same time and place every working day of the Sprint". Its purpose is to inspect progress toward the Sprint Goal and adapt the plan for the coming work.
The same guide also says the Developers "can select whatever structure and techniques they want". The three classic questions are a habit, not a rule. If "what did you do yesterday?" has turned into a recital, change the question.
The Standup Question Generator helps here. It picks 1 to 10 random questions from one of four banks: icebreaker, retrospective, deep and fun. Open the standup with one icebreaker question once a week, or bring retro questions such as "Where did you lose the most time?" or "What do we need to STOP doing?" to the retrospective.
Step 3: Estimate the stories before planning
Planning goes faster when the stories already have sizes. The Story Point Estimator is a solo version of planning poker. You pick Fibonacci (1, 2, 3, 5, 8, 13, 21, 40, 100) or T-shirt sizes (XS to XXL, plus "?"), type the story, pick a card and set your confidence to low, medium or high. Estimates go into a running list with a point total.
The guidance under each card is the useful part. A 13 shows "Big · break it down before committing", a 21 "Too big · split into smaller stories", and "?" means you need more information before estimating. If you find yourself picking 13 or higher, the story is not ready for the sprint.
Solo estimates are a starting point. The team still discusses them, because one person alone misses what the others know.
Step 4: Forecast the sprint from your own velocity
The Scrum Guide does not mention velocity or story points. It does say that the more the Developers know about "their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts". Velocity, the points a team completed per sprint, is one common way to measure that.
The Sprint Velocity Calculator takes your last three sprints and your capacity for the next one, in percent, and returns:
- The average of the three sprints
- A trend: up if the last sprint was more than 10 percent above the one before, down if it was more than 10 percent below, otherwise stable
- A forecast: the average multiplied by your capacity
- How many sprints it takes to finish 50 points at that forecast
A worked example
A team of five completed 24, 31 and 27 points in its last three sprints. One person is on holiday for the whole next sprint, so capacity is 80 percent.
- Average: (24 + 31 + 27) / 3 = 27.3 points
- Trend: 27 is more than 10 percent below 31, so the calculator shows "Trending down — investigate blockers"
- Forecast: 27.3 x 0.8 = 21.8 points
- Sprints to finish 50 points: 50 / 21.8 = 2.3, rounded up to 3
Now take the estimated stories from step 3: 8, 5, 5, 3 and 2 points, 23 in total. That is more than the forecast of 21.8. The honest plan is 8 + 5 + 5 + 3 = 21 points, with the 2-point story as the first one to pull in if the team finishes early.
The trend compares only the last two sprints, so one rough sprint is enough to trigger "down". Ask in the retrospective what got in the way before you read it as a problem. And never compare velocity between teams: every team's points mean something different.
Where KIMISUITE fits
The tools work on their own. If you want the meetings and the sprint board in one place, two KIMISUITE apps cover the steps above.
Meeting Hub runs video meetings that guests join in the browser with a link. When you schedule a meeting, you can paste the agenda into its description. In the call, the Tools menu has a timer (1, 5, 10, 15, 30 minutes or custom) that everyone sees and that turns red at 0:00. A poll with two or more options helps a retro decide which action to take first. After the meeting, the transcript can be downloaded on every plan, and on Pro and Enterprise an AI summary lists the action items with who and by when, and the decisions.
Task Hub holds the sprint itself. Its Engineering Sprint template creates lists, labels and example cards for a new board. On the Grow plan and above, you can add custom fields such as a number field and set dependencies, so a card can show what it blocks or is blocked by. On the Business plan, AI Task can turn the summary and transcript of a finished Meeting Hub meeting into proposed cards, which you review before they are created. More on that route in Task Hub: from a voice note to a task board.
Both apps live in the same KIMISUITE workspace, which is billed per workspace, not per user. For what that means for a team, see priced per workspace, not per user. Each app comes with a 14-day trial.
FAQ
What if our standup keeps running over 15 minutes?
Move problem-solving out of it. When a topic needs more than a minute, name it, name the two people who need to talk, and let them meet straight after.
Do we have to use the three standup questions?
No. The 2020 Scrum Guide lets the Developers choose the structure, as long as the meeting inspects progress toward the Sprint Goal and adapts the plan. A different question each week keeps the round from becoming a report.
How many sprints do I need to calculate velocity?
The Sprint Velocity Calculator uses the last three. Fewer sprints give a noisy average; very old sprints describe a team that may have changed since.
What capacity should I enter when someone is off for part of the sprint?
Estimate the share of the team's working days that is actually available. In a team of five, one person off for the whole sprint is 80 percent. One person off for three days of a ten-day sprint is 47 of 50 person-days, so about 94 percent.


