User Story Format
As a <user type>, I want <goal>, So that <benefit>.
উদাহরণ
As a registered customer, I want to reset my password via email link, So that I can regain access if I forget my password.
Acceptance Criteria (Given-When-Then)
Given the user is on login page When they click "Forgot Password" and enter email Then system sends a reset link valid for 30 min And shows confirmation message And logs the request
INVEST Principle ⭐
- Independent
- Negotiable
- Valuable
- Estimable
- Small (1 sprint)
- Testable
Epic → Feature → Story → Task
Epic: User Account (3 months) ├── Feature: Authentication (1 month) │ ├── Story: Email login (3 days) │ │ ├── Task: Frontend form │ │ ├── Task: API endpoint │ │ └── Task: DB schema │ ├── Story: Password reset │ └── Story: 2FA
Use Case Detail (Cockburn)
Use Case: Borrow Book Actor: Member Precondition: Logged in, book available Main Flow: 1. Member searches book 2. System displays results 3. Member selects, confirms 4. System creates loan record 5. System sends confirmation Alt Flow: 4a. Unavailable → suggest reservation Postcondition: Loan recorded
Backlog Grooming
- Description clear, acceptance criteria
- Dependencies identified
- Estimated (story points)
- Priority set, splittable