Horizontal Slicing
Work is organized by technical layer (“build the API,” “update the schema”) rather than by independently deliverable behavior. Nothing ships until all the pieces are assembled.
10 minute read
Tag: Work-Decomposition
Monolithic Work Items
Work items go from product request to developer without being broken into smaller pieces. Items are as large as the feature they describe.
5 minute read
Unbounded WIP
The team has no constraint on how many items can be in progress at once. Work accumulates because there is nothing to stop starting and force finishing.
5 minute read
Velocity as a Team Productivity Metric
Story points are used as a management KPI for team output, incentivizing point inflation and maximizing velocity instead of delivering value.
8 minute read
Big-Bang Feature Delivery
Features are designed and built as large monolithic units with no incremental delivery - either the whole feature ships or nothing does.
11 minute read
Undone Work
Work is marked complete before it is truly done. Hidden steps remain after the story is closed, including testing, validation, or deployment that someone else must finish.
6 minute read
Thin-Spread Teams
A small team owns too many products. Everyone context-switches constantly and nobody has enough focus to deliver any single product well.
6 minute read
Missing Product Ownership
The team has no dedicated product owner. Tech leads handle product decisions, coding, and stakeholder management simultaneously.
6 minute read
Push-Based Work Assignment
Work is assigned to individuals by a manager or lead instead of team members pulling the next highest-priority item.
9 minute read
AI Tooling Slows You Down Instead of Speeding You Up
It takes longer to explain the task to the AI, review the output, and fix the mistakes than it would to write the code directly.
4 minute read
AI Is Generating Technical Debt Faster Than the Team Can Absorb It
AI tools produce working code quickly, but the codebase is accumulating duplication, inconsistent patterns, and structural problems faster than the team can address them.
6 minute read
Completed Stories Don't Match What Was Needed
Stories are marked done but rejected at review. The developer built what the ticket described, not what the business needed.
3 minute read
Stakeholders See Working Software Only at Release Time
There is no cadence for incremental demos. Feedback on what was built arrives months after decisions were made.
3 minute read
Sprint Planning Is Dominated by Dependency Negotiation
Teams can’t start work until another team finishes something. Planning sessions map dependencies rather than commit to work.
4 minute read
Everything Started, Nothing Finished
The board shows many items in progress but few reaching done. The team is busy but not delivering.
3 minute read
Some Developers Are Overloaded While Others Wait for Work
Work is distributed unevenly across the team. Some developers are chronically overloaded while others finish early and wait for new assignments.
3 minute read
Work Items Take Days or Weeks to Complete
Stories regularly take more than a week from start to done. Developers go days without integrating.
3 minute read