-2

As far as we know, the User Stories are the way a requirement is defined in bounded context with acceptance criteria. On the other hand, the Product Backlog enlists all requirements, i.e., new feature, enhancements, and existing production issues.

This is not clear, if or if not, the Product Backlog just consists out of User Stories. So, the question here is as follows.

Does the Product Backlog just consists out of User Stories in Agile Development?

closed as unclear what you're asking by gnat, 17 of 26, Eric King, Peter K., Greg Burghardt Jan 10 at 14:53

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    Did you try searching for this? See scrum.org – Greg Burghardt Jan 10 at 14:35
  • 1
    Rumen sums it up. But perhaps you can explain more about what you see the difference to be? – Ewan Jan 10 at 14:41
  • 2
    You say "as far as we know"... How do you know that? What research have you done already in the topic? I say that because "the way a requirement is defined in bounded context with acceptance criteria" doesn't sound like a User Story to me. I think if you read more on the topic you question would be naturally answered. – Eric King Jan 10 at 14:45
  • Yes @GregBurghardt, thank for the link. Also, I updated the question so that you could understand my doubts. – Francisco Maria Calisto Jan 10 at 14:47
3

The product backlog is simply list of user stories.

  • 1
    If possible, please provide more description to your answer. For instance, you could give some examples. As well as, more information regarding the topic. – Francisco Maria Calisto Jan 10 at 14:28
  • 1
    I think this answer pretty well covers the gist of the relationship, but I would like to add that a Product Backlog may contain stuff other than User Stories. – Eric King Jan 10 at 14:43
  • 1
    @EricKing Why? Can you give some examples? If they're requirements, they shouldn't go into the backlog until they're written as user stories. If they're not requirements, ignore them until they're framed as requirements... after which, see my first point. – Peter K. Jan 10 at 14:48
  • 1
    @PeterK. A User Story is a particularly formatted type of requirement statement, written from the perspective of the User. There are many other ways to express a requirement that aren't written in the form of a User Story. A backlog can contain any of those requirements. That's all I mean. – Eric King Jan 10 at 14:51
  • 1
    Yes, as well as user stories, there might be research epics/spikes and technical tasks like repayment of technical debt. – James McLeod Jan 10 at 21:37

Not the answer you're looking for? Browse other questions tagged or ask your own question.