Reflection caused by the program

Reflection caused by the program

When you are in the bow and night writing code, whether to think I write this part in the product occupies what position, belong to which link, why have such demand, from where, and where to go, eventually will produce what effect, and will bring how the cycle. With these doubts, the cause and effect of the original.

How to raise demand

Through the market excavation and analysis, from the specific phenomenon of abstract product concept, in the product concept refined into specific requirements, and form a document outline, guide product development, resulting in market analysis documents, as well as product requirements documents. When this is just a general concept, which involves a lot of detail, as well as departmental collaboration, the final refinement needs to be realized by you. The specific process can be seen,

How to control the demand cycle

With the instructions above, you may already have an understanding of the entire process of the product, but there is another problem here, how to control it? A picture to help you understand the control process.

How to cycle Products

A product on-line, does not mean that it has been completed, remember not to produce this mentality, you have to remember that this is just the beginning, lean entrepreneurship theory is a perfect interpretation of this (please follow the summary of this), from the collection of user data, analysis data, validation of the existing functional effectiveness, and extract new requirements, The project cycle is then re-entered.

Summarize

This is just a simple product flow, so that we have a concept, as a programmer, need to stand on a higher level to look at the problem, it is time to jump out of the mire of code, with a new perspective of the interpretation of what you do, you will find a different landscape, the original everything is from this.

Reflection caused by the program