Shulou(Shulou.com)06/02 Report--

Hello, everyone. I'm Heng Shao, product manager of Huawei Cloud:

As an evangelist and product manager, it is normal to travel to contact customers, often communicate with Huawei Cloud customers, preach, technical salon, but offline communication, cover a small number of users.

I hope to use the online platform to continuously exchange Huawei's thoughts and considerations on the improvement of R & D efficiency with users.

Because there is no silver bullet in the software, exploration is always on the way.

-practical information segmentation line-

How to carry out agile, DevOps, and other R & D changes

Agile, Lean Kanban, DevOps. Technology is developing, and so are the processes, methods, concepts and tools of research and development. I believe that new ideas and methods of software research and development will continue to emerge in the future, because the complex monster of software is still a long way from conquest. :)

When I communicate with many enterprises, I always mention the most important point: why should we treat new R & D methods such as Agile and DevOps as change? What is the most difficult thing about reform or change, and the reason for the failure of many changes is actually the same: get rid of the benefits. It should be easy to understand if you are familiar with China's reforms in recent years.

Agile, DevOps, and even the new configuration management tool Git, for many existing enterprises are a huge transformation, many enterprises in the original model has formed their own organization, process, culture and tool system, the interests of all parties have been solidified.

We cite a classic picture of DevOps (Patrick Dubois), such as the following picture (Wall of Confusion), to feel how change is touched and there is an "interest". Product and development students want to go online as soon as possible, which is the natural demand of products and development, while operation and maintenance students want as few changes as possible, because it is their natural duty to ensure the stability of the existing network. The main conflicts between developers and operation and maintenance students:

Different worldviews: operation and maintenance staff require stability and reliability and believe that change is risky, while developers are encouraged to release new code frequently, believing that the persistence of the operation and maintenance department to the process hinders the speed of development.

There's nothing wrong with it on my machine! Developers often say this, but the operation and maintenance team does run into trouble because there are differences in script, configuration, process and environment between development and operation and maintenance

Communication barriers: development and operations teams are usually located in different departments of the company organization, usually with different managers, usually distrustful relationships, and usually work in different locations

This natural conflict of interest is the biggest challenge to all R & D changes and the biggest factor leading to failure. What should we do? Let's listen to Hengliao decompose next time.

Related articles:

[product Manager-001 of the fully connected Series] what on earth is Epic/Feature/Story/Task/Bug?

[product Manager-003 of fully connected Series] Huawei Agile / DevOps practice bit by bit (1) _ how to hold a good standing meeting

I will regularly interact with you in Huawei Cloud Community. Interested friends are welcome to post to the product section I am responsible for: http://t.cn/EZBrJC3

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.