As a Developer, I want to see functional requirements, so that expected behavior is well documented and is not open to individual interpretations between product, development, and QA.
Requirements
Itemize user requirements
[x] Ticket author uses Defines Acceptance Criteria using GWT format
[x] Ticket author does not need to itemize user requirements separately from those expressed in the user story
[x] Ticket authors can create simpler Task issues a-la Azure DevOps, but not necessarily attached to containing user stories
References
In traditional software engineering processes, user requirements are initially elicited (with a variety of methods - often interviews), and are ultimately transformed into system requirements for implementation, further divided between functional and non-functional requirements. Functional requirements define function – i.e. behavior – which should be tested, conveniently expressed using GWT format. Non functional requirements define other expectations of the system, like appearance which can be communicated with design files, and system constraints like running time, which can often be stated as Then statements after an action or event.
User Story
As a Developer, I want to see functional requirements, so that expected behavior is well documented and is not open to individual interpretations between product, development, and QA.
Requirements
Itemize user requirements
References
In traditional software engineering processes, user requirements are initially elicited (with a variety of methods - often interviews), and are ultimately transformed into system requirements for implementation, further divided between functional and non-functional requirements. Functional requirements define function – i.e. behavior – which should be tested, conveniently expressed using GWT format. Non functional requirements define other expectations of the system, like appearance which can be communicated with design files, and system constraints like running time, which can often be stated as Then statements after an action or event.