Product Design Experience ()-resource wars and BRD

The product team has just gone through a war within the company, competing for resources from development engineers and test engineers next month.

 

Let me first explain why there has never been such a war before, because the company originally divided departments by product lines, so that for a product, there is its own PD, development and testing, etc, what needs to be done next month can be decided at the product manager level; but now the company has become a team by function, with a unified Product Operation Center (Pd and Operation) R & D center (all development engineers) and quality control center (all test engineers). In this way, all products will be ready for development and testing in the next month, however, resources are always seriously insufficient, so what we do in the end will have to be determined by the big boss of several centers. The decision-making basis of the Big Boss is the PK of various product managers, the description of their respective Product Development BRD (Business Requirement document), so the war broke out ,:)

 

So some time ago, everyone was preparing BRD together. This is our weapon. We need to try our best to illustrate the commercial value of what we are going to do in order to grab all kinds of resources, the company's resource requirements have already been several times that of existing resources ...... (It is generally measured by a simple estimation of "person-day". Some people say that a group of people is called group P for short, which means to win more ~ Person ~~ ~~~, Er, it's evil !)

 

Weapons mainly include the following parts: Project Overview, project background, and Business Value Analysis (focus! The big boss is most interested in, be sure to talk about it on the point), Function Requirement Description, other requirements, resource evaluation (Focus 2! Big bosses should look at the cost), risks and countermeasures.

 

Of course, the students will also make some technical things, such as selling flaws and intentionally adding things that let the boss cut down, something similar to the things in negotiation skills.

 

Finally, let's talk about the advantages and disadvantages of the two organizational structures. The departments divided by product line are advantageous to the product itself. The product manager can follow his own ideas and ensure resources, product Planning will not change passively. Its disadvantage is the advantages of dividing departments by function; functional departments are advantageous to sharing resources of the entire company, ensure that all resources are used on products that are most meaningful to the company. In addition, it can expand the Catfish Effect of resource wars from within the product to the company level, making PD and product managers even more crazy to think about the development of products ......

 

Record the missing ones: 1. my understanding of the changes in the two organizational structures is an inevitable process of the company's natural development. As the number of products increases, the company has become more and more local optimal resources, they are more and more likely to complement each other. At this time, the benefits of global optimization become more and more obvious, so they can get through. 2. The product team has the advantage of smooth communication. Single-line leaders are responsible to the product manager.