User stories and Agile methods read Note three

12th Chapter: What is the story

The user story differs from the IEEE 830 Software Requirements Specification, use case, and the home-pride design scenario.

It is more important to consider the user's goal than to list the characteristics of the scenario.

User stories are similar to use case scenarios. They have different integrity and longevity. They are written for different purposes.

The 13th chapter: The advantage of the user story

User Stories drive us to focus on verbal communication, a shift that provides a rapid feedback cycle.

User stories are smaller in scope than use cases and scenarios. He is suitable for iterative development. Encourage delayed details and encourage development of contingency.

14th. User stories of bad disease trillion list

Stories are too small, stories are interdependent, gilded, stories contain too much detail, too early to contain user interface details, Taiyuan to think, stories to be too frequent, and difficult to prioritize stories. Customers are reluctant to write user stories and prioritize stories.

15th Chapter: Scrum and User stories

Scrum is an iterative and incremental process that iterates every 30 days and becomes a sprint.

The product backlog is a list of functional requirements to be developed. Sprintbacklog is a list of tasks that a team commits to complete in the current sprint.

16th Chapter: Other topics

Tools for using the right projects and teams.

Iterative processes can lead to repeated changes in the user interface.

Once the story is complete, tearing away the story card will have some fun.

Part IV A complete example

This section is a complete example of defining user roles together with Lori, writing stories, estimating stories, creating release plans, and finally writing some acceptance tests for the stories in the initial plan.

User stories and Agile methods read Note three