Shulou(Shulou.com)06/03 Report--

Why is the product manager requirement project delayed? The actual completion time of the project is later than the expected completion time. There are many reasons for the delay. It may be that the project is delayed due to unclear requirements or changes in requirements, and the R & D technology level. The same requirements, different technicians need different time. In order to let everyone know more about the product manager, Xiaobian summarized the following contents for everyone, and looked down together.

Most delays directly affect the expected time on the actual completion time, but the product manager does not have the ability to predict the time, especially some complex requirements cannot be predicted, resulting in unreasonable expected time.

Different technicians need different time for the same requirements. Even if the requirements are the same and the developers are the same, but the code environment is different, different business environments will lead to deviations in the actual time required. The inability of product managers to predict development time is not a simple "technical ignorance" problem, but an objective phenomenon, not most of the predictions put forward by actual operators are inaccurate. Product managers have this illusion.

The expected time is unreasonable. The expected time directly affects the actual completion time. The feedback cycle is too long. Only when it is close to the launch can you get a feedback of "will be postponed". It is extremely passive. It is too late to make adjustments. You can only postpone it.

Predicting time allows you to subtract requirements before development to simplify complex logic, eliminate unnecessary features, and lower the priority of unimportant features. Minimize the risk of delays. The core of the product manager's solution to the delay problem is not overtime, not to change development, but to seek a "forecast time", how long it will take to complete.

Predicted time can only be provided by R & D, that is, R & D estimated time, actual operation of R & D provided time prediction can be trusted, everyone's technical experience is different, even his leader, auxiliary provided estimated time can only be used as a reference.

Some technology-driven teams have strong CTO, often making some time commitments, and the function is very simple and can be realized in one day. The technical staff of the team usually have a hard time. Maybe it takes only one day for the CTO to do it himself, but the actual operator is not the CTO, but other technical staff, which may take 2 days or even longer to complete.

The experience structure of each R & D personnel is different. Whether it can be realized or not is a matter of ability. Whether it can be completed quickly is a matter of experience. It takes some time to study the R & D of ability. It will go through the process from slow to fast. Introducing forecast time gives the team two possibilities, one that helps the product manager control delay risk and the other that helps the R & D team manage objectively.

Product managers are industry-specific, where requirements come from problems and solutions come from requirements. There are many factors for project delay. The inability of product managers to predict development time is not an objective phenomenon, not an actual operator's prediction, which is mostly inaccurate.

The above is the product manager requirements project why the details of the delay, after reading whether there is any harvest? If you want to know more, welcome to the industry information!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.