Team Workflow

Anti-patterns in how teams assign, coordinate, and manage the flow of work.

These anti-patterns affect how work moves through the team. They create bottlenecks, hide problems, and prevent the steady flow of small changes that continuous delivery requires.


Pull Request Review Bottlenecks

Pull requests sit for days waiting for review. Reviews happen in large batches. Authors have moved on by the time feedback arrives.

Work Items Too Large

Work items regularly take more than a week. Developers work on a single item for days without integrating.

No Vertical Slicing

Work is organized by technical layer - “build the API,” “build the UI” - rather than by user-visible behavior. Nothing is deployable until all layers are done.

Too Much Work in Progress

Every developer is on a different story. Eight items in progress, zero done. Nothing gets the focused attention needed to finish.

Push-Based Work Assignment

Work is assigned to individuals by a manager or lead instead of team members pulling the next highest-priority item.

Last modified February 13, 2026: Add team anti-patterns (5b51a94)