# Round work durations after the aggregation rule is clear

Illustrative planning brief; no automatic product import.

Synthetic case: Three elapsed durations are 0.6 hours each. The draft rounds each to a whole hour and then adds them.

## Decision

Under the stated sum-raw-then-round policy, retain 1.8 raw hours and show 2 whole hours; disclose that rounding each first would show 3.

## Owned work

- Retain raw durations
  - Owner role: Report owner
  - Acceptance evidence: All three 0.6 hour values remain available.
- State rounding order
  - Owner role: Reviewer
  - Acceptance evidence: The policy sums raw values before rounding once to whole hours.
- Publish both meaning and display
  - Owner role: Lead
  - Acceptance evidence: 1.8 raw hours becomes 2 display hours; per-item rounding would be 3.

## Workflow

1. Choose the aggregation unit and retain raw precision.
2. State where rounding occurs and how a tie would be handled.
3. Keep rounded display distinct from the underlying total.

## Judgment

Rounding does not improve measurement accuracy. This example avoids a tie; a real policy still needs an explicit tie convention and unit.


## Filled review note

Precision note: raw total 1.8 hours; displayed total 2 hours under sum-then-round. A different order yields 3 and is not silently substituted.


## Workflow questions

### Why can the displayed sums differ?

Rounding each 0.6 to 1 before summing gives 3; summing first gives 1.8 and then 2.

### Can I recover raw precision from the rounded display?

No. Keep original event evidence and raw values.

## Product connection

Bring this manual reporting policy and its owned checks into your TeamBoostAI work discussion. Native report/export fields and historical reconstruction depend on your account and implementation; this worksheet does not import or change product records.

Confirm account availability before adopting this manual outline.

## Decision workshop

Synthetic examples only. Manual worksheet; no automatic import or product writes.

### Synthetic reporting records

Item | Raw elapsed hours | Per-item rounded display
--- | --- | ---
A | 0.6 | 1 if rounded first
B | 0.6 | 1 if rounded first
C | 0.6 | 1 if rounded first

### Version changes

Boundary | Draft | Revised
--- | --- | ---
Rounding order | Round each then add | Add raw then round once
Evidence | Only rounded values retained | Raw durations retained with policy

### Draft or earlier version (review its limits)

Draft: three whole hours after rounding each item first.

### Revised example

Precision note: raw total 1.8 hours; displayed total 2 hours under sum-then-round. A different order yields 3 and is not silently substituted.

### Decision situations

- Raw values and the rounding convention are known: Apply the stated order and disclose the display unit.
- Only rounded item displays are available: Do not invent the lost raw total.
- Rounding order is unspecified: Define the convention before comparing totals.

### Method references

- The Kanban Guide, May 2025: https://kanbanguides.org/the-kanban-guide/2025.5/ — Clock and work-item definitions; examples and local rules are our own.