Sprint planning cut from half a day to 30 minutes

For this team, sprint planning had become a half-day ritual: a room full of senior engineers debating estimates, reconciling capacity against a calendar nobody trusted, and hand-writing acceptance criteria story by story. The cost wasn't just the hours. It was the senior-engineer hours, spent on arithmetic and wordsmithing instead of architecture and review. Adopting Stride's Plan module changed the shape of the meeting rather than just speeding it up. The AI drafts the sprint from the team's real inputs (historical velocity, PTO, meeting load) and the AI Story Writer turns each backlog item into structured stories with acceptance criteria already attached. The team's job shifted from authoring to reviewing and editing, which is both faster and a better use of judgment. The headline result was a 6x reduction in planning time, from roughly half a day to about 30 minutes. That multiple matters less than what it freed up: the reclaimed hours went back into the work the planning meeting was supposed to protect. Just as telling is the 92% acceptance rate on AI-generated stories. A high acceptance rate is the signal that the AI is a genuine starting point rather than a draft that has to be rewritten. The team kept the vast majority of what the Story Writer produced, editing rather than replacing. As the VP of Engineering put it, the AI generates better acceptance criteria than they wrote manually, which is the quieter, more durable win: consistency. Human-written criteria drift in quality across authors and late-afternoon sessions; AI-drafted criteria start from a consistent baseline the team then sharpens. The story is anonymised by agreement, role and sector only, but the mechanism generalises: move the rote half of planning to the AI, and the expensive half of the room gets its time back.