The scope of demand is also a factor that affects our efficiency. It is also the realization of attendance requirements. In the simplest case, it can only be made into a module similar to calendar check-in, but if it is larger, it can be made into email list an independent product, such as
If the scope of the requirements is too large and the functions are too complex, the cost will be increased and the cycle will be prolonged. If the functions are too simple, it will not be able to meet the requirements well.
Therefore, the ideal situation is that we only do those important functions and improve the cost performance of the functions, so that they can meet business demands and save costs to the greatest extent.
Of course, it is not so easy for us to control the scope of requirements in practice, because there are some objective difficulties:
When we conduct demand research, we usually collect a large number of scattered demands. Among the demands put forward by these demanders, in addition to core demands, there will also be divergent non-core demands. If we do not control it, we will easily overdesign. , reducing the cost-effectiveness.
Even if the core demands of the demand side have been extracted very accurately, how to design cost-effective functions will become a difficult problem for us, because different product managers will have different solutions for designing the same function. Some of them know which solution to use to meet the demands will be more cost-effective, while others will make more complex functions, which will also expand the scope of demand.
The solution is:
It is necessary to judge which functions are necessary and which are just icing on the cake through demand analysis during research; ask the reasons for doing so, and determine whether the usage scenario really exists; whether it can be removed, and if not, can it be implemented later.
We need to accumulate enough functional solutions in our minds to be able to provide cost-effective solutions in a short period of time based on the previous demand research. We can accumulate them in two ways. On the one hand, we usually experience the functions of other products more often. On the other hand, it is to accumulate functional solutions through a lot of project experience.