Requirements Structure and Organization

The requirements section allows for the creation of folders, text documents, and requirements. These allow you the flexibility to organize and structure your thoughts, ideas, and requirements in ways best suited for you and your teams. 



Folders and sub-folders provide flexibility and allow for hierarchy and categorization, or even as a place to keep unneeded items for hold or intended for deletion. 





Text Documents

Text documents provide ways to capture stories and thoughts, among other non-requirement items. Common uses for text documents are for capturing user stories.

User stories are typically non-technical context describing, from the end-user's perspective, how the product should work or the desired outcome. The intent is for the team to understand what they are developing, why they are developing it, and the value provided to the end-user. These user stories allow the team to stay focused on the user needs. They also allow the team to understand the end goal and to collaboratively and creatively think of the best solution to get there. 



A requirement is a formal specification of a feature (or part of a feature) of a project's end product. Therefore, by definition, requirements formally state the behavior, presentation and user experience that the end product should have when it is released to the consumer.  Learn more about requirements. 




Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.