DEV Community

Discussion on: Enough with the User Stories already!

 
just_in_social profile image
Justin Wigtion

Although that makes your title rather confusing

Thread Thread
 
redfred7 profile image
Fred Heath

hey Justin, thanks for the feedback.

I don't think the title is confusing, I advocate stopping referring to User Stories as first-class entities in the Requirements Domain when they are just descriptive devices, so 'enough with the user stories' captures this sentiment :)

As to your first point, readers shouldn't be BAs or POs in order to understand the difference between Requirements and Specifications, or to know what a domain model is, or to grok the difference between an entity and an attribute. I dare think that most developers in this day and age are involved throughout the project lifecycle, so managing requirements is IMO an essential skill.

Thread Thread
 
pabrams profile image
Paul Abrams • Edited

When you say "Enough with the user stories" it sounds like you're saying we should get rid of them completely, so it seems like a pretty confusing title to me, too.
And who ever said User Stories were "first-class entities in the Requirements Domain", anyway? I've only ever understood or used them as tools to help communicate requirements. Business people (often subject matter experts, and not real BAs) put a lot of emphasis on them, because those are usually the only artifacts they understand.

Thread Thread
 
redfred7 profile image
Fred Heath • Edited

Hi Paul and thanks for responding

And who ever said User Stories were "first-class entities in the Requirements Domain", anyway?

Whenever we talk about creating, reading and delivering user stories we are implicitly accepting them as first-class entities in the Requirements Domain, instead of just descriptors.

I've only ever understood or used them as tools to help communicate requirements

That they are. But they are also used to communicate specifications, business goals, capabilities and technical tasks. So let's start referring to these entities instead of their associated user stories.