Recommend the best product development process in the Internet industry!

Take the chestnut of product development

1、 One boss management 5 A product manager

2、5 The product managers are divided into baidu Design product requirements , There is no intersection between requirements , Each person writes his own document , Design everyone's prototype , Whose needs are reasonable , Innovation , valuable , Whose needs have the highest priority , This boss Who says it is . Incomplete documentation 、 Unreasonable demands can't be started , The performance of the product manager is naturally low , They have a strong sense of competition with each other

3、 At this stage, there may already be 3 Requirements passed boss Audit , Get into UI design phase

4、 To this stage ,UI The design has been completed , open 3 A product review meeting , Assign tasks to three groups of people involved （ A person can be in multiple groups at the same time ）

5、3 Team building 3 Branches （ The branch name of the same requirement at the front and back ends should be exactly the same ）, Separate development , The product manager follows up in real time , Testers communicate in real time , Edge development , Edge change requirements 、 Edge test （ Tests on different branches ）

6、 If there are requirements, the development tests have been completed , This branch will merge into develop On the branch , Test in develop Test again on the branch , Make sure there is no bug, If there is bug, Reestablish the branch , After finishing , Test on the new branch , After the test, it will be merged into develop On the branch . No one is allowed develop Write any code on the , You can only create new branches to write code , And if you want to merge branches into develop On , Only after strict tests can it be combined , Programmers have no right to merge branches , Testing and operation and maintenance have

7、 At this time, there may be 2 New requirements passed boss Audit , and UI It has also been designed , Just at this time, a group of programmers' requirements have passed the test , Can directly respond to new needs

 

8、develop It is a very stable version , At any time from develop Branch into master Branch , Selling products on Monday , Just on Monday , If you want products on Friday, give them on Friday . Whether it's Monday's products or Friday's products , Are stable products , It's just that from Monday to Friday, a few hidden ones that were not found before have been repaired bug Maybe some new functions have been added . All on the market app It's all the same , Every time the user is reminded to install a new version, they will tell you , They fixed some bug, New features added

9、 The product manager is the soul of a company , Programmers are not

other ：

1、feature Branches and develop The branch runs in exactly the same environment , Actually in git Software seems ,feature and develop It's even , It's just an artificial belief develop More advanced . To guarantee feature towards develop Conflicts and overrides occur when merging code , You can merge the latest develop（ It is possible that other branches have gone to develop Merged code ） Merge into your own feature On the branch , If there is a conflict , After resolving the conflict, submit to your own branch , Then test , At this time, my own feature Branches are completely and up-to-date develop The branch code is the same , Just add your new functions , These functions need to be fully tested before they can be merged into develop On the branch .

2、 If a function is half done , The product manager feels that this function is unreasonable , You can just put this feature The branch is discarded , It doesn't affect at all develop Branch and product stability

3、feature Branches and develop The branch runs in exactly the same environment , If there is one bug stay develop Can reproduce , stay feature It cannot be reproduced on the , It is necessary to question the environmental problems of operation and maintenance . If there is one bug stay develop Can reproduce , stay feature It can also be reproduced on , But the previous tests were feature I didn't find , To develop I found that , It is necessary to question whether the test has been done carefully （ It is suggested to impose a direct fine ）

4、develop Branches and master On the branch bug It is the pot of testing and operation and maintenance （ It is suggested to impose a direct fine ）, If not bug The product itself is defective , That's the product manager's pot （ It is suggested to impose a direct fine ）. When this kind of problem occurs, the relevant personnel need to have a good talk with the programmer , Good attitude , Admit your mistakes with sincerity , Then the programmer fixes the problem , Otherwise, they will always make such mistakes ！

5、 Programmers often make mistakes , But our mistake should be feature Branches are found

6、 The scenario in this example is that there is only one product , Multiple product managers design different requirements for this product

7、 The solution I recommend can solve new needs and go online in time , There are stable versions in real time , There are many product managers , Developers also spend a lot of time , Each requirement has a different priority , The progress is different , The online sequence is also random

Reference link ：​ ​http://blog.jobbole.com/109466/​​

Reference link ：

Branch management and Automated Deployment Prototype map