Item size
Also known as Small and large changes
Definition
Item size describes the work unit used in flow analysis. It may use changed behavior, files, stories, or another local convention, but comparisons require a consistent definition and awareness of complexity.
Item size in practice
Item size describes the work unit used in flow analysis. It may use changed behavior, files, stories, or another local convention, but comparisons require a consistent definition and awareness of complexity.
A concrete example
An illustrative team reports ten completed items in one month, including eight small fixes and two migrations. The count hides the scope difference, so the team segments the work before interpreting throughput or cycle time.
How to use the signal
Compare this measure with cycle time, throughput, work in progress, and queue time. Define the start and finish events, inspect distributions instead of relying on one average, and record the policy behind any comparison. A useful measure should lead to a specific question about flow rather than a score for an individual.
Limitations
No sizing method perfectly captures value or effort. Lines and points can encourage gaming or false precision. Use size to explain flow variation, not to rank individual engineers.
How this relates to Weave
Weave's engineering intelligence can help teams inspect delivery activity and timing around item size. Use those signals to find patterns and test workflow improvements, while keeping the team's work system as the source of truth for product, operational, and dependency context.
Explore Engineering intelligence