Tagged agile
-
Teaching Engineers to Speak in Constraints
Or: Why “We Can’t Do That” and “Sure, No Problem” Are Both Lies
-
What It Looks Like When It’s Working
Or: The Engineer Who Brings You Problems You Didn’t Know You Had
-
The Process That Punishes the Behaviour You’re Building
Or: Why Your Engineers Stopped Taking Initiative — and Scrum Helped
-
Why Your Engineers Are Still Waiting
Or: The Ownership Problem Nobody Admits They Created
-
The Thematic Quarter: Why Your OKRs Are Fighting Each Other
Or: How a Book About Silos Changed How We Set Goals
-
The Autopsy Nobody Wants to Do
Or: A Field Guide to the Execution Post-Mortem
-
The History Lesson Nobody Wanted: Why Your Team Is Living in 1985
Or: How We Forgot What Agile Actually Meant and Built a Cargo Cult Instead
-
The T-Shaped Trap: Why Your Org Says It Wants Versatile Engineers but Punishes Them for It
Or: Stop Hiring Full-Stack Engineers and Start Building Full-Stack Teams
-
Your Engineers Don’t Trust Your Data (And They’re Probably Right)
Or: Why Your Analytics Pipeline Is the Most Expensive Lie in Your Stack
-
Your Senior Engineers Are Trapped in Sprint Tickets — And You Put Them There
Or: Why Giving Someone a Title Without Giving Them Time Is Just Gaslighting with Extra Steps
-
Your Meetings Are Broken (Yes, Even the In-Person Ones)
Or: Why Being in the Same Room Doesn’t Mean You’re in the Same Conversation
-
The Prototype That Became Production
Or: Why “It Was Only Supposed to Take Two Sprints” Is the Most Expensive Sentence in Software
-
Your Engineers Can’t Negotiate — And It’s Your Fault
Or: Why “We Can’t Do That” and “Sure, No Problem” Are Both Career-Limiting Answers
-
Is This Scrum, or Is This Just Meetings?
Or: A Diagnostic for the Disease Nobody Admits They Have
-
Developer Experience Is a Product — You Just Don’t Have a Product Manager for It
Or: You Already Know How to Build Products. You Just Forgot Your Developers Are Users Too.
-
The Solutioneering Trap: Why Your Best Engineers Are Solving the Wrong Problems
Or: How a Perfectly Good Prototype Taught Me We Were Asking the Wrong Question
-
Co-location, Remote First, and the Rollback Every Few Decades
Or: Why the Most Important Architecture Decision Is Your Floor Plan
-
Why Empathy Is a Technical Skill
Or: Your Users Aren’t Edge Cases, and Neither Are Their Feelings
-
Silent Standby: The Invisible Tax on Your Engineering Velocity
Or: Why Your Sprint Is a Two-Week Hiding Spot for Waiting
-
The Tech Time Tightrope: Why Scrum Has No Handle for Technical Health
Or: How to Stop Drowning in Debt When Your Process Only Speaks Features
-
The Phantom Stakeholder: Why You’re Building for Someone Who Doesn’t Exist
Or: How “Because Legal Said So” Became the Most Expensive Sentence in Software Engineering
-
The Pressure Is Coming From Inside the House
Or: Why Your Engineers Are Burning Out and Nobody’s Asking Them to
-
The Design Handoff Is a Lie: Why Your Engineers and Designers Are Playing Telephone
Or: What Pixar’s Brain Trust Can Teach You About Product Development
-
The Design Review That Reviews Nothing
Or: Why Your Engineers Are Asking for Permission When They Should Be Writing Code
-
Your Roadmap Is a Lie You Tell Yourselves Every Quarter
Or: Why Architectural North Stars Matter More Than Your Q3 Technical Roadmap
-
The Slack Channel Graveyard: Why Your “Async Culture” Is Just Loneliness at Scale
Or: Why #architecture-decisions Has Been Dead Since That One “Thanks!” Seven Months Ago
-
The Onboarding Cliff: Why Your New Engineers Are Productive at Month Six (If They’re Still Here)
Or: What Restaurant Kitchens Mastered That Tech Companies Haven’t
-
The Business Model Blindspot: Why Your Engineers Don’t Know How Your Company Makes Money
Or: We Shipped It, But We Can’t Explain Why It Matters
-
The Craftsman’s Dilemma: Why Your Best Engineers Are Your Biggest Overengineering Risk
Or: Why the Engineers Who Care Most About Quality Are Building Solutions Nobody Asked For
-
The COVID Hangover Is Killing Your Engineering Velocity
Or: Why Walking Twenty Metres Beats Two Weeks of Slack Messages
-
The Question That Changes Everything
Or: Why Asking Engineers “How Can We Do This Faster?” Is the Worst Question You Can Ask
-
The AI Coding Trap: Why 95% of Companies Are Measuring the Wrong Thing
Or: Your AI Can Write Code. So What?
-
The Feature Team Fallacy: Why Your “Agile” Teams Are Just Waterfall in Disguise
Or: How We Accidentally Recreated 1990s Software Development with Better Tooling
-
I Don’t Care What You Build (And Neither Should You)
Or: Why Your Design Reviews Are Missing the Point Entirely
-
Centralization Is Contention: The Hidden Tax on Your Engineering Velocity
Or: Why Every Centralized Team Becomes a Bottleneck (And the Math to Prove It)
-
The Regenerate Button: Why Your Snapshot Tests Are Lying to You
Or: The Most Dangerous Command in Your Test Suite
-
Breaking Engineering Silos: The Uncomfortable Truth About Collaboration
Or: Why Your Teams Are Islands and What You’re Actually Going to Have to Do About It
-
“But, But… My Points!”: The Story Point Trap That’s Killing Your Engineering Culture
Or: Why Your Team Might Be Measuring Success While Missing the Point Entirely
-
The Taste Gap: Why Your Engineering Teams Keep Solving the Same Problems Differently
Or: Why Your ADRs Are Unread and Your Guilds Are Dead
-
Watch Me: The Defiance-to-Data Pipeline
Or: Why Your Best Engineering Decisions Start with Spite and End with Spreadsheets
-
Technical Debt: The Elephant in the Scrum Room
Or: Why Your Product Owner Shouldn’t Be the Only One Steering the Ship