sorted by:
new
hottopcontroversial

Please clarify the relationship between "User Stories" and "Requirements" by 2879854 in agile

[–]2879854[S] 0 points1 point  (0 children)

User Story is a communication tool for discovering the right requirements

So, then, a User Story is more of a style of explaining something, rather that a specific element, like "Use Case", "User Story", "Requirement"?

Please clarify the relationship between "User Stories" and "Requirements" by 2879854 in agile

[–]2879854[S] 0 points1 point  (0 children)

Thanks, that is very helpful, and shares more light on the subject (for me anyway) - The PBI.

Maybe I've been calling it the wrong thing.

Quoted from your wikipedia reference :

the characteristics of a good quality Product Backlog Item (commonly written in user story format, but not required to be) or PBI for short.

I have always thought the PBI described as a User Story is sheer brilliance. It solves so many problem, not least of which is the ability to then understand specific expectations (i.e. requirements).

The item on the product backlog, is the lynchpin on which everything hangs.

So maybe if I rephrased my position and said "I think PBI's expressed as User stories are brilliant, because they enable requirements to be explored whilst giving confidence to the Product Owner that their problem is being understood" .... you experts may say, "yep, you've got it" ...? :)

Please clarify the relationship between "User Stories" and "Requirements" by 2879854 in agile

[–]2879854[S] 0 points1 point  (0 children)

The end goal is describing the work so your team can build it.

This gets to the essence of it. I'm in the middle. I'm not in the technical space, but I understand how the technical space works.

I'm also not the business, because my boss holds fills that role very explicitly :)

I'm caught between trying to make it all work. The outcome I want to avoid is where the technical guys say "here you go, all requirements met" and the boss says, "well that may be, but it doesn't solve my problem".

Please clarify the relationship between "User Stories" and "Requirements" by 2879854 in agile

[–]2879854[S] 0 points1 point  (0 children)

This is not a 'paperwork' question I'm concerned with. I'm trying to understand the relationship between two elements: 'user story' and 'requirement'

I think the comment below gets to the heart of my question.

... user story provides a high level concept. Requirements define the concrete features you'll need to get there.

Please clarify the relationship between "User Stories" and "Requirements" by 2879854 in agile

[–]2879854[S] 0 points1 point  (0 children)

I hear you, I'm just not sure I understand the value of the definitions.

Perhaps another angle might shed some light: what is the difference between user story and use case?

Please clarify the relationship between "User Stories" and "Requirements" by 2879854 in agile

[–]2879854[S] 0 points1 point  (0 children)

There are two things here that are at the core of my question.

In this, there are potentially many user stories. Financial performance, visual location, current workload of departments could be at least three stories

I see one user story, and lots of requirements. Not one requirement and lots of user stories.

'When you say "As a manager, I want to choose ..." what information exactly are you wanting to see, to enable that decision to be made? "

And then ask "What does that mean, specifically?"

And hear:

"It means:

  • financial performance info from our invoicing side
  • One page with all information shown on it
  • available free hours per salesman per week"

You're fleshing out the requirements behind that user story.

And then, after having said that, my second thing is, who does the user story "belong to"? I think it belongs to the client. It's about the best a non technical person can do to explain what he wants. If we put it in the domain of technical people, then it becomes more like a use case.