focus objects for the inaccurate requirements documents and

[rifattryo.ut11]

What developers often like about product managers is that the function you designed is unreasonable and there are some aspects that have not been considered. As a result, they encounter some "pitfalls" when writing code. They don't know how to deal with some logical loopholes, so they can't write the code anymore, and it won't work if they write it. Some testers prefer to play the game of "finding" from the requirements. Once they find that your requirements document has something missing, they will have to talk to you. They may even call you to their seat and teach you how to "write requirements" like a lecture.



Then they will list you as one of the key This is iranian phone numbers really a "sour and refreshing" feeling! No matter how awesome the product manager is, he is still being ordered around by me. At the same time, he has already taken a favorable position and will stare at you and urge you to quickly complete the requirements document. Urging people to change things and finding problems in things are the two basic skills that testers are best at. So once there is a problem in the logic of the requirements document you wrote, wait for the R&D and testers to go back and forth! .



The functional design is too complicated and the technical difficulty of implementation is too great. When we are conducting requirements review, the R&D personnel are not appreciating how awesome your product design is. They are looking for "pitfalls" with a magnifying glass. I was thinking in my mind, how many new tables do I need to create to implement this function? Where will the data come from? Should I run a separate task? Will it conflict with existing functions? What else have I not considered? Is it logically feasible? After a thorough analysis, I can probably know whether the "bricks" in the next period of time are easy to move or not.