Grand Canyon Education: Doubling Team Velocity in Six Months

When I was brought in to manage backend and platform engineering at Grand Canyon Education, the team said it was Agile. In practice it was running Agile theater on top of a command-and-control culture. In six months we doubled its velocity without adding headcount. Here is how.

The challenge

The numbers told the story. The team delivered about 13 story points a sprint, well below its capacity, and missed 40% of its sprint commitments. Deployments happened every three or four weeks, which made every release something to fear. Morale was low from the constant sense of falling short.

Underneath that, the causes were all process. Stories were poorly sized and kept changing. There were no limits on work in progress, so everyone context-switched constantly. Deployment was manual and risky. Standups were status reports, not blocker removal. Retrospectives produced no action. There were no one-on-ones and no career development. The team had talent; the system around it was broken.

What I did

Fixed story sizing. I introduced reference stories and planning poker so the team shared a real understanding of effort. Estimates became predictable and people regained confidence in their commitments.

Limited work in progress. I enforced strict WIP limits so work had to be finished before new work began. Tasks moved across the board faster with far less context-switching.

Built CI/CD. I replaced the manual release process with automated pipelines, turning deployment from a rare, frightening event into a routine one that happened multiple times a week.

Rebuilt the ceremonies. Standups refocused on identifying and removing blockers, with leadership clearing obstacles daily. Retrospective actions became sprint commitments with owners and follow-through, so improvement was real rather than performative.

Invested in people. I started regular one-on-ones and used the Tours of Duty framework from Reid Hoffman's "The Alliance" to frame work as missions with clear goals and genuine growth.

The results

• Velocity went from 13 to 26 story points a sprint, a 100% increase, growing 10 to 20% per sprint.
• Sprint commitment success rose from 40% to 90%.
• Deployments moved from every three or four weeks to several per week.
• Morale improved and the team added two developers, funded by its own performance gains.

What it taught me

Most velocity problems are not people problems. They are process problems. This team already had the talent; it needed better process and someone to remove the obstacles in its way. The harder lesson was about sustainability: an isolated team transformation is fragile. When organizational priorities later shifted back toward micromanagement, that pressure worked against the culture we had built, which is why real transformation needs alignment above the team, not just inside it.