R&D how to adjust the requirements so as to change

[rifattryo.ut11]

For example, if we want to make a map, we can't do it without a third-party interface. At this time, we have to find external resources to ask them to help. Although there is an extra process, it is better than giving up! The changes to the requirements are too big and the existing technical framework has to be changed. Sometimes, in order to meet a certain requirement, the existing technical framework may need to be changed. For example, in a middle-end system developed with the TM framework, adding video and animation effects may require changing to a framework with front-end and back-end separation.



At this time, we have to discuss with Of course, to iranian phone numbers determine whether a function can be technically realized, product managers must also understand some technical knowledge. Otherwise, they will be in the dark and confused, so how can they communicate with R&D on how to implement it technically. . Time problems are mostly caused by division of labor or ability problems. R&D hopes that the adjustment of requirements mainly involves two aspects: there are other projects in the process, and the launch time of new requirements conflicts with each other.



In this case, we have to find out the details before the product requirements review to see if the R&D staff already have a lot of things on hand. If this guy must be involved in this project, then we have to adjust the project schedule or re-order the function priorities instead of simply adjusting the requirements. The time required by the requirements is too short and the personal technical ability cannot do it. When we do project time estimation, we usually roughly calculate it by man-days, but often do not take into account the ability level of each person.