Jump to content

9.2.2 User Stories, Sprints

From Computer Science Knowledge Base
Revision as of 02:30, 10 July 2025 by Mr. Goldstein (talk | contribs) (Created page with "=== 9.2.2 User Stories, Sprints === Two key ideas in Agile are: * '''User Stories:''' Instead of long, technical documents, Agile teams describe features from the perspective of the person who will use them. A user story sounds like: "As a gamer, I want to be able to jump over obstacles, so I can explore new areas." or "As a parent, I want to track my child's homework, so I know what they need to do." This helps everyone understand ''why'' a feature is important and wha...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

9.2.2 User Stories, Sprints

Two key ideas in Agile are:

  • User Stories: Instead of long, technical documents, Agile teams describe features from the perspective of the person who will use them. A user story sounds like: "As a gamer, I want to be able to jump over obstacles, so I can explore new areas." or "As a parent, I want to track my child's homework, so I know what they need to do." This helps everyone understand why a feature is important and what problem it solves for the user.
  • Sprints: As mentioned with Scrum, a sprint is a short, fixed period of time (like 1 to 4 weeks) during which a team works to complete a specific set of user stories. At the end of a sprint, the team should have a working piece of software that can be shown to the people who requested it. It's like having mini-deadlines to keep everyone focused and motivated.

Bibliography:

  • Cohn, Mike. User Stories Applied: For Agile Software Development. Addison-Wesley Professional, 2004.
  • Schwaber, Ken and Sutherland, Jeff. Scrum Guide. Scrum.org, 2020.
Retrieved from "https://wiki.omnivision.website/index.php?title=9.2.2_User_Stories,_Sprints&oldid=294"