Iteration Planning -

“What about the refactor?” Leo asked.

Leo nodded. That was a real problem. But so was the memory leak in the reporting engine. And the new compliance field. And the thing no one wanted to talk about: the gnarly refactor they’d been postponing for four sprints. iteration planning

At the next planning, Mia brought three stories. Not because she had to, but because she saw what happened when they stopped pretending to predict the unpredictable. “What about the refactor

Silence. The kind that gets filled with someone saying, “Let’s see if we have room.” But so was the memory leak in the reporting engine

For the first time in months, iteration planning ended early. People didn’t bolt for the door. They lingered, talked about the refactor’s approach, drew diagrams on the whiteboard.

They started with payment retry. Five points. Then compliance. Three points. Then reporting. Eight points—big, but doable.

Two weeks later, they finished all three stories. The refactor made the next sprint’s work cleaner. Payment retry dropped failed payments by 40%. Compliance passed audit without a fight.