RICE scoring

What RICE scoring means

RICE scoring is a concept used in software delivery planning to describe a condition, relationship, estimate, or decision about engineering work. It is most useful when the team names its unit, time window, owner, and decision boundary. The term is clearer when the team defines what enters the measure or decision, what counts as completion, and which planning period is in scope. That discipline prevents a familiar phrase from becoming a different metric in every meeting.

A concrete example

For example, a delivery group can use the concept to expose a hidden queue and then test whether a smaller batch or clearer owner changes the outcome. The record should include the starting condition, the intended result, and the tradeoff that makes the choice possible. When the outcome differs from the plan, the team can inspect the assumption instead of assigning a simplistic explanation to the people doing the work.

Limits and interpretation

Do not use the concept to hide a priority decision. Make the business consequence, technical risk, and opportunity cost explicit. Use this concept as an input to a decision or learning loop, not as a detached score. Keep the relevant work population visible, and revisit the interpretation when the system changes. A useful planning artifact explains what someone should do next and what evidence would change that action.

How Weave fits

Weave can help teams inspect delivery evidence related to rice scoring, including completed work, waiting, review, and rework patterns when those records are connected. That context can inform a planning discussion, but Weave does not make the decision, infer missing organizational context, or guarantee a date, capacity level, or outcome.