COMP 4004 Lecture Notes - Lecture 2: User Story, Activity Diagram
26 Oct 2018
School
Department
Course
Professor
Document Summary
User stories: an agile introduction: a good way to think about a user story is that it is a reminder to have a conversation with your customer. In short, user stories are very slim and high-level requirements artifacts. Import considerations for writing user stories: 1. Stakeholders (the domain experts) write user stories: 2. Use the simplest tool (often written on index cards: 3. Indicate the estimated size (assign user story points to each card: 5. Indicate the priority (priorities of high/medium/low are often used instead of numbers and some people will even assign each card it"s own unique priority order number e. g. 344, 345, etc. : 6. Optionally include a unique identifier (if you need to maintain traceability between the user story and other artifacts, particularly acceptance tests: mike cohn suggests a more formal approach to writing user stories. Scheduling: priority assigned to a story affects when the work will be done to implement that requirement, 2.
