White Paper on Agile &DevOps
COURTESY :- vrindawan.in
Wikipedia
Agile may refer to:
- Agile, an entity that possesses agility
- Agile software development, a development method
- Agile construction, iterative and incremental construction method
- Agile learning, the application of incremental and iterative methods to learning processes
- Agile manufacturing, an organization able to respond quickly to customer needs and market changes
-
- AIM-95 Agile, an air-to-air missile
- HMS Agile, a never-built Amphion-class submarine
- Project AGILE, a 1960s ARPA program
- USS Agile, two minesweepers
- AGILE (satellite) (Astro-rivelatore Gamma a Immagini LEggero), an astronomical satellite of the Italian Space Agency
- Agile (horse) (born 1902), American thoroughbred racehorse, winner of the 1905 Kentucky Derby
- Agile (producer) (born 1975), Canadian hip-hop music producer
- Agile, a member of the X-Hunters in the video game Mega Man X2
- Chevrolet Agile, a subcompact car
- Wallis WA-116 Agile, a 1960s British autogyro, used in the James Bond film You Only Live Twice
- Agile (species group), a wasp species complex in the genus Pison
- AGILE (Aircraft 3rd Generation MDO for Innovative Collaboration of Heterogeneous Teams of Experts) was an H2020 European funded project
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary with Agile software development; several DevOps aspects came from the Agile way of working.
Other than it being a cross-functional combination (and a portmanteau) of the terms and concepts for “development” and “operations”, academics and practitioners have not developed a universal definition for the term “DevOps”. Most often, DevOps is characterized by key principles: shared ownership, workflow automation, and rapid feedback.
From an academic perspective, Len Bass, Ingo Weber, and Liming Zhu—three computer science researchers from the CSIRO and the Software Engineering Institute—suggested defining DevOps as “a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality”.
However, the term is used in multiple contexts. At its most successful, DevOps is a combination of specific practices, culture change, and tools.
In 1993 the Telecommunications Information Networking Architecture Consortium (TINA-C) defined a Model of a Service Life cycle that combined software development with (telecom) service operations.
In 2009, the first conference named devop sdays was held in Ghent, Belgium. The conference was founded by Belgian consultant, project manager and agile practitioner Patrick Debois. The conference has now spread to other countries.
In 2012, the State of DevOps report was conceived and launched by Alanna Brown at Puppet.
As of 2014, the annual State of DevOps report was published by Nicole Forsgren, Gene Kim, Jez Humble and others. They stated that the adoption of DevOps was accelerating. Also in 2014, Lisa Crispin and Janet Gregory wrote the book More Agile Testing, containing a chapter on testing and DevOps.
In 2016 the DORA metrics for throughput (deployment frequency, lead time for changes), and stability (mean time to recover, change failure rate) were published in the State of DevOps report.
Many of the ideas fundamental to DevOps practices are inspired by, or mirror, other well known practices such as Lean and Deming’s Plan-Do-Check-Act cycle, through to The Toyota Way and the Agile approach of breaking down components and batch sizes. Contrary to the “top-down” pro scriptive approach and rigid framework of ITIL in the 1990s, DevOps is “bottom-up” and a flexible practice, created by software engineers, with software engineer needs in mind.
The motivations for what has become modern DevOps and several standard DevOps practices such as automated build and test, continuous integration, and continuous delivery originated in the Agile world, which dates (informally) to the 1990s, and formally to 2001. Agile development teams using methods such as Extreme Programming couldn’t “satisfy the customer through early and continuous delivery of valuable software” unless they subsumed the operations / infrastructure responsibilities associated with their applications, many of which they automated. Because Scrum emerged as the dominant Agile framework in the early 2000s and it omitted the engineering practices that were part of many Agile teams, the movement to automate operations / infrastructure functions splintered from Agile and expanded into what has become modern DevOps. Today, DevOps focuses on the deployment of developed software, whether it is developed using Agile oriented methodologies or other methodologies.