In Scrum, are stories supposed to be a replacement for product requirements?



  • In Scrum, are stories and acceptance criteria supposed to be a replacement for project scope and product requirements? Is it convenient that all requirements are scattered over many issues in Jira (instead of being kept in a single document)?



  • In Scrum, are stories supposed to be a replacement for product requirements?

    No, they are not.

    One of the Agile values is "Working software over comprehensive documentation". One reason being that it's hard to define what the product should do from the beginning. Once the clients see the software, they will want changes because they get a better understanding of what they need once they see the software working. That's also why you build software in short iterations: to get feedback quickly and make sure you build the right thing.

    In this context, starting software development with a large software requirements document doesn't really make sense. But if you don't have a full specification document, you still need something as the basis of your developments, and user stories are a better tool for this environment. They are just a "placeholder" for the discussions you need to have about what exactly you need to build.

    See the following links for more details:


Log in to reply
 

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2