At the beginning of the business, there may be an idea, after research and investigation, there is market feasibility, and then people start to start the business. At this time, it is usually done alone, and one or two people are responsible for everything, including product design, interactive prototyping, web art cutting, program development, and functional testing. At this time, there is basically no need for cooperation, the independent development mode is adopted, and you can save it yourself. However, there is also a risk that the hard disk is broken. You must know that the hard disk is the most fragile thing. I usually back up the hard disk regularly.
If you find that the entrepreneurial model is feasible, you need to hurry up to grab the market, and one or two people can’t complete many tasks, and you need more professional people to join in to create a product with good interaction, beautiful pages, and easy-to-use functions. At this time, there should generally be product managers, art design, program development, testing, and operation and maintenance. However, these roles do not mean that so many positions must be arranged, and they need to be set according to the company's specific situation.
With a little market opportunity, time is the most important. If the traditional planned development model is not suitable, agile development is relatively similar. It doesn't necessarily say what development model must be adopted, and this also depends on your own company. Our model should be a development model based on agile XX company like China's socialist society.
Well, there are positions available, how do we divide the labor and cooperate? At this time, because the product is evolved based on ideas, many things are uncertain, and a large and unchanging long-term plan and demand cannot be set. After all, it is impossible to require constant demand at this time, and we ourselves act as product managers. Not only the needs of the market and the boss, but also the needs of the product itself and function realization, and gradually turn a vague thing into a practical product prototype, and then form the final product. Combined with the characteristics of agile development, people-oriented, divide a large requirement into small requirements and assign them to suitable people for completion. The roles mentioned above do not necessarily require a specific person for each position, or one person can assume a role, or multiple people can assume a role. For example, our company temporarily does not have product managers, testing, operation and maintenance, program development is responsible for development, testing, operation and maintenance, and everyone involved in product design must participate. The overall product design is checked and tracked by one person, and each product is subdivided to be responsible for analysis and follow-up of its own product. It is equivalent to implementing a sentence, as if it came from a book "Everyone is a Product Manager" written by a product of Alibaba. If you don’t know your own product, you can’t play it, and you can’t operate it, what can you talk about to make users like it? Regardless of art, R&D, testing, operation and maintenance, you need to have a good understanding of the product. If you can, understand not just a small piece of the product you're making, but also the products of other colleagues. As the general gatekeeper of the product, the technical director needs to be familiar with each product so that he can follow up and design discussions. Therefore, no matter what work you do in R&D, art, testing, and operation and maintenance, you need to think about problems from a certain height. Since starting a business, you need to think from the perspective of starting a business. This will help your career development and make products.
After discussing with everyone according to a large demand, the technical director will gradually clarify the vague things to get a more clear approach and assign them to the right people. In this way, everyone leads their own needs and begins to analyze the specific implementation, and after getting a general idea, discuss with the technical director to determine the final specific implementation. You can participate in the analysis of the overall needs of the artist, so that it is easy to understand the entire demand, or you can design a good-looking and easy-to-use product interface after understanding that sentence. The detailed requirements and technical implementation are left to R&D to think and determine. After R&D has determined the implementation plan, discuss the interface implementation plan with the artist. At this time, the artist will know the realization function and interface plan of the small requirement. Then the artist designs the interface. If you have time, you can come up with a few more plans. You can use strokes in the sketch at the beginning, and you also need to communicate, discuss, and confirm. Finally, a user interface is selected, and the R&D starts to develop the program and cut the page for art. If the template and specifications of the art are basically determined, the work may not be too stressful, so it can meet the needs of several development. This determines the number of artists on a case-by-case basis.
At the beginning of research and development, you can make your own pages, first determine the dynamic tags, and then insert them according to the pages cut by the artist. Then develop the background logic, generally from the foreground to the background development and even db development, you need to understand a little bit, so as to ensure efficient development. If it is split horizontally, some people will develop services, some will develop dao, and some will develop jsp, which will increase unnecessary communication and waste time. If the later project is huge, it is recommended to add a professional front-end js development and back-end DBA. Research and develop your own business code to test the function, and the technical director of the test ok confirms and waits for the integration and continuous adjustment. At this time, the development is completed on its own machine, and it is not tested in the test environment to provide research and development speed and efficiency. Everyone knows that if it is developed in Java, the continuous reload of the deployed war will affect the work of others. If the project is relatively large, it will be slower to start. If it is in this machine, just modify the things in the class and jsp, etc., you can see the effect directly. Modifying class signatures and adding classes requires redeployment.
After everyone has developed their own modules, they focus on testing server integration testing. Here, a designated person can package and deploy, and everyone can test to find problems and modify them. Regarding the front end, the prototype interface is generally modified by itself, and the dynamic page is directly modified after being embedded in the dynamic page. The preview is on the integration server. Here, the preview can be integrated with the svn server. The front-end artist submits the jsp to the svn and it will take effect. He can also see the effect directly. The specific operation will be introduced later in the article. There was no problem in the final test. The boss confirmed that the external network server was released and the db was deployed. It is also easy to make mistakes here. If the publisher is not himself, it is easy to miss things, so it is best to provide a release list and modify it when you change anything other than the program before.
In the future, with the expansion of the project and the expansion of personnel, you need to use more modes and auxiliary tools to find a more suitable way for you. For example, page publishing tools (the front end can directly publish IDC), continuous integration (can automatically deploy testing and IDC), and so on. The most important thing in the project is the people. Different working modes are selected according to the people. Just like the CEO of Douban said, it doesn't matter what language tools and technologies are used. The most important thing is the people and the team. I believe that after everyone's running-in, every team that is superhuman (skills, communication, cooperation) is born in this way.
Original article, please indicate: Reprinted from Lanceyan
Link to this article: Talk about the working model of startup technology