Cumulative Flow Diagrams: Spotting Workflow Bottlenecks
A Cumulative Flow Diagram is a geological cross-section of your project, showing work moving through states over time. Agile teams use it to spot bottlenecks by seeing where tasks pile up. The footgun is misinterpreting a widening band as a failure.
Start, Stop, Continue: A Simple Action-Oriented Retrospective
This retrospective turns feedback into action by asking what to start, stop, and continue doing. Teams use it after a sprint to improve processes and collaboration. The footgun: the 'Continue' list can become a long praise session, losing focus on improvement.
Impact Mapping: From Business Goals to Code
Impact Mapping is a visual roadmap that connects business goals directly to features, forcing you to answer "Why?" before "What?". Use it to align stakeholders on a new vision or prioritize a backlog. The footgun is starting with features and working backward.
Buy a Feature: Prioritize by Making Customers Spend
Buy a Feature turns prioritization into a game where customers spend a limited budget on their desired features. It's used in product planning to force trade-offs and reveal true value.
The Technical Debt Quadrant
The Technical Debt Quadrant reframes debt not as one problem, but a 2x2 matrix: prudent vs. reckless and deliberate vs. inadvertent. This distinguishes a strategic choice to ship early from a simple mess. The footgun is treating all debt as equally bad.
The Boy Scout Rule: Leave Code Cleaner Than You Found It
The Boy Scout Rule applies a simple principle to code: always leave it a little cleaner than you found it. When fixing a bug, make a small improvement like renaming a variable.
Planning Poker: Avoid Groupthink in Estimates
Planning poker avoids groupthink in effort estimation. Team members reveal estimates simultaneously using cards, preventing the first number spoken from anchoring everyone else. It's used in Agile to size up tasks.
The MoSCoW Method: Prioritizing for Fixed Deadlines
The MoSCoW method protects deadlines by sorting work into four buckets: Must Have, Should Have, Could Have, and Won't Have this time. It's used in agile projects with fixed timelines to ensure critical features ship.
Value Stream Mapping: Find the Waste in Your Process
Value Stream Mapping visualizes your entire process, from request to delivery, to separate value-adding work from wasteful delays. It's used to find bottlenecks in manufacturing or software, like code waiting for review.
Cycle Time vs. Lead Time: Team Speed vs. Customer Wait
Lead Time is the total time a customer waits for a feature, from request to delivery. Cycle Time is the portion of that time your team is actively working. The footgun is optimizing only for Cycle Time, which can hide major customer-facing delays in the.