Forum Posts

akter rojoni
Aug 02, 2022
In Welcome to the Forum
In the process of making products, we often encounter urgent iterative requirements, which require us to complete them in a very short period of time. And if the email list time left for requirement design is shorter, the less time is left for us to think in the process, which means that the functions we make are more prone to defects. In order to avoid defects after the function is launched, we often improve the quality of requirements by working overtime and delaying the delivery of requirements. But the problem is that when the launch time point has been determined, this method will squeeze the cycle of R&D, testing, and acceptance, and will also increase the probability of defects after launching. The quality of the requirements will affect the effect after the launch, and the time-consuming of the requirements will affect the R&D cycle. We seem to have encountered a difficult problem. If you think about it carefully, you can see that if you want to reduce the probability of defects after going online, you must find ways to improve the quality of requirements and reduce the time-consuming of demand output, that is, to improve the efficiency of demand output and work efficiency, and the above dilemma will also be Solved. Everyone understands the truth, but it is not easy to improve efficiency, because the output of product requirements is a complex process. Let's split this process, and we will find that it usually includes requirements research, requirements analysis, defining the scope of requirements, flowchart design, prototyping, writing requirements documents, and requirements review. If we find out which work content has a large room for optimization, and think about a better way to do this, we may find the answer to improve efficiency. According to my own experience in product requirements work, I have summarized the following methods for different work contents. 2. Methods 1. Method 1: Do a good job in demand research Many product people, including myself, often overlooked requirements research when they first started working on requirements, and spent a lot of time on prototyping and requirements documentation. There is a high probability that there will be such a situation that after the requirement is completed, because the demander is not satisfied, it will be repeatedly modified. We know that when the requirements have been output, it will cost us a lot of time to modify the process, prototype, and documentation. When we spent 0.5 days of research, we completed the requirement design in only 3 days, which seemed to be very efficient. As a result, because the plan was rejected, there was an extra 3 days for repeated revisions, so that the original 4-5 days could be completed. It took a total of 6.5 days before and after. Also, the longer the cycle and the more complex the requirements, the more time will be lost. When I just graduated and made products, I often encountered the above situation. Later, after reflection and experimentation, I came up with a rule: It is to spend as much time as possible in the stage of demand research and demand confirmation. It is best to fully understand and understand the demands of the demand side before starting to make demand plans. According to my past experience, generally at least 40% of the time is required to investigate and confirm with the requester, the user of the function, and other stakeholders, and sometimes even 60% of the time at this stage.
How to improve the efficiency of demand output? content media
0
0
2

akter rojoni

More actions