Archive
2026
- What Sprint Planning Looks Like When Throughput Has Doubled
- Velocity Is a Planning Tool, Not a Performance Metric
- User Stories Are a Conversation Starter, Not a Requirements Document
- The Sprint Review Is Not a Demo
- The Sprint Goal Is the Most Skipped Part of Scrum
- The Scrum Master's Real Job Is Organizational, Not Ceremonial
- The Product Owner Role Is Harder Than Most Organizations Treat It
- The Definition of Done Needs to Account for How the Code Was Built
- The Decisions That Remain Irreducibly Human
- The Daily Standup Has Three Failure Modes and Teams Hit All of Them
- The #NoEstimates Argument Deserves to Be Taken Seriously
- Testing AI-Generated Code Requires a Different Default Posture
- Technical Debt in the AI Era Is Accumulating at a Different Rate
- Technical Debt Belongs in the Backlog, Not in Side Conversations
- Splitting User Stories Is a Skill Most Teams Develop Too Late
- Retrospectives That Change Nothing Are Worse Than No Retrospective
- Requirements Writing Is Now a Core Engineering Skill
- Remote Agile Teams Fail at the Informal Layer, Not the Ceremony Layer
- Prompt Engineering Is a Software Discipline, Not a Workaround
- Planning Poker Works, But Not for the Reason Most Teams Think
- Most Teams Adopting Scaling Frameworks Do Not Need Them
- Kanban vs. Scrum Is Usually the Wrong Question
- How AI Has Shifted the Leverage Points in Engineering Teams
- Fixed-Price Contracts and Agile Development Are Structurally Incompatible
- Definition of Ready Is the Guardrail That Sprint Planning Needs
- Continuous Delivery Is Not a DevOps Practice — It Is an Agile Foundation
- Backlog Refinement Is the Most Underrated Practice in Scrum
- Architectural Coherence Is the Discipline That AI Cannot Substitute
- AI Pair Programming Has Not Eliminated Code Review — It Has Made It Harder
- Agile Is Not Dead — the Cargo Cult Version Deserved to Fail