Requirements and User Stories Flashcards
What is a requirement?
a requirement is a service, function or feature that a user needs. Requirements can be functions, constraints, business rules or other elements that must be present to meet the need of the intended users.
What two types of requirements are there?
Functional requirements: what it does and how well it performs. They express a function or feature and define what is required
Non-functional Requirements define how well, or to what level a solution needs to behave. They describe solution attributes such as security, reliability, maintainability, availability
What is a User Story?
A User Story is a requirement expressed from the perspective of an end-user goal. User Stories may also be referred to as Epics, Themes or features but all follow the same format.
A User Story is really just a well-expressed requirement. The User Story format has become the most popular way of expressing requirements in Agile for a number of reasons:
It focuses on the viewpoint of a role who will use or be impacted by the solution
It defines the requirement in language that has meaning for that role
It helps to clarify the true reason for the requirement
It helps to define high level requirements without necessarily going into low level detail too early
What are the 3Cs of User Stories?
Card
Conversation
Confirmation
Requirements activity during Evolutionary Development
At the outset of each Timebox, the User Stories allocated to that Timebox will be further investigated. The User Stories from the PRL are broken down into more detailed User Stories which are small and clear enough for the team to work from. The detail is only elaborated one Timebox at a time, and thus the complexity of the requirements is managed. Also, the fine detail is only elicited immediately before that element of the solution is created. This avoids time being wasted on developing detail on all areas up front.
