User stories are short descriptions of features or functionality that provide value to end users. They are written from the perspective of the user and follow a standard template of "As a <role>, I want <goal> so that <benefit>". User stories should be independent, negotiable, valuable, estimable, small, and testable. They provide a way for customers to influence development without formal requirements documents. Acceptance criteria define how a story will be considered complete. User stories are used in agile methodologies like Scrum to plan and track work in sprints.

1. User Stories

4. Example:

6. Story must describe the What not How.

9. Negotiable - They are not written contracts or requirements that the software must implement. Story cards are short descriptions of functionality, the details of which are to be negotiated in a conversation between the customer and the development team.

10. Valuable - each story must bring some business value.

11. Estimable – the scope of as story must be observable.

12. Small – to estimate, to track progress

14. Business analyst can be a surrogate of a customer.

16. Example:

18. Organizer CRUD userstories: R US 2. As a user I want to view the records that have a particular date, time specified on the calendar, so that I can schedule my plans._____________Acceptance criteria: System displays the records that have date specified on the calendar.Size: medium. Priority: highSprint: 1

19. Organizer CRUD userstories: R US 3. As a user I want to view the records with no date specified on the tasks section, so that I can view my tasks that have to schedule._____________Acceptance criteria: System displays the records that have no date specified on the tasks pane.Size: medium. Priority: mediumSprint: 1

20. Organizer CRUD userstories: U US 4. As a user I want to edit the records stored persistently in the app, so that I can change my plans._________Acceptance criteria: 1. System allows to edit an existing records.2. The entered/existing data is saved successfully to the persistent storage when the user saves the record.Size: big. Priority: lowSprint: 2

21. Organizer CRUD userstories: D US 5. As a user I want to delete records, so that I can clean up the mess.______Acceptance criteria: The record is deleted from the persistent storage and is no longer available.Size: simple.Sprint: 2

23. Agile > XP

26. Sprint Backlog

27. User Story XXX

28. Task 1

29. Task 2

30. Task 3

32. Identify user role

33. Identify value

34. Identify acceptance criteria

35. Estimate the story