If the requirement is only shown at first glance-no profit or product

After two weeks of multi-function statistics, I was confident that I had obtained the product that the customer wanted, added some of the features that I thought were very important to me, and finally communicated with the customer, find that something has deviated from what the customer wants.

If the demand is just like the first sight, this is not the case at all. You may not be able to look at the best things at first sight in reality. Maybe when you look at the second and third eyes, far from the first sight.

At first glance, the customer has a lot of contact with the market, and can get the first-hand user requirements, which coincide with the previous statistics. What you want to do is what others want to do.

Requirements should also begin with collection, analysis, and evaluation. However, in a short period of time, there are various analysis and tests, and there is no time to do it without human resources. If there is anything around you, you can find the appropriate agile method, simplify the document, and simplify the process, this is a process of cutting.

As a developer, inertial thinking generally refers to how to implement it technically and reminds me not to be brought into the technical cycle. What should I consider now? -- Commercial value of products

In my understanding, the commercial value of a product is that, while solving user problems, it can bring benefits without profit.

 

My requirements list:

Module, Overview, detailed description, business value, business attributes, business priority

 

The actual cost of development is not taken into account here. Some features give you a glimpse of the number of person-days, and you can control your own ignorance.

When the demand comes, we know what to do, how to grasp the commercial value of the product, and how to choose.