Are equivalent to the mixture of the operation Whatsapp Mobile Number List proficiency of the novice players + the product understanding of the skilled players + the industry understanding of the big players, the questions and comments raised by the judges are likely to be you if this product is put on the market, the problem will be exposed Whatsapp Mobile Number List immediately. Once the judge brings up a product point that he is not clear about, or even a problem that you have not thought of before, then immediately write it down, this is a defect in your product. Your current product may dissuade novice players, hurt skilled players, and drive big players crazy because of these flaws.
With this feedback, you can use this to deduce: since my product has these problems, what is wrong with my function point design? Or is there Whatsapp Mobile Number List something wrong with my user scenario thinking? Am i not getting the real needs of users? Or is there a problem with the underlying logic of my product? Or is there a problem with the Whatsapp Mobile Number List business model of my product? Could it be a user experience issue at the top level? … from these perspectives, rethink the product requirements of how the function points related to this module of your product are done.
Rethink what kind of scenario Whatsapp Mobile Number List your user scenario is, and does it really exist? Is it possible that you think wrong, this scenario does not exist, there should be another scenario; rethink your user needs, start from the user scenario, rethink your user story, and analyze the unreasonable existence of it local, even further build Whatsapp Mobile Number List a set to actually play out your user story, and then let yourself become a user, to think about why mushrooms need umbrellas from the perspective of mushrooms; rethink the underlying logic of your product.