Handling Non-Functional Requirements in Agile Projects

Поділитися
Вставка
  • Опубліковано 17 лис 2024

КОМЕНТАРІ • 2

  • @the0nerens
    @the0nerens 8 місяців тому

    This is very clear, great video! One small questions, I still struggle with something like Scalability. In my eyes it's important for all user stories, but do I have to write and acceptance criteria for every user story which says that the system should be able to handle 10.000 concurrent users for example?

    • @agilecheetah8954
      @agilecheetah8954  7 місяців тому

      Glad you found the video helpful! No, you don't need to state that across all of your user stories. Just make sure that your acceptance criteria don't contradict NFRs. In other words, how the functionality that satisfies a user story functions and behaves should support, or not take away from, realizing NFRs. In your example, stress testing the feature along with the entire application will highlight whether it performs as stated in NFRs. NFRs are system-wide constraints.