After reading the "User Stories and Agile" Today's Chapter 12: The user is not
The user is not IEEE 830, not the embodiment, the scene is not available. After reading this chapter, I learned that for any method, there will always encounter ring true, we will look at some bad signs or signals when the problem occurred. Most of the time, holding a list of features to allow customers to use the given scenarios that feature, we will save a lot of unnecessary work. Customers often find that some features they really need to, we should have to spend time on value-added things. The scene is a detailed description of user interaction with the computer. No matter how comprehensive was expected, we can not fully define a complete system of considerable size. User stories and use cases should be written in a different purpose, use cases are written to facilitate developers and customers to discuss and reach a consensus, and to facilitate plans to release and discuss remind demand for details.