Background
It is well known in the Toyota lean production, the core ideas include respect for human beings, eliminate waste, continuous improvement, the only way to maintain healthy functioning of enterprises, competitiveness will increase. And specific waste scenarios are summarized as "Made in excess, wait, handling, storage, processing, additional action, defective," has seven later added waste "management" of.
The author's performance improvement team, has been committed to Lean practices, from the point of view of cost efficiency, to enhance the effectiveness of software development to praise, to cope with the uncertainty of the times full of change impact. And that time of software development, from the perspective of process management, have "item" system popular among the team and continue to play a role, but from the perspective of engineering practice, although there are some infrastructure sectors, but only for the department service, overall in its infancy, there is a need to separate each of the main island connected in series, synergy value.
First, the status of the engineering practice
1.1 Technical debt
has praised as a start-up company, the first task is to survive in the competitive market, so in terms of technical precipitation, in a passive state for a certain period, coerced by the business bolted forward, is understandable, but must be experienced. But it can be expected that, over time, will accumulate a lot of technical debt, and will rise along with the complexity of the system, technical debt brought about by the rapid increase in R & D costs, until it becomes a pile shunned legacy Features.
From the perspective of Lean waste treatment technology is a kind of debt "additional action", it is a time in a not open around the R & D work, but in addition to spend a lot of manpower and time outside, does not create any value. We need to grasp the current number of technical debt, how to risk, how to deal with costs, in order of how much scope there is a reasonable and controllable. The following diagram is like DevOps in the construction process, an application obtained by scanning the code quality SonarQube static situation:
the impact of code changes 1.2
We often say: enters garbage, the output must be the rubbish (garbage in, garbage out). Do incremental development in the full technical debt and there is no protection code, like walking in the swamp, at any time there will be an accident. There may be code comments to help you understand the historical legacy business, but after more than supplement the hands of this code, the comment may be more verbose than code.
Work in this technological environment, it is prone to "defective", perhaps most problems can be put out in front of the line, but the flow line is likely to be a failure, and even become a future source of failure of the new code. The figure is for sermons DevOps "Phoenix Project" on the cover, so it presents some startling sight:
1.3 integration period
due to the R & D is a need for multi-party co-operation, and outputs the results of the parties is very clear: meet product features and quality expected code. About the results, in the development of pre-preparation, the parties to task decomposition by product function point target, it has been preordained. Since it is for the common goal of product, we go hand in hand, we were developed after production, the results will inevitably want to join together to produce a synergistic value of innovation. We usually criticized one of the most fatal flaw waterfall project model is that everyone develop quality are very high, but it is a mess when large-scale integration.
Therefore, researchers need to continue to try to integrate upstream and downstream, but also involves the integration compile and run the code, each integration is a wait, the project is also an ordeal, the time schedule is difficult to control, so lean that this is a kind of "waiting" wasted. Although we defined 'interfaces in advance "of the project management process in action, but in the actual encoding process, or will produce along with further understanding and clarification of demand, the researchers readily change the interface (but not on the downstream timely notification) of Happening. The following diagram is like DevOps platform applications on a case of aging:
Second, the effectiveness of the improved entry point
2.1 Import idea
All beginnings are hard. Although R & D team in the industry flourishing, "the development of operation and maintenance" has a certain knowledge, but focus on the use of tools, the purpose of this is to enhance the team's productivity. And after a series of attempts, we have been vaguely aware that "continuous integration" is to enhance the efficiency of research and development of high leverage point frequently delivered under pressure, and "single standardized test" and "environmental governance" is the protection of the premise of continuous integration , so performance improvement teams to join R & D team, quality assurance team and the operation and maintenance team to discuss the decision, these two tasks in-depth Publicizing. Consideration path is as follows:
1) if there is sufficient coverage with high quality single probe embodiment, can protect the business logic code, in case no additional testing costs, and can withstand any changes and adjustments;
2) if there is a healthy and stable test environment, the code will be able to after being submitted to the code repository, automatically trigger the execution of static code checking and single-use test cases, rapid and healthy verify the correctness of the new code, and can withstand frequent deliveries of quality assurance tests;
3 ) based on a single measurement by cases, the integrated use cases may be combined to form according to the business scene, in a healthy and stable testing environment, unattended continuous integration, automatically triggers package and deploy, and validate business logic, or even published on-line (common practice is released to advance environment), lower release cycle, increase the frequency of publication.
2.2 voluntary pilot
if you can find a team willing to participate in the pilot, let beneficiaries to share the results of improvements to other colleagues, is a good practice, this theory is more convincing than preaching we just passed. That time, there is praise performance improvement teams in the research process, relatively smooth communication with the U team, the technical team leader also very much agree with agile development methods based on frequent deliveries, which we find a breakthrough for the promotion of single measurement practices.
In addition, S Group G Group C and Z Jun Jun is the R & D personnel in the geek users to actively participate and precipitation best practices on how to write a single test, and very happy to share my colleagues. Thus, we get the chance, on the basis of a single test to promote the need to achieve their goals and expectations, based on the continuous organized several field technology sharing, the remaining technicians quickly mastered the method of preparation of a single measure, a single measure to promote rapid improvements and implemented. The figure is taken to share content material:
2.3 assists flanking
From development to on-line throughout the process, there are three types of roles: research and development, quality assurance, operation and maintenance. As the industry continues to mature in the field of automated testing and automated maintenance of transport, to praise the quality assurance and operations teams aware of its value, it is in the field of research and practice in DevOps has been at the forefront of the industry, and promote the process of landing long-term positive status, acts as a role of vanguard. On the one hand, the quality assurance team and development agreement must ensure that a single test coverage, or to refuse to return to mention when measured measured; on the other hand, operation and maintenance strengthen environmental governance, standardized "Dev Environment", "QA environment" "Pre Environment" the ability to use gestures and table. Multi-joint force, and improve the technical team to enhance the measurement capability of a single initiative. The figure is the growth of a single line of business application test coverage standards:
2.4 tooling support
in addition to the irregularities in the management tool also provides a lot of supporting functions. There praise of the development process "minimum performance platform" managed with self-development, in order to facilitate the use of developers, it increased with DevOps platforms linked fast track, can be a key to generate a complete environment that supports both sides of the system state synchronization, automation the results fails to reach the threshold limits into the next part, and so on. The figure is sustained delivery of pipelining functions locally like DevOps platforms:
2.5 atmosphere to build
to help the technical team to enhance the perception of engineering practice, performance improvement teams also do a lot of fun and interesting surrounding:
1) CI (the Continue Intergrate, continuous integration ) indicator. Raspberry and we send a warning LED lamp set up means connected via a network to send raspberry DevOps internet, when the subscription application on DevOps fail platform (typically unit test fails, performing integration tests fail, the coverage the next scene is not compliance, etc.), corresponding to the raspberry Pi will receive information, and trigger the red light flashes to alert administrators concerned about the application, urged the code in this team submitter repair as soon as possible. Results as shown:
Episode: occasionally develop a colleague back home in the evening of a corporate VPN remote office, site office at this time the lights had closed, if the colleague code into the repository, triggering DevOps use cases when a single measure fails, you will see strange picture in the following figure (once almost frightened our HR sister):
2) CI big screen. The company has several sets of idle touch screen, used to be in the mall when used as an advertising push, and we are out to take advantage of the old material, even on the corporate network, placed in the office area, used to display the major application platform in DevOps on the state. On the one hand, to have access to applications developers DevOps platforms, it is a reminder and compete with each other; on the other hand, developers who have not yet contacted the DevOps, also played an advertising effect of the demonstration. Below is data showing big screen:
Episode: Because there is often a company's customers to access, so passing through, but also occasionally be stopped to watch, Administration later put it simply positioned to lead customers to visit a necessary " one of attractions "a. The figure is to praise the staff at the big-screen presentation content to show to customers:
Summary
As previously mentioned, there is praise team performance improvement is not a person in combat, quality assurance teams and operations teams are their areas of expertise, playing an active role in promoting engineering practice floor at the same time, the development team is also working to break through their own comfort zone. As the saying goes:
the development of operation and maintenance center is tied to a single measure to protect protect my body.
Three sets of environmental governance, a red light illuminates win opportunity.
From the perspective of Lean, strengthen the ability of engineering practice, can reduce waste and greatly enhance the efficiency of research and development, and is worth the investment to be improved. The review has praised the landing process, on the one hand to do propaganda and ideas to import (it is best to use the power of benchmarking and the role of volunteers and pilot demonstration team), on the other hand be strengthened in the tool level, making it an inescapable function, and thus strengthen muscle memory, coupled with the practice of CI lights, big screen, so that the concept of implantable heart of R & D personnel, have a more sense of ritual spread. (Source: Chan has technical)
