# No Bullshit Agile

> No Bullshit Agile is an English-language knowledge portal by Thomas Esders about agile work — no buzzwords, no framework dogma, no agile theater. At its core stands the Work–Feedback Loop: agile work is the ability to connect work and feedback quickly and reliably. Everything else is overhead. The website includes articles on agile practices, the Work–Feedback Loop conceptual model, and critical perspectives on frameworks, AI in development, and team culture. Language: English. Audience: developers, team leads, managers, and anyone who wants to work agile instead of just talking about it.

## Core Position and Conceptual Model

- [My Position](https://no-bullshit-agile.com/my-position.html): How work systems actually learn — through real work and fast feedback. Everything else is overhead.
- [Work–Feedback Loop (Full Conceptual Model)](https://no-bullshit-agile.com/wfl/): The complete thinking and diagnostic model — Diagnosis Matrix, Feedback Response Time, capital coupling, nested loops, four system states (Learning, Actionism, Frustration, Stagnation).
- [The Work–Feedback Loop (Overview)](https://no-bullshit-agile.com/the-work-feedback-loop.html): The central conceptual model at a glance.
- [The Work–Feedback Loop (Short Version)](https://no-bullshit-agile.com/the-work-feedback-loop-2.html): If feedback doesn't change work, it's not feedback — it's a coupling problem.
- [Context and Origin of the Work–Feedback Loop](https://no-bullshit-agile.com/context-the-work-feedback-loop.html): How do you explain agile work without the burnt term "agile"?
- [Diagnosis Matrix: Why Work Systems Don't Learn](https://no-bullshit-agile.com/diagnosis-matrix-why-work-systems-dont-learn.html): Four quadrants of learning ability — Learning, Actionism, Frustration, Stagnation.
- [Feedback Response Time](https://no-bullshit-agile.com/feedback-response-time.html): FRT measures how long it takes for feedback to change the next piece of work.
- [The Nested Loop](https://no-bullshit-agile.com/the-nested-loop.html): Agility at scale is managing nested learning loops with different speeds.
- [Flight Levels and Nested Work–Feedback Loops](https://no-bullshit-agile.com/flight-levels-nested-work-feedback-loops.html): Flight Levels describe where decisions are made — nested loops describe whether those levels are capable of learning.

## Forget "Agile" as Theory — Craft Matters

- [Forget "Agile" Theory: The Only Cycle That Really Matters](https://no-bullshit-agile.com/agile-working-feedback-loop-skills-over-frameworks.html): Agility is measured by the speed of the cycle Work → Feedback → Adjustment.
- [The "Agile" Label Is Burnt](https://no-bullshit-agile.com/agile-label-burnt-agile-work-craft.html): Anyone wanting to "introduce agility" in 2026 only creates defensive reactions — agile work is craft.
- [Work & Feedback: Skills Not Frameworks](https://no-bullshit-agile.com/iteration-feedback-skills-not-frameworks.html): "We can only release every three months" is the decision not to invest in the craft.
- [Your Team Isn't Slow — Your Feedback Comes Too Late](https://no-bullshit-agile.com/feedback-comes-too-late.html): Feedback belongs in the process, not at the end.
- [Just Because Systems Get Faster Doesn't Mean They Get More Productive](https://no-bullshit-agile.com/just-because-systems-get-faster-doesnt-mean-they-get-more-productive.html): More output through AI doesn't mean more value.

## Scrum, Kanban and Frameworks — Critical Perspectives

- [Scrum vs. Kanban: Why I Recommend Kanban](https://no-bullshit-agile.com/scrum-vs-kanban-why-i-recommend-kanban.html): Scrum focuses on "team collaboration", Kanban focuses on "work" — two fundamentally different approaches.
- [Story Points Are Nonsense?](https://no-bullshit-agile.com/story-points-nonsense-agile-estimation.html): If story points are just code for time, it's agile theater.
- [The Agile Iceberg](https://no-bullshit-agile.com/the-agile-iceberg.html): Scrum rituals are just the tip — beneath the surface lie trust, mindset, and psychological safety.

## For Developers

- [The Agile Survival Kit for Developers](https://no-bullshit-agile.com/agile-for-developers.html): Agile has become a micromanagement tool in many organizations.
- [Daily Scrum for Developers](https://no-bullshit-agile.com/daily-scrum-for-developers.html): Walk the Board puts work at the center instead of the person.
- [Why Good Developers Hate Ticket Shuffling](https://no-bullshit-agile.com/why-good-developers-hate-ticket-shuffling.html): Good devs want to understand why something is being built.
- [Backlog Refinement Technique](https://no-bullshit-agile.com/backlog-refinement-technique.html): Refinement is more important than planning.
- [Definition of Done Practical Guide](https://no-bullshit-agile.com/definition-of-done-practical-guide.html): The DoD is your most important tool against technical debt.
- [Technical Debt in the Agile Process](https://no-bullshit-agile.com/technical-debt-agile.html): Technical debt is like loans with interest.

## AI and Agile Work

- [AI Reduces My Mental Load. That's All. And That's Enough.](https://no-bullshit-agile.com/ai-realistic-usecases-agile.html): AI is a tool like Excel — supports, but replaces neither method nor collaboration.
- [AI Costs and Waste](https://no-bullshit-agile.com/ai-costs-waste-flow.html): Once AI costs money, usage patterns become visible — like meetings.
- [The Hidden Cost of AI Is the Work–Feedback Loop](https://no-bullshit-agile.com/ai-work-feedback-loop-cost.html): The more ambitious the use case, the more scaffolding required.
- [Won't Touch It. It's Made with AI.](https://no-bullshit-agile.com/wont-touch-it-its-made-with-ai.html): Critical perspective on blind AI adoption in development.

## Tools

- [Cylenivo: A Tool, Not a Cockpit](https://no-bullshit-agile.com/cylenivo-a-tool-not-a-cockpit.html): An insight tool for the team, not a surveillance tool for management.

## About the Author

Thomas Esders is a team lead of an agile development team. He has worked with agile methods for over a decade — Kanban focus, no certification hype. no-bullshit-agile.com is the English edition of his knowledge portal: a place for honest, practical exchange about agile work. He is active on Mastodon as @nobsagile@mastodon.social.