In the work of product managers, temporary requirements are the most common type of requirements. Often, a requirement is thrown over without warning, and the product manager is confused. At this time, what is the need to do? Or not to do it? How to bulk sms service handle it as well? As a product person, you may have experienced the following scenarios: The version requirements have already been finalized, development and testing are in full swing, and you are also involved in the testing of this version and the planning of the next version. Seeing that the version will be launched in a few days, the business lady is running He came over and said, "I have a requirement here, bulk sms service which is very important. Can you help me add it to this version and do it together?" The launch time has not changed, and a demand is temporarily added. At this time, should we do it or not? 1.
What are temporary needs First of all, we have to clarify what is a temporary demand. Generally speaking, when the functional requirements of the original version have been finalized, the temporarily added requirements can be collectively referred to as bulk sms service temporary requirements. According to the different problems solved by these requirements, we can divide them into the following three categories: 1. Defective requirements: requirements in order to solve existing functional defects Our common requirement to solve system bugs is a defect requirement. But defective requirements are not the same as system bugs, but bugs at the requirement level . bulk sms service For example, the product provides the demand for nicknames, but does not stipulate the number of characters for the nicknames, which leads to the appearance of nicknames with super long characters, which is a defect in the demand.
The characteristics of this type of demand are: it has a significant impact on the existing business and is generally urgent. Therefore, such needs must be decided quickly. In order to facilitate understanding, the processing flow of defect requirements is sorted out as bulk sms service follows: The first step is to determine whether it will affect the release time of the version . If not, add this temporary requirement to the version, and it can be completed according to the original plan; otherwise, proceed to the next step. The second step is to determine whether there is a plan B that meets the bulk sms service requirements and will not affect the version plan. If there is and accept the B plan, then use the B plan; otherwise, proceed to the next step. The third step is to determine whether additional manpower/foreign aid can be added