How to write and slice work items a team can act on, organized as four ticket smells, their shared root cause (bad slicing), and the techniques that cure them.
Most bad tickets are slicing failures, and they are detectable before you start work, the way a code smell is. This bundle catalogs four ticket smells, the concepts that explain why they hurt, the techniques that cure them, and playbooks you can run in refinement.
The Iceberg is a slice that hid its size. The Twins are a slice on the wrong axis. The Tapper is a slice missing its reason. The Boulder is a slice that was never cut. Each is a slicing failure, and slicing well is a learnable skill (see INVEST and vertical slicing).
A ticket that looks small on the surface but hides most of its work below the waterline, surfacing as surprise complexity mid-sprint.
Two tickets split on paper but so technically intertwined that neither can be built, demoed, or shipped on its own.
A ticket written by one expert in such terse, context-free, solution-dictating terms that whoever picks it up cannot tell what done means and runs in circles.
A ticket too big to finish, which sits on the board for weeks showing no progress because nothing smaller than the whole thing can reach done.
Bill Wake's six-point checklist for a well-formed user story: Independent, Negotiable, Valuable, Estimable, Small, Testable.
Slice a story as a thin increment cutting through every layer (UI, logic, data) to deliver demonstrable value, instead of by technical layer.
Mike Cohn's five patterns for splitting a user story into vertical slices: Spike, Paths, Interfaces, Data, Rules.
Richard Lawrence's flow and nine patterns for splitting stories, built on a meta-pattern of finding the core complexity and slicing one complete path through it.
A team exercise (Cockburn and Kniberg) for practicing breaking a feature into many extremely thin vertical slices, each independently demonstrable.
A timeboxed investigation whose only job is to buy enough knowledge to estimate or split an uncertain story.
Build a tiny end-to-end path linking the real components first, and agree interfaces up front so coupled work can proceed in parallel without hard blockers.
A short pre-development conversation among three perspectives (business, development, testing) to build shared understanding of a story before work starts.
Matt Wynne's 25-minute, four-card refinement technique that surfaces a story's rules, concrete examples, and open questions.
An optional, team-owned agreement that a backlog item is understood enough to start; useful as a guideline, harmful as a rigid stage gate.
The ongoing team activity of adding detail, order, and size to upcoming items so they become small, clear, and deliverable before a sprint.
The systematic tendency to underestimate the time, cost, and risk of one's own future tasks, even when past tasks ran long.
Estimate variability is widest at the start of work and narrows only as unknowns are resolved, not as time passes.
A cognitive bias where someone who knows something cannot imagine not knowing it, so they communicate as if the audience shares their hidden context.
Cycle time, throughput, WIP, and work item age, the lens that makes a stalled ticket visible before it is formally late.
Average cycle time equals average WIP divided by average throughput; for a given throughput, more work in progress means each item takes longer.
The amount of work moved through the process in one increment; smaller batches reduce cycle time, risk, and variability.
A yes/no checklist to run before a ticket reaches the board; a "no" is a prompt to talk, split, or send it back, not a veto.
A step-by-step for cutting a too-big or wrongly-sliced story into thin vertical slices that each deliver value.
The 2003 article that coined the INVEST acronym and the vertical cake-slicing metaphor for user stories.
Mike Cohn's canonical write-up of the five story-splitting patterns, with worked examples.
Richard Lawrence's widely used guide: a meta-pattern, nine patterns, a flowchart, and two tie-breaker rules.
The originator's write-up of the four-card, 25-minute refinement technique.
Chip and Dan Heath on why experts write opaque instructions, including the tapper-and-listener study.
Scrum.org's definition of the four flow metrics and of Work Item Age as the leading indicator.
