In an agile software development project, writing down requirement is one of the most important activities that should be done. When the requirements are clear and written down in proper order, developers will be able to go ahead and start working on them accordingly. This can contribute a lot towards the success of an agile software development project.
When writing down agile requirements, it is important to take a separate document. On the index page of the document, you need to list down the goals and properties of the document. You should be short and brief at the time of communicating all the goals of the document. Then you should write down the background or the requirement from business. If there are any assumptions, you should write down them as well.
Next, you come to the most important aspect of writing down agile requirements, which is the compilation of user stories. It is possible to list down all the users who are involved with the development and then write down the user stories. Your user stories should be broken down into granular level as much as possible. Then only you will be able to end up with effective user stories. The user stories should cover all different aspects of the development as well.
For example, assume that you are creating a login page for a website. Then one of your user stories should be “As a user of the website, I should be able to see a link to retrieve my password, so that I can recover the password when I cannot remember it.” This user story will represent one granular level requirement of the login page. Likewise, it is important for you to have the other requirements written down in clear format.
Next, you should use user interactions with the system. If there are any questions, you should list them down.
— Slimane Zouggari