Career Forums

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  User stories vs requirements
Previous Previous
 
Next Next
New Post 7/26/2024 10:47 AM
User is offline Jw3000
1 posts
No Ranking


User stories vs requirements  
Modified By Chris Adams  on 7/26/2024 1:09:33 PM)

I'm trying to understand the different between a user story and a requirement.Is there a hierachy like the requirements come first and then user stories created in the backlog. Maybe I'm confusing myself but always thought the user stories are just a way of representing a requirement and then acceptance criteria is the functional aspect? But then unsure how this relates to a product requirements document?I often hear that agile doesn't mean you don't have a requirements document,so how does that relate and interact with the user stories? I Would really appreciate some input to how everyone structures and approaches the documentation of requirements in agile.

 

 
New Post 8/14/2024 9:25 AM
User is offline Gildas
3 posts
No Ranking


Re: User stories vs requirements  
Modified By Chris Adams  on 8/14/2024 9:38:42 PM)

ISO29148 defines a requirement as "a statement which translates or expresses a need and its associated constraints and condition". According to the définition, user stories are requirements since they express a business or user need. They are also source of requirements : the acceptance criteria.

I'm not an agile practitioner. Whatever the software devolpment process is, we need a softwate requirements document.

Best regards,

Gildas 

 
New Post 8/17/2024 7:43 AM
User is offline steve
2 posts
www.parkson.us
No Ranking


Re: User stories vs requirements  

Userr stories are specifically not requirements. They are, as Ron Jeffries, the "inventor" of user stories, says, "tokens for communication".  The idea is that when the agile team selects a specific user sroty to do in the next iteration, the developer and user discuss the story. The developer asks questions that, when answered, give the developer the specifications, or requirements, for creating the software that completes the user story as requested. The developer also asks the user "what do you need to see to prove to you that this user story is complete?" and together they define the acceptance criteria or tests for the story.

As a result, user stories can be ambiguous, vague, incomplete, redundant, wordy, incorrect, and so forth, all of which is ironed out in the conversation, and none of which is allowed for a requirement (at least accoding to the IEEE).

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  User stories vs requirements

 






 

Copyright 2006-2024 by Modern Analyst Media LLC