DEV Community

Steve Hallman
Steve Hallman

Posted on • Originally published at theagilecouch.com on

“Feature” is Ambiguous.

Great joke of course.

We’ve used the word feature to the point that it’s lost specific meaning. A feature could mean, “this field will retain your data for the next time you log in”. A feature could also mean “big green button”. A feature could also be almost any object or landmark. That big rock that looks like a bird’s head is a feature on the way to the world’s largest ball of twine.

I realized this as I was writing about an accidental behavior, that some might claim helps a customer. “Well, it wasn’t planned, but you could consider that a benefit if…”

This is the reasoning behind the joke, “It’s not a bug, it’s a feature”.

My question was, “Was this designed as a feature?”

I realized someone could answer, “Yes, that field is a feature”. Or be confused, thinking “The Product Owner created that object as a feature (story), and we made it. Of course it’s a feature”.

I don’t mean “was this object as part of the GUI, designed?”

What I really should be asking is, “Did someone argue that this would intentionally create a benefit for the customer?”

“Does this add value?”, is something we should be asking more often.

Sentry image

Hands-on debugging session: instrument, monitor, and fix

Join Lazar for a hands-on session where you’ll build it, break it, debug it, and fix it. You’ll set up Sentry, track errors, use Session Replay and Tracing, and leverage some good ol’ AI to find and fix issues fast.

RSVP here →

Top comments (0)

Image of Docusign

🛠️ Bring your solution into Docusign. Reach over 1.6M customers.

Docusign is now extensible. Overcome challenges with disconnected products and inaccessible data by bringing your solutions into Docusign and publishing to 1.6M customers in the App Center.

Learn more