【DEVOPS】Technical Team Role Division

Our ultimate goal is to create an "ALL IN IDE" R&D experience. The business R&D team should not be aware of the entire process, and the fewer details they need to know, the better.

1 Introduction

Bottom-up DevOps promotion, in addition to the bad experience step by step, the biggest difficulty is the formation of consensus.

Lack of administrative support in the organizational structure, lack of ability and awareness of personnel in the team, multi-responsibilities and many other reasons lead to the fact that in the actual promotion process, the progress of DevOps belongs to you, and it takes a step forward; if you don’t pay attention, it takes half a step back. In this back-and-forth see-saw, many people were disheartened.

This article adheres to the ideological principle of "it is better to lure it with profit than to understand it with reason", and draws a "cake" for the R&D team, hoping that there will be fewer obstacles and more support on the road to advancement in the future.

2. Role division

On the improved route of DevOps advancement, we recommend the use of the "surgical team" teamwork model.

"The Mythical Man-Month" suggested an organizational method called "surgical team". Just like a surgical operation, there is a chief surgeon, and a software project should also have a chief programmer, and everyone else supports him. In this way, the product integrity of a few minds is obtained, while the overall productivity of many assisting personnel is obtained, and the communication workload is drastically reduced.

Role	number of people	responsibility
lead mover	1-2 people	a) Design the entire process. b) Build the most basic implementation - realize the start-up operation of the entire process. c) In the initial stage, the actual business R&D team needs to be involved to really promote the process, and find and train successors within the team. d) Continuously accumulate, optimize, maintain and iterate the entire process in practice. e) Training, publicity, and promotion of the entire process.
core backbone	Subjective will take precedence	a) Master the implementation of the entire devops process and be able to solve more than 90% of the expansion requirements. b) Feedback upwards to actually promote the problems collected during the devops process, as well as the corresponding solutions. c) Answer the business R&D team's questions about the devops process. d) Provide corresponding solutions according to the customized needs of the business team. e) Publicize and promote the entire process.
Team Leader (Business R&D Team)		a) Know the relevant extension points and implementation methods in the devops process. You can use these extension points to realize the custom requirements of your own projects. b) Respond upward to problems in the devops process.
Team Member (Business R&D Team)		a) Know the basic manual operations in the prescribed devops operation process and use them skillfully. For example: keywords supported in GIT commit logs. Product download address link address, directory structure. b) Other information that end users need to know.

3. Ultimate goal

Our ultimate goal is to create an "ALL IN ONE" (one IDE to solve all problems) R&D experience. The business R&D team should not be aware of the entire process, and the fewer details they need to know, the better. They should not know :

What tool is the product compiled and packaged by?
What tools drive the entire process?
…？

What the business R&D team (especially front-line business R&D personnel) needs to do:

Understand the requirements, convert the needs into code,
Fix code based on process or tester feedback.
Submit your code in the required format.
Gone.