Do we really put users first in Agile - or do we just ask them to debug our assumptions?

In this episode of The Agile Engineering Deep Dive, Alessandro Guida challenges a common Agile belief: that frequent feedback automatically means meaningful user involvement.

When users are shown isolated features instead of full interaction flows, feedback becomes guesswork. User stories describe intent, but without UX context, interaction design, or storyboards, teams often build correct functionality into the wrong experience.

This episode explores:

• Why user stories alone are often not enough
• How storyboards help validate understanding before code is written
• The role of UX and interaction design in reducing rework and uncertainty
• How to involve users in shaping experiences, not just approving backlog items

Not anti-Agile.
Not anti-user stories.
A challenge to how we use them.

If you care about building the right thing - not just building fast - this episode is for you.

Please subscribe to this Podcast. It is the best way to support it.
Also, if you are interested in the original article for this podcast make sure to subscribe the Agile Engineering newsletter 👉 here.