For new products, the most troublesome meeting is the requirements review . In the past few years of making products, the author has held hundreds of demand category email list review meetings. I was once crying at the meeting by R&D, and I also encountered a situation where R&D and the product quarreled for half an hour, and finally one party slammed out of the door. . But category email list this was a tragedy in the beginning. At that time, I was trembling with fear at the thought of having to face nearly 10 R&D projects by myself.
Today, almost every requirements review has gone fairly smoothly, with the timing and results as expected, without even requiring much additional preparation. Many product newcomers worry that they can't beat R&D, but in fact, the word "R&D" puts themselves on the category email list opposite side of R&D. Many of the quarrels and arguments in the requirements review are unnecessary after the meeting, and most of them stem from poor information and communication category email list skills. Therefore, today I want to share with you how to do a good job in demand review and no longer be afraid of being scolded.
This article will discuss from multiple perspectives such as product, R&D and team . The following is a catalogue. I hope everyone can have a category email list framework in mind in advance: What is the meaning of needs assessment? Stages and Processes of a Standard category email list Requirements Review How to manage the meeting of requirements review well What do the front-end, back-end and testing focus on at the requirements review meeting? 3 Demand Review Tips for Pressing the Bottom of the Box! 1. What is the significance of needs assessment? Directly using a bunch.