Some relevant suggestions for requirements review
1. It is important to discuss the product in combination with the background. We can discuss the status quo and the specific reasons for the status quo as our group, and then to the solution, discuss some pain points and hatred points of business functions in today's environment to customers, and then explain how our products solve the problem.
2. Analyze current hot issues. Just as the system we want to make is a questionnaire system, we received a questionnaire about the activity just before the review, which happened to be a hot topic, we took this hot topic as an example and conducted an analysis of its pain points and hate points. elaborate. Use hot topics to resonate with everyone.
3. Data visualization. When performing data analysis, it needs to be displayed in the form of charts to visualize the data, which can reduce the visual fatigue of the viewers, allow the viewers to fully immerse themselves in your speech, and understand the final purpose you said to express.
4. Remember to compare the pros and cons when discussing the product. When there are some products similar to the company's products on the market, you must do a market research and analysis, fully analyze the advantages and disadvantages of competing products, and define the standard line, compare the company's products with the market's products from different angles, and summarize Our market share strategy.
5. There must be a sequential logic when speaking. There needs to be a general logic when speaking, so that the audience's thoughts will not be interrupted, and the audience will not feel the effect of frequency modulation.
6. You can conduct a preliminary research on the product. This is a discussion from the perspective of product thinking. When positioning a product, you can conduct research on the product through questionnaires or other forms. The form of research can better understand user needs, especially TC products.
7. Clarify the relationship between stakeholders and user roles. Stakeholders refer to in project management: individuals or organizations (such as customers, sponsors, executing organizations or the public) who actively participate in the implementation or completion of the project whose interests may be positively or negatively affected, rather than user roles in the system, General user roles refer to super administrators and ordinary administrators, but these roles may not necessarily participate in the implementation and completion of the project, and the difference between the two must be clarified.
8. PPT must be used in the process of requirements review.
9. If it is a TC platform, the user's adhesiveness needs to be considered.
10. During the review process, the general time plan of the project needs to be given. Increase user confidence.
11. Use modeling tools reasonably.
12. Non-functional requirements need to be mentioned during the requirements review process.
13. The process of telling needs to show his sincerity.
14. The review process requires trade-offs, such as the need to discuss some public functions.