"Quest for Demand" read the note one

This book focuses on issues related to development projects, the topic of which is a problem statement or a collection of requirements, and the requirements are very important in many ways. We usually use a demand map rather than the requirements themselves, so we need to explore the requirements.

Once a tool that ignores human factors is used in the quest for demand, it is impossible to describe the requirements perfectly, which creates ambiguity, while the requirements are clearly stated, but the use of vague words also leads to ambiguity. Ambiguity requires cost and has a huge impact on our problem solving, that is, the importance of ambiguity can be found, so in the process of exploring the need to eliminate ambiguity as soon as possible, using some of the search requirements can be very good to suppress ambiguity tools. Many ambiguities do not necessarily come from one place, and when you find ambiguity in a requirement, you have to position each ambiguity, and the use of a cluster heuristic of any kind of ambiguous voting results can help separate its source.

Explore demand through direct questioning to get demand Ben is not wrong, but there are still some topics hidden somewhere, so no other tools and techniques to assist the direct questioning of the right to get the demand is never enough. The decision tree model is a tool to compensate for direct problems, and this model helps to reach the destination by answering the questions. We need other tools and techniques to reduce ambiguity because, as ordinary people, we are not very good at discovering what we have overlooked, in short, to ensure that direct questioning succeeds, the questioner must be able to ensure a perfect understanding of the early parts of the decision tree. A major mistake for designers is to try to give customers what they need more than they want, and when they find out that you know more about what customers need, tell them they really need what you think they need.

All demand work must occur after a certain type of initial process, and those who propose the idea of the problem are the starting point of the demand process. Everyone has a different way of thinking, which leads to different points of entry, will bring a lot of trouble to the demand process, will also make the whole project in the absence of success is doomed to failure, so in the beginning of a common starting point and the need for the entry point and the needs of all members to establish a balance. One solution is to think that each design project is likely to solve some problems and then simplify each starting point, knowing that the problem statement becomes very common. All development begins with the assumption that the solution to the problem is there.

When a pointcut is identified, the next step in the project process is to ask some free questions. From the decision tree Point of view, free questioning can help you decide which main branch to climb, far more than the analysis of a small branch or a peripheral. Free questioning allows you to find questions about the overall situation in the design process that can be accurately entered in the right direction, and one of the great potential benefits is that they can be prepared before the project is thoroughly understood and can help us overcome the embarrassment of starting a new project or a new relationship. Free questions should be provided early in the requirements process and must be completed before some details are finalized.

One of the most common mistakes in a development activity might be to omit a required person from the discovery requirements, so be sure to identify, locate, and find more participants in the relevant people, which also requires some tools. To identify the customer and user, the customer is the person who pays for our needs, and the user is the individual who will influence or be affected by the product being designed, of course, the customer is also the user, not all users are customers. The customer determines the external attributes of the product, hires and dismisses the designer, and the user is the one who can determine the success or failure of the product. When identifying customers and users, decide what to do with them.

Through this period of time to read the book slowly, every time in the book to talk about the need to explore the need to pay attention to the problem or should be required skills, through the author's own experience of the real case or encountered, see the examples of interpretation, So that we can quickly understand the exploration process should need our attention to problems and solutions to solve the problem, a lot of professional terminology is easy to understand. In this part of the reading, it is necessary to understand the need to use other tools or techniques to assist with direct questioning in the quest for demand, and then we need to identify, analyze, and eliminate demand ambiguity, determine entry points, and balance different points of entry, and then use free questions to get a deeper understanding of the project. Identify and clearly explore the needs of the people in the process. The exploration demand is also a big project, needs all sides to consider, the analysis is thorough, next many aspects need us to understand, the various tools, the technique we also must know, these all are advantageous for us to carry on the right and the accurate demand exploration.

"Quest for Demand" read the note one