they can discuss it with the product manager, the "Party A".

[rifattryo.ut11]

Every project has a time requirement for going online. It's like a "small alarm clock" ticking in your ears. Project managers often keep the word "rushing" on their lips to urge everyone to work quickly. One problem this brings is that R&D personnel sometimes really have no idea how to implement this product function within the limited time? If it takes a day to think about the technical implementation method, you have to work overtime for a day on the weekend to make up for the progress! In this situation, if you can avoid working overtime, then you definitely won't work overtime.



People will instinctively think about whether for iranian phone numbers the product manager. Everyone has this idea, except for the R&D manager who doesn't write code. As long as the product manager agrees, you don't have to work overtime. Why bother to rack your brains to find a solution? Why waste your brains! . The cost-effectiveness of the demand is too low, and the product has no value and is not cost-effective. R&D personnel are not the kind of "mechanical workers" who "do whatever you say"! They also have their own work enthusiasm, sense of achievement and pride.



If they think that some functions have no value, they will resist. It is a very reasonable mentality to consider the value of communicating the requirements with you from the perspective of gilding their own work and saving resources for the company. In particular, some functions are too technically difficult to implement and require a lot of time to invest, and there is a certain risk that they cannot be done. In his opinion, the value of doing this function is not great, so he will consider whether it is cost-effective to do it, and he must also consider the issue of keeping his job.