Requirements Review, Include Version Each module is pulled together to category email list review and determine which requirements can be included in this version plan. This involves the overall scheduling of demand, so there must be a war of words here. 5. Demand tracking, grasp the progress For product managers, requirements tracking is most important to reduce the risk of delays. At the same time, evaluate the category email list temporary increase in demand, and give a reasonable estimate of the delay risk brought by it.
As a requirement proposer, track the completion process of category email list requirements and communicate with developers in a timely manner to ensure that requirement understanding meets business requirements. I've had situations where requirements fulfillment didn't match expectations. I raised a report requirement, which I thought was a very clear and simple requirement. But when the development let me accept it, I was category email list dumbfounded, and the values of many indicators were unreasonable.
Later, it was discovered that his understanding of the indicator was deviated category email list from our definition. This caused him to return to work, and our demand was delayed, which was really miserable! Emphasize that requirements tracking is really, really important! It's not advisable to throw hands category email list at the shopkeeper! 6. Requirement acceptance, closed-loop process One of the requirements acceptance is the tester acceptance.