Writing Good Requirements
Understand what constitutes good requirements.
Learn how to write good requirements, as user stories.
Be able to write good user stories following the INVEST principles.
Learn what acceptance criteria is, and how to write them according to the Given-When-Then format
A core responsibility of a BA is to write the requirements of the stakeholders in a way that is understandable by the development team to be delivered effectively and in the way that it adds value to the stakeholders.
A good requirement should always be necessary, verifiable and attainable. As such, it is our duty to get the proper understanding about the requirements during the elicitation process and document them comprehensively.
User stories are the most popular way of writing requirements, and this challenge will equip you with the knowledge to write good requirements using the INVEST principle.
For the given case study, answer the following questions:
Write down at least 5 assumptions you would make in order to define the requirements better.
List 5 key features expected by each of the key user groups based on the case study.
For each of the 3 key user groups, write 3 user stories each using INVEST principles
For each of the user stories above, write Acceptance Criteria using the GIVEN, WHEN, THEN format.