当前位置:网站首页>Understanding Devops from the perspective of decision makers

Understanding Devops from the perspective of decision makers

2022-06-24 03:06:00 Trespass

In the last two articles , We are from 【 staff 】 and 【Leader】 From the perspective of DevOps.

If you are a decision maker , How to understand DevOps?

review

role

understand

staff

According to a rule , Holding a series of tools , Follow a process to complete the work . Most employees don't go 【 perception 】 perhaps 【 question 】 Processes or tools .

Leader

The rule maker , Implementer , According to the situation of the team , Appoint , change , Evaluation rules .Leader Need basis CAMS And the actual situation of the team , Build a team culture , automation , Evaluation system , Sharing system .

Agile,DevOps It's just a way

Don't have this misunderstanding : Do not do DevOps Not competitive , Did DevOps It must be competitive . for instance , If it's a 3~5 People's start-up team ,DevOps For they , It won't help directly , We should focus more on expanding our business , Grinding products .

In the previous article , We have been discussing Agile,DevOps These concepts , From the perspective of decision makers , These are just promotions 【 Enterprise competitiveness 】 It's just one way .

Any enterprise can have a better way to meet its own situation , promote 【 Enterprise competitiveness 】.

DevOps What can be brought to the enterprise ?

As a decision maker , Need to know DevOps What can it bring to the enterprise , Can't bring anything .

Puppet take DevOps The benefits can be summarized as follows 4 class , Let's put this 4 Class is linked to the core elements of the enterprise .

From that ,DevOps Not by itself 【 Direct promotion 】 The value of a business or a product ,DevOps What promotes is the production efficiency of the enterprise , So as to enhance the competitiveness of enterprises .

DevOps It's like Europe's advanced 【 Football youth training system 】, Introduce this system , Can't let us 【 immediately 】 Enter the World Cup , However , This is becoming 【 Football power 】 Necessary conditions .

If you want to introduce , How to do it ?

If you want to pass DevOps promote 【 Enterprise competitiveness 】, Recommend the decision maker to make decisions in the following order .

  • Judge the timing
  • Find out the problem , Select the implementation sequence
  • Top down promotion
  • Providing resources , Adjust architecture
  • Evaluate the results , Give affirmation

Judge the timing - Is it time ?

Decide whether to introduce DevOps, It can be downloaded from 【 external 】 and 【 Inside 】 Two considerations .

The external environment

DevOps The ecological development of is the external environment , First look at it. DevOps External conditions .

Current research results ,DevOps Our external environment is quite mature .

overall , Population , policy , Maturity, etc. are conducive to DevOps Promotion of . In our view , Population driven is the focus .

To put it bluntly , The competition for talents will become more and more fierce .

1. Population driven - From demographic dividend to engineer Hongli

The population of the software industry continues to grow , The domestic population is gradually showing a downward trend , The demographic dividend of the software industry is gradually disappearing .

end 2030 year , Developers all over the world , It is expected to break through 4500 ten thousand . come from :Software Developer statistics 2021

end 2025 year , The population of domestic software industry is expected to exceed 900 ten thousand . come from : White paper on talents in key software areas

According to the statistics of the National Bureau of population statistics , China is now facing the trend of population aging . come from : China's population report 2020

2. Industry driven - The software industry continues to grow

The software industry will continue to grow , Will drive DevOps Grow together .

come from : IResearch :2020 In China DevOps Applied Development Research —— Irecloud native series reports ( Two )

3. Technology driven – Cloud native , Container technology promotion

With the container and cloud reach ,DevOps Development has also been gradually developed . come from : IResearch :2020 In China DevOps Applied Development Research —— Irecloud native series reports ( Two )

4. Policy driven – Establishment of domestic industry standards

2018 year 4 month , DevOps Standard projects “ R & D operation integration capability maturity model ” In China Communications Standardization Association, the project was successfully established . come from : IResearch :2020 In China DevOps Applied Development Research —— Irecloud native series reports ( Two )

5. Ecological drive – The open source community

The continuous enrichment and development of open source ecology provides diversified tool choices for development and operation engineers , Build up DevOps Rich resource pool . come from : IResearch :2020 In China DevOps Applied Development Research —— Irecloud native series reports ( Two )

Internal environment

Judgment of internal environment , Decision makers can consider the following aspects , If something has already happened inside the enterprise 1/3 Above situation , Decision makers should start thinking about DevOps 了 .

personnel

  • Poor recruitment results .
  • Employees leave frequently , The ability of new and old employees is stagnant .
  • Employees work overtime frequently , And the business progress is poor .
  • There is an infidelity between teams , Compete with each other , Waste human resources .
  • The promotion proportion of internal backbone is low .

product

  • Product innovation stagnates , Business expansion is slow .
  • Lack of product automation pipeline , Frequent accidents .
  • There is internal product homogenization .
  • Product costs remain high .

assessment

  • Internal technology / Lack of business sharing mechanism .
  • The internal evaluation mechanism of the enterprise is chaotic .

Culture

  • Corporate culture cannot be implemented in work .

Find out the problem , Select the implementation sequence

With the judgment of the internal environment , There is a problem , however , Solving single point problems is never what decision makers want to see .

also , Which problem to solve first , It all looks like 【 correct 】 Of , It's hard to judge .

We can start from the enterprise / Starting from the core of the product , Select the implementation sequence .

such as , What enterprises need is to improve the efficiency of product iteration , Then the preferred order should be 【 automation 】,【 assessment 】 System construction .

Top down promotion - decision DevOps Success or failure

We identified the problem point , Implementation sequence , Next, be sure to go from top to bottom 【 strong 】 Extension . This kind of project , It's hard for employees to realize its value .

The result will be 【 Do things carelessly 】. because , Employees find it difficult to get 【 Promotion 】 The opportunity of .

In the process of advancement , There will also be all kinds of resistance , There is only one clear 【 Imperial edict 】 So that the promotion can proceed smoothly .

Amazon stay 2002 In, the microservice architecture was enforced , Is the CEO Jeff Bezos Sent an email to all the staff . The most important sentence is :Anyone who doesn’t do this will be fired.The Bezos API Mandate: Amazon’s Manifesto For Externalization

Providing resources , Adjust architecture

Providing resources

With a plan , Providing resources is certainly essential . at present , There are many open sources at home and abroad & paid Agile,DevOps Related products and solutions . We'll introduce... In a later article .

here , We only give selection suggestions ( Of course , If it is for the purpose of pulling investment, etc DevOps product , Just say something else ).

  • Don't buy all the functions of the one-stop platform at one go , It will not be on .
  • Select cloud native ,K8S Native products .
  • Try to choose products with open source foundation .
  • Don't let the introduced DevOps Products are stuck in the neck of technology upgrading .
  • product + Instructions + Training is a must .
  • Listen to employee experience and word of mouth before deciding .

Adjust architecture

The next work is to adjust the corresponding architecture . Not familiar with DevOps For the team , There must be several roles in the company .

If there are no following roles in the enterprise , Almost impossible to promote DevOps, Rely only on the products of third-party companies 【 It must not reach 】 Purpose .

  • DevOps Communicator team : There needs to be a team or individual to constantly innovate the business , Set a benchmark , Can be imitated .
  • Automation architect : According to business attributes , The process can be , People who design automated architectures, such as testing / The team .
  • Research and development + Test Engineer : Every R & D / Testing should be gradually transformed .
  • quality + Safety assessment team : Preferably composed of R & D personnel .
  • Utility evaluation team : New technology , Evaluators of new tools .

Evaluate the results , Give affirmation

according to Atlassian The evaluation of , Overseas enterprises accept DevOps The period of is 1 year , therefore , Decision makers should have psychological expectations of the time cycle .

Each team's Leader It needs to be reported according to the actual data DevOps The process of . Take a few examples :

  • Percentage of deployment build automation
  • Percentage of test automation
  • Time cost (Blocking time & Waiting time) percentage
  • Product user feedback

Besides , It's important , To give 【 do DevOps】 The team / Employee recognition , otherwise , No one will be willing to do 【 The boss doesn't approve 】 Things about .

summary

From a macro perspective, we analyze the decision-makers in DevOps Role in promotion .

Review our previous two articles , staff ,Leader, Decision makers should be DevOps Joint investment in , otherwise , It will only be a face project .

role

understand

Decision makers

The pilot of the direction , According to the situation of the enterprise , Determine the implementation sequence , Providing resources , Adjust architecture , Give evaluation and affirmation .

Leader

The rule maker , Implementer , According to the situation of the team , Appoint , change , Evaluation rules .Leader Need basis CAMS And the actual situation of the team , Build a team culture , automation , Evaluation system , Sharing system .

staff

According to a rule , Holding a series of tools , Follow a process to complete the work , Actively accept change , Improve personal ability .

We'll see that in a later article , In depth introduction DevOps Details in .

原网站

版权声明
本文为[Trespass ]所创,转载请带上原文链接,感谢
https://yzsam.com/2021/10/20211019035502530U.html

随机推荐