I spent way too long debating whether to write 2 or 3 stories.
Start by clarifying the feature's scope and user personas (learners and instructors), then write user stories that follow the INVEST criteria, focusing on the core actions: submitting and watching short videos. Prioritize stories to deliver incremental value, and include acceptance criteria to make them testable.
Pro tip: Frame stories around user outcomes and business value, not just technical tasks, and explicitly mention how you'd handle edge cases like video moderation or offline viewing to show product thinking.
Ask clarifying questions about who can submit videos (learners only or instructors too), where videos appear, and any constraints (e.g., moderation, storage). Identify primary personas: learners who watch and learners who submit.
Write 2-3 user stories covering the main actions: submitting a short video, watching a video, and possibly moderating or managing videos. Use the format: 'As a [persona], I want [action] so that [benefit].'
For each story, list specific, testable acceptance criteria (e.g., video length ≤ 2 minutes, supported formats, upload progress, playback controls). This ensures the stories are ready for sprint planning.
Order the stories by value and feasibility, and consider slicing them into smaller increments (e.g., basic upload first, then playback, then moderation). Explain your prioritization rationale.
Briefly check that each story is Independent, Negotiable, Valuable, Estimable, Small, and Testable. Adjust if needed to ensure they fit within a sprint.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.