All bites
The whole library, newest first. Filter by what you are here for, or pick a topic if you already know.
8667 bites
Page 429
Information Radiator: Your Team's Public Billboard
An information radiator is a large, public display that broadcasts key project info to anyone walking by. It's used for build statuses or task boards to keep the team aligned without meetings. The footgun is cluttering it until it becomes ignorable noise.
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.
Cost of Delay: Quantifying the Price of Waiting
Cost of Delay puts a price tag on waiting, quantifying the value lost for every week a feature isn't shipped. It helps prioritize work by its economic impact, not just effort.
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.
Relative Sizing: Estimate Effort, Not Hours
Relative sizing compares work items to each other instead of assigning absolute hours. A team agrees on a baseline task and estimates others as 'larger' or 'smaller' relative to it, often using story points. The footgun is mapping points back to hours.
Personas: Build for a Specific 'Who', Not a Vague 'Everyone'
Personas give your team a shared user understanding by creating a fictional, yet realistic, character profile. They guide feature prioritization and design decisions by focusing on a specific "who."
Job Stories: Focus on Motivation, Not Persona
A Job Story shifts focus from *who* is doing something to *why*. It frames work around a situation, a motivation, and an outcome. Use it when a user's context is more important than their persona. The footgun is simply rephrasing a user story.
What is a DEEP Product Backlog?
A DEEP backlog prevents the 'quicksand' of endless refinement with no progress. It helps teams align on customer value and create reliable plans. The footgun is that without a structured approach, backlogs become chaotic, eroding trust in agile forecasts.
Agile Themes: Connecting Work to Strategy
An agile theme is a strategic focus that groups related epics to achieve a larger business goal. Use themes to show stakeholders how specific features contribute to quarterly objectives like 'Improve Mobile Performance.'
INVEST: The Checklist for High-Quality User Stories
INVEST is a checklist for quality user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable. Use it in backlog grooming to ensure work is clear and sprint-ready.
Epic: The Agile Placeholder for Big Ideas
An Epic is a large user story that's too big for a single sprint, acting as a placeholder for a major feature. Use it to group related stories for features like 'user profile management.'
Mob Programming: The Whole Team on One Computer
Mob programming is like pair programming for the whole team: everyone works on one task, on one computer, at the same time. It's used for complex problems or onboarding. The footgun is letting it become a passive meeting instead of an active collaboration.
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.
Pair Programming: Two Heads, One Keyboard
Think of pair programming as a continuous code review. One developer (the Driver) writes code while the other (the Navigator) reviews it in real-time. This is often used for complex tasks or onboarding. The footgun is letting one person dominate the keyboard.
Collective Code Ownership: The Team Owns the Code
Collective code ownership treats the entire codebase as team property; anyone can change anything. This prevents bottlenecks in agile teams, especially during refactoring.
T-Shaped Skills: Deep Expertise, Broad Collaboration
T-shaped skills describe a professional with deep expertise in one area (the T's vertical bar) and the ability to collaborate across others (the horizontal bar). This is vital in agile teams where cross-functional work is constant.
Burndown Chart: A Project's Fuel Gauge
A burndown chart is a project's fuel gauge, showing work left versus time. Scrum teams use it to track sprint progress and predict completion. The footgun is treating it as a performance report instead of a conversation starter about blockers.
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.
Technical Debt: The Hidden Cost of Shipping Fast
Technical debt is like a loan on your codebase: you ship faster now by taking a shortcut, but pay 'interest' later as slower development. It's often a choice to meet a deadline. The footgun is thinking all debt is bad; strategic debt is fine if.