DEV Community

Cover image for "Agile" isn't about delivering every sprint
Jonathan Hall
Jonathan Hall

Posted on • Originally published at jhall.io on

"Agile" isn't about delivering every sprint

I was recently having a conversation with someone who was asking if their team could be considered “agile.” As evidence to support the claim, they said “The team delivers working software every sprint.”

Of course, delivering frequently is usually a good thing. But is it enough to claim “agility?”

Of course not!

Agility is the ability to move quickly, or to adapt to change.

To truly claim agility, the team must constantly receive and incorporate feedback into their work and planning. Frequently delivering software is not sufficient. Although, it probably is necessary, to allow for feedback.

To make the point as blunt as I can:

  • Frequently delivering software that nobody uses isn’t agile.
  • Frequently delivering software that doesn’t work isn’t agile.
  • Frequently delivering software, but not considering feedback on how to improve, isn’t agile.

If you enjoyed this message, subscribe to The Daily Commit to get future messages to your inbox.

Image of Datadog

The Essential Toolkit for Front-end Developers

Take a user-centric approach to front-end monitoring that evolves alongside increasingly complex frameworks and single-page applications.

Get The Kit

Top comments (0)

Billboard image

The Next Generation Developer Platform

Coherence is the first Platform-as-a-Service you can control. Unlike "black-box" platforms that are opinionated about the infra you can deploy, Coherence is powered by CNC, the open-source IaC framework, which offers limitless customization.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay