Techno_5 User Story Flashcards
It is a short, simple description of a feature from the end-user’s perspective.
User Story
It defines who the user is, what they need, and why it’s important.
User Story
How does User Stories help in task?
help Agile teams break down work into small, manageable pieces.
Who creates User Stories?
PRODUCT OWNERS & DEVELOPERS
What does creators make User Stories
- USER INTERVIEWS & FEEDBACK
- MARKET NEEDS
- BUSINESS GOALS
What are the user stories used in Agile Development?
- Discovery and Ideation
- Planning and Prioritization
- Development
- Testing and Validation
- Iteration and Feedback
What is Functional Acceptance Criteria
(What the system should do)
* Defines specific features, functions or interactions
Example
* The system must allow users to log in with an email and password
* User should be able to reset their password via recovery link
Define the Key terms in Agile Development:
Epic, User Story, Task
- Epic - A large goal that contains multiple user stories.
- User Story - A single feature within an epic
- Task - A small piece of work needed to complete a user story
What is Non-Functional Acceptance Criteria
(Performance, Security, Usability)
* Specifies how well the system should work
Examples:
* The page should load within 3 seconds on a mobile Service
* The system must handle 100 concurrent users without performance degredation
What is Business Rule Criteria
(Compliance with business rules)
* Defines conditions that align with industry standards, laws, or company policies
Example
* The application must comply with GDPR data privacy regulations
* Transaction above 50k required two-step aunthentications
What is User Experience Criteria
(Ease of use, design, accessibility)
* Defines how the system should behave from a user’s perpspective
Example
* The interface should follow Material Design Guidelines
* Error messages should be displayed in red with clear explanations
Explain the difference between Backlog and Sprint Backlog
- Bocklog - A list of all user stories for a project
- Sprint Backlog - A subset of high-priority stories selected for development
What is MoSCoW Method
(Technology/Product Centric)
* M- Must Have (Essential)
* S - Should Have (Important but not critical)
* C - Could Have (Nice to have, but not necessary)
* W - Won’t Have (Not a priority for now)
What is KANO Model
(Customer Centric)
* Basic Needs (Must Have) - Expected by User
* Performance Needs (More is better) - Directly affects satisfaction
* Delighters (Exciters) - Unexpected but highly appreciated
* Indifferent Features - No impact on user satisfaction
* Reverse Feature - Some users dislike them
