Stopwatch
The stopwatch is the small clock on a section. It counts up while that section is open. It stops when the room moves to the next section. Summary has no stopwatch.
Definitions
The words the board uses when it counts time, checks a review, or scores a bet.
These words describe time, votes, and the notes the team writes.
The stopwatch is the small clock on a section. It counts up while that section is open. It stops when the room moves to the next section. Summary has no stopwatch.
Time spent is the stopwatch turned into whole seconds. It is how long the room kept that section open.
The timer counts down. Anyone in the room can start it at 3, 5, or 8 minutes, or type a custom length from 1 to 60 minutes. Summary has no timer. The icebreaker has no timer.
Time left is how many whole seconds remain before the timer reaches zero. If nobody started a timer, this is empty. If the timer has finished, this is 0.
A dot is one vote on a note. Each person starts with 3 dots. Anyone in the room can change that budget to any whole number from 1 to 10. Lowering the budget removes the extra dots.
Dots left is your budget minus the dots you have already placed. At 0, remove a dot before you can place another.
FormulaDots left = dots each person may spend minus dots you have placed.
Vote count is how many dots sit on one note. It is the number of people who chose that note, counting each person once.
These words describe the checklist, the evidence, and the release call.
A checklist item is one line the team wants to be true before they leave. A required item must be checked. An optional item can stay open.
The bar counts required items that at least one person has checked. Optional items do not move the bar. The bar reads 100 percent when every required item is checked. Two people can check the same line. That still counts as one checked item.
FormulaChecklist bar = required items with at least one check, divided by all required items.
Evidence is the short note on a checklist line. It records what the team showed, a link, or a caveat. It is not a second checklist item.
Feedback is a comment captured in the room. Each comment is one of three kinds. Praise says what worked. Change asks for a fix. Question asks for an answer.
The release decision is the single call the room makes before people leave. Ship means release it. Iterate means change it and look again. Hold means do not release it yet. The notes next to the call say why.
These words describe a bet, the score, and where that score sits on the board. The score helps the team compare. It does not decide for them.
Reach is how many people or accounts feel this bet during the quarter. It is a whole number from 0 to 1,000,000.
Impact is how much the outcome moves for the people in Reach. The choices are fixed. 0.25 is minimal. 0.5 is low. 1 is medium. 2 is high. 3 is massive.
Confidence is how sure the team is that the outcome will happen. It is a fraction from 0 to 1. For example, 0.8 means the team is fairly sure. Below 0.6, the board says the confidence is thin.
Effort is team time, counted in person months. The smallest value is 0.25. The largest is 240. A floor of 0.25 stops a tiny effort from making the score look huge. If effort is 0, the RICE score is 0.
RICE compares bets by how many people they reach, how much the outcome moves, how sure you are, and how much time they take. A higher score is a stronger candidate. It is still a comparison, not a command.
FormulaRICE score = (Reach times Impact times Confidence) divided by Effort.
ICE uses three whole numbers, each from 1 to 10. Impact is how much the outcome matters. Confidence is how sure you are. Ease is how little friction there is to ship. 10 on ease means easy. 1 means hard.
ICE is a fast score for comparing bets. Each input is 1 to 10, so the score runs from 1 to 1,000. A higher score is easier to believe and easier to ship.
FormulaICE score = Impact times Confidence times Ease.
Business value is how much the outcome is worth to the business, from 1 to 10. 10 is the outcome you most want. 1 is a small gain.
Complexity has three parts, each a whole number from 1 to 5. Technical complexity is how hard the engineering is. Dependency load is how much you must wait on other teams. Uncertainty is how much you still do not know. 1 is light. 5 is heavy.
The complexity index is the average of the three complexity parts. It is one number from 1 to 5 so a bet can be compared with its score.
FormulaComplexity index = (technical complexity + dependency load + uncertainty) divided by 3, rounded to two decimal places.
This score asks whether the business value is large compared with how hard the bet is. A high value with low complexity scores higher. If the complexity index is 0, the score is 0.
FormulaScore = business value divided by the complexity index.
The median is the middle score on this board. Half of the bets score at least this high. A bet is called strong when its score is greater than or equal to the median. With an even number of bets, the median is the average of the two middle scores.
High complexity starts at 3.5 on the complexity index. A bet at or above 3.5 is called heavy. The chart draws a line at 3.5 so the team can see that cut.
Each bet lands in one of four groups, using its score and its complexity. Do first means a strong score and not heavy. Big bet means a strong score and heavy, so start with a thinner release. Fill-in means a modest score and not heavy. Keep it only if it clears the path for something larger. Reconsider means a modest score and heavy. Sharpen the outcome before it comes back.
Rank is the order of bets by score, from highest to lowest. Rank 1 is the highest score. If two scores are equal, the board sorts those titles from A to Z.