Introduction
Most "Agile arguments" are not really about right versus wrong. They are about trade-offs — which constraint matters most in this context, what risk is acceptable, what habit needs to break first. The same debate that is foolish in one team is essential in another, and the answer that worked at a small startup may be exactly wrong inside a 5,000-person enterprise.
The Great Agile Debates are the long-running tensions that recur across the practice — estimation, cadence, planning, team structure, quality, leadership. Each side optimizes for something real, and each side breaks down at the limits of what it optimizes for. The point of this hub is not to declare winners. It is to make the trade-offs visible enough that teams can choose deliberately rather than by inheritance.
Topics
Story Points vs. NoEstimates
Relative sizing for shared understanding, or throughput-based forecasting that skips estimation entirely.
Read →TDD vs. Test-Last Development
Tests as design pressure written first, or tests as verification written after the code feels right.
Read →Scrum vs. Kanban
Time-boxed cadence with sprint goals, or continuous flow with WIP limits. Different bets about what produces focus.
Read →Velocity vs. Flow Metrics
Story points per sprint as a planning input, or cycle time and throughput as a system health signal.
Read →Definition of Ready vs. Continuous Refinement
A gate that protects sprint focus, or an ongoing conversation that risks letting half-formed work in.
Read →Sprints vs. Continuous Delivery
Heartbeat cadence for inspection and adaptation, or release-on-demand for fast customer feedback.
Read →Three Questions vs. Flow-Based Standups
Round-robin status, or board-driven conversation focused on blockers and aging work.
Read →Proxy PO vs. Real Customer Involvement
A scalable internal stand-in, or the slower, harder discipline of getting actual users into the conversation.
Read →Burndown vs. Cumulative Flow Diagrams
Sprint-scoped completion trajectory, or system-scoped visualization of work moving across stages.
Read →Capacity Planning vs. Pull-Based Scheduling
Forecast how much fits, or let the team pull work as it finishes the last item. Push vs. pull at the planning level.
Read →Component Teams vs. Feature Teams
Teams aligned around a technical layer they own, or teams aligned around customer-facing features end to end.
Read →Backlog Grooming vs. Continuous Refinement
A dedicated meeting that may go stale between sessions, or a steady drip of small refinement conversations.
Read →Sprint Goals vs. Backlog Commitment
Commit to an outcome and let scope flex around it, or commit to a list of items and let the goal emerge from them.
Read →Hardening Sprints vs. Built-In Quality
Dedicated cleanup time before release, or relentless investment in done-meaning-done from sprint one.
Read →Servant Leadership vs. Delivery Accountability
Leaders who clear the way for the team, or leaders who own the outcome. Often a false dichotomy, sometimes a real tension.
Read →Definition of Done: Minimal vs. Expansive
A short, hard-line bar everyone can meet, or a richer definition that captures more of what "really done" means.
Read →Cross-Functional Teams vs. Swarm When Needed
All skills present permanently in the team, or specialist swarming pulled in for the work that needs them.
Read →Swarming vs. Parallel Work
Everyone on one item to finish it, or multiple items in flight at once to reduce idle time.
Read →Timeboxing vs. Flow-Based Limits
Fixed-duration meetings, or meetings that run until the topic is genuinely addressed. Predictability vs. quality of conversation.
Read →Planning Poker vs. Alternative Sizing
Card-based parallel reveal, or quicker techniques like affinity sizing, Roman estimation, or T-shirt sizing.
Read →How to Use This Hub
Each debate is a frame for a real choice the team will face. The wrong move is to pick a side as a matter of identity — "we're a Kanban team," "we don't believe in estimation" — and stop noticing when context changes around it. The right move is to keep the debate alive: what is the team optimizing for now, what is it giving up, and is that still the right trade-off?
Pick the debates that match your friction. Teams arguing about story points should read about flow metrics. Teams running quarterly hardening sprints should read about built-in quality. The point of the disagreement is to surface the underlying assumption so the team can examine it on purpose.
Back to Hubs