Showing posts with label DevOps. Show all posts
Showing posts with label DevOps. Show all posts

Tuesday, 25 July 2017

The 2016 Report on the state of DevOps

The annual State of DevOps Report affirms as well as highlights the fact that acquiring higher Information Technology an organizational performance is a team effort that spans operations and development. Furthermore, it is also an investment that could deliver powerful returns. The report for this year reveals the way of boosting the whole product lifecycle. The lifecycle includes initial planning of a product, the quality and security assurance to customer feedback that hastens delivery and at the same time boosting customer feedback, speeds up delivery while boosting security, quality and business outcomes.

We have surveyed over 25,000 technical professionals over the past five years. This makes the State of DevOps Report the most extensive study on the DevOps topic nowadays. This year, we surveyed over 4,600 tech professionals worldwide. Again, we saw a boost in response from those who are working in DevOps department than last year. Unfortunately, there was just a slight increase in respondents who are female, and we have observed the same in other surveys. Admittedly, there is still a lot of work to be done to improve the inclusiveness and diversity in DevOps.

2016 Report on the state of DevOps

In the report of the State of DevOps, the following key findings are revealed:

1. Organizations that are high-performing are fiercely outperforming the lower-performing peers when it comes throughput. High performers deploy 200 times more often compared to lower performers, with 2,555 times quicker lead times. Moreover, they also continue to remarkably outdo low performers, with 24 times faster times of recovery and tree times lower rates of change failure.

2. High performers have better loyalty on their employees, as measured by eNPS or employee Net Promoter Score. Employees in high-performing firms recommend their company to a friend as a great work place, and 1.8 times more likely to recommend their team as a great working environment. Other studies showed that this is correlated with better business results.

3. Enhancing quality is everyone’s job. High performing companies spend 22 percent less time on rework and unplanned work. Thus, they’re able to spend 29 percent more time on new work, like for instance new code or features. They’re able to do this since they create quality into every step of the development process via using continuous delivery practices, rather than retrofitting quality at the end of the development cycle.

4. High performers spend 50 percent less time in remedying security concerns than low performers. Through better integration of information security objectives to day-to-day work, teams gain higher IT performance levels and create systems that are more secure.

5. Taking an experimental approach towards development of product. This could boost IT as well as organizational performance. The product development cycle begins long before a developer starts coding. The ability of the product team to decompose features and products into small batches, offer visibility into the workflow.

The survey analysis showcased that using continuous delivery practices as well as lean product management practices have predicted the extent to which people agreed with these statements and whether the culture of an organization was performance-oriented and generative. Moreover, the extent in the way people identified with their company predicted a performance-oriented and generative culture as well as predicted organizational performance as measured when it comes to market share, productivity and profitability. This should not surprise us. If the greatest asset of a company are the people, and most corporate leaders claim that they are, then having employees who identify strongly with the company must prove a competitive edge.

Netflix’s cloud architect by Adrian Cockcroft, was once asked by a senior leader in a Fortune 500 company where he got his wonderful people from. Cockcroft replied that ‘I hired them from you’, making our analysis clear. In the rapidly-moving and competitive world these days, the best thing to do for the products, company and people is to institute a culture of learning and experimentation and to also invest in the management and technical capacities which allow it.

Traditionally, IT has been considered as a cost center, which make it difficult to persuade management to invest in enhancements. Until recently, there has been little evidence that investments in IT could offer considerable returns. In past reports, we showed that there is a predictive relationship between organizational and IT performance, which prove that Information Technology could deliver true business value and provide different organizations a competitive advantage.

In the survey this year, we found that high-performing teams spend the least time on unplanned work and rework, approximately 21 percent. ROI calculations are based on the savings expected. This we expressed in monetary systems, but it is necessary to bear in mind that when it comes to saving employees time, you’re giving them back the space to experiment, think and to be innovative and creative.

Today, DevOps is no longer just a buzzword or a fad but an understood set of cultural patterns and practices. People turn to DevOps not only to improve their daily working time and spend quality time for the family, but also to boost the performance, revenues and profitability of their organizations as well. We have launched the State of DevOps and the DevOps survey report five years ago in order to discover just how the system’s tools, cultural values and practices have impacted IT teams and the companies that they serve. This year, the data gathered were wider in range and more deeply analyzed. We hope that the analysis, findings and guidance in this report helps in the better understanding of the potential impact of DevOps to any organization.

Thursday, 6 July 2017

The DevOps thing

DevOps is a movement that stops the waste of money and time to start delivering great software and building lasting systems. DevOps believe that there’s a better way of creating teams and software that can solve issues of a system.


THE DEVOPS MOVEMENT

DevOps is a movement that stops wasting time, money to begin delivering great software and creating lasting systems. The movement is created around a group of people who believe that the app of a combination of the right technology and attitude could revolutionize the software development and delivery environment. The movement is bold enough to believe that there is a better way of building teams and software that could solve system problems.

The DevOps movement is characterized by people who possess a multidisciplinary skill set, persons who are comfortable with configuration and infrastructure, but at the same time happy to roll up their sleeves, debug, write tests and ship features. These are people who make connections since they could, because they have feet in numerous camps, they could be peace makers, ambassadors, facilitators, and communicators. The point of the movement is to encourage people, compare ideas, train, recruiting and popularizing this method of doing IT.


DevOps

The DevOps movement is attempting to encourage development of understanding the domain which the software is written, communication skills and crucially, a passion and sensitivity for the underlying business and for ensuring that it would succeed. Born of the need to boost IT service delivery agility, the movement puts emphasis on collaboration, communication and integration between software developers and Information Technology operations. DevOps recognizes the interdependence of IT operations and software development and helps a business create software and IT services faster, with frequent iterations.

Organizations that integrate DevOps practices get more done, simple and plain. They deploy code up to thirty times more often than the competition. Collaboration across the various roles deliver a lot of benefits.

TECHNICAL BENEFITS OF DEVOPS
  1. Less complex issue to fix
  2. Continuous software delivery
  3. Faster solution to problems
BUSINESS BENEFITS OF DEVOPS

  1. More stable operating systems
  2. Faster features delivery
  3. More time available for adding value
THE NEW WORLD OF DEVOPS

DevOps is not just another Information Technology buzzword. It is here to stay. A big majority of businesses either have already implemented DevOps practices or planning to implement them. It is characterized by operations staff that make use of a lot of the same techniques as developers for their systems work. The idea is that rather than avoiding each other in the work place, the development and operations people must learn to work together in numerous cooperation.

DEVOPS AFFINITIES WITH AGILE AND LEAN APPROACHES

DevOps has strong affinities with Agile and Lean approaches. It could be interpreted as agile outgrowth. Agile development prescribes close collaboration of clients, developers, product management and at times QA to fill in the gaps and iterate quickly towards a better product. Simply, DevOps is extending Agile principles beyond the code boundaries to the whole service delivered.

WHY DEVELOPERS SHOULD WANT DEVOPS?

DevOps is great for developers. There are three principal reasons that a developer would want to work in an organization that is DevOps-oriented. Developers who work in DevOps-mode receive lesser calls in the middle of the night for resolving production problems. This is because they see problems before they become catastrophic issues because of an orientation of proactive monitoring instead of reactive alerts.

In a traditional software process, once a software is developed, it is ‘thrown over the wall’ to QA, which throws it over later to another wall to production. Thus, what the end-user ultimately sees could be a bit different from what a developer wrote. But, under the DevOps model, what a developer writes goes live since one continues to have access and visibility to the code even after it goes to QA and production. In other words, developers own the code delivery from creation to implementation.

Developers, such as most human beings, get greater satisfaction from work with relevance in the real world. As the developers in a traditional organization are isolated, often they work on simulated problems in made-up use scenarios and they just find out that these approximations were wrong when something will break. In a DevOps model, the scenarios are real. For instance, environments are load tested before they are put into production to determine if they work correctly. Another instance is that test scripts are, themselves tested for realism via being deployed in a production environment, not only test labs. Sharing the test results with developers provide them the chance to see how their code will perform under real-life scenarios.

DevOps need an orchestra leader. Selling a DevOps environment is all about understanding what is relevant to management. Is it moving higher quality, moving faster? Is it about developers more accountable for their code? All these come about by way of a DevOps environment.

DevOps is all about understanding what is important to organization management. It is great for developers.