Top 5 Goals related to Devops

5 Goals related to Devops 

Devops


If you want to get your own definition, the research is likely to start by asking Google, "is DevOps?" Of course, Wikipedia is one of the first results, so that's where I'll start. The first Wikipedia article describes Devops "software development software that focuses on communication, collaboration and interaction between software development and information technology professionals." Well, that is a beautiful description, but it is still white. I think Devo can only be described as how the operators work with the engineers to deal with them quickly and again.

Devops goals

The guides are wonderful things, allow us to do repeat things, get to know our mistakes and create good habits. In the last few years, we have discovered many Devops goals, which we constantly look at, and here are:
  • Start with needs
  • Delete technical and unpaid business loans
  • Fast / fast / secure
  • Look "outside"
  • Measure the value of the environment
1) start with needs

It was a time when we are talking to people about current and future cadences releasing the meaning, "So if I would release 4 each month, how would life be if I could do 4 weeks?" Now, we are focusing on providing a coherent and capable software always able to release, so that when a new feature is ready to be activated, it can be activated, whatever the organization should be circular in this publication. . This approach was introduced in the country of information DevOps 2014 Puppet Lab and you can read more about how one of our customers, Hiscox, CD line cultural and allow to throw 19 spells in the first week after the release, here a. Implementing management management tools means that organizations must:
  • Start when comfortable
  • Predictable, frequent and quick
  • Return (or perform) if it fails to successfully complete the final status immediately
  • Ensure complete compliance checks
  • the inclusion of NFRs on process and security
  •  Let's go to a holiday - the system becomes so breathing

2) Delete technical and unpaid business loans

many readers from this blog read the Phoenix project, a story about DevOps that focuses on the vision of barriers and planned business management. Debt Technical is often the main cause of the work and unplanned, the structure or system error, which requires special attention to determine the funds allocated to work on the function or Refactoring code of a new one that is outside the original between project and budget constraints. The first step in understanding the impact of the technical part of the credit union is unplanned for measurement (the basin is the basic idea of ​​DevOps): Many today do, but this is not difficult to do. Most organizations have a system of hours' records (if already, you should) accept and add the code for unexpected work (or refactoring) to prepare stations and to compare the country in the future. The debate is possible to completely abolish the technical debt, especially when we do it, and often we work in the Advanced Code of Good Dignity. We may want a code that is very good or right, but time and budget are limited, as it is necessary to create enough creativity for success or competition. However, we can all do this to add quality within the code, it is useful; Here we are talking about changing the left side. We know that the previous investigation of the cycle means that the errors are faster and easier to repair, and DevOps provides a platform for its operation in the early stages of the development cycle and the conditions for the non-functional first-stage design.And the terms are really important: many organizations are concerned about the extent of the errors and have reached a level that will benefit from interaction. After monitoring the process often find that there are difficulties in accessing the conditions for improvement here, it is weighed; 

The main cause of the error is the poor state.This does not mean that automated tests are not relevant; it is necessary to improve the development of software and to create and maintain quality CDs and CDs: the most important is to ensure the conditions and interactions of the test process ... and beyond. The device can really help you.

3) confidential / immediate / safe mistakes

Two key traditional ideas in DevOps are related to crime and mistakes:
The mistake is often unhealthy and unhealthy. Many organizations have "war rooms" (sometimes in places of refuge) that are under control or fail to solve the system's error and can spend a lot of time and create bad feelings, such as individuals and groups ...The phrase is often used when we talk about cultures DevOps is "the feeling that dancing is all about failure": although it can look bad on the face (it sounds dangerous), what we are really doing is to create an environment in which people feel with power and security for innovation; they are not afraid to try new things. This requires processes and systems that eliminate or minimize the greatest possible risk by doing things like:
  • Automated test
  • Implementation of the proposal
  • You can immediately redistribute the last known good country
  • Have an early warning system for error
  • Look "outside"
This means thinking about everything from the perspective of its users. I mean it really (many people have done this for a long time, but it's difficult when you're in the company to look at OUTSIDE). Not only if you acquire and define priority requirements, and develop and test them, but you are following your full experience. Again, some of the latest capabilities management tools are very powerful and can provide information not only on response times on various mobile browsers in different geographic areas, but also at the level of business transactions where people leave, for example, web applications or shopping carts.

A / B tests are well-established in the marketing world: sending e-mails in two different formats and analyzing results helps salespeople make better choices. However, we can do more than to check whether the red button is better than the blue button on the job site: we can (if we have integrated our requirements at the beginning) and start iteratively) measure the effect and take-over (or not) a new feature; how many of our users are doing what we just did.

More detailed integration and analysis also provide an analysis of the opinions. Some of the companies we work with, for example, in the insurance industry, are worried because their traditional businesses consume "new customers"; Highlights Classic sales now offer insurance (see brochures next time you are at the box office in a food store) and have a real advantage over traditional insurance, as data has been collected in a more detailed customer for a while and can produce more specific offers By exploiting social networks and collecting information about the feel of the brand, the product and the specific characteristics of the company can increase their competitiveness.

5) Measure the property value

The passage through iterative and agile methodology enables us to trace the characteristics from the beginning to the end and measure the travel costs throughout the process. Characteristics must be determined by end-users and operations and operational efficiency is necessary in order to be able to determine the characteristics with respect to the expected value for the end-user and thus business, and also inform the actual value (or not) received over time. Incorporating the pipeline production equipment and being an effective application control tool can detect changes at the transactional level is essential to inform interested parties about the impact of this new part of the code that has been put into production. ..



Comments

Popular posts from this blog

Introduction to Ansible - DevOps in 2018

Important Topic of Terminology in DevOps

How to implement Containers to streamline your DevOps Workflow -2018