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

This article mainly explains "What are the differences between DevOps and Agile". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's take you to learn the difference between DevOps and Agile.

The difference between the two is what happens after development.

Early on, software development did not have a specific management process. Then came Waterfall, which suggested that software development activities could be defined in terms of the time spent developing and building applications.

At that time, software often took a long time to develop, test, and deploy because there were no reviews and trade-offs in the development process. The software delivered was also of poor quality with defects and bugs, and the delivery time did not meet the requirements. At that time, software project management focused on long-term and delayed planning.

The waterfall process is related to the triple constraint model, also known as the project management triangle. Each side of the triangle represents one of the three elements of project management: scope, time, and cost. As Angelo Baretta writes, the triple constraint model "considers cost as a function of time and scope, and these three constraints interact in a deterministic, predictable way... If we want to shorten the timetable, we must increase the cost. If we want to increase the scope, we have to increase the cost or time. "

Transition from waterfall process to agile development

Waterfall flows are derived from production and engineering domains that lend themselves to linearized flows: just as a building needs to have a supporting wall built before it can be capped. Similarly, software development problems are thought to be solvable by planning ahead. From start to finish, the development process is clearly defined by a roadmap that leads to the final product delivery.

Ultimately, the waterfall model is considered counterintuitive and detrimental to software development because the value of a project is often not realized until the end of the development process, resulting in many projects failing. Also, the customer doesn't see any software that works until the project is over.

Agile takes a different approach. It abandons planning the entire project, promises estimated time points, and simply follows the plan. As opposed to waterfall flow, it assumes and embraces uncertainty. Its philosophy is to respond to change instead of discussing the past, and it considers change to be part of customer needs.

agile values

Agile is represented by the Agile Manifesto, which defines 12 principles:

Our most important goal is customer satisfaction through consistent early delivery of valuable software.

Be open to changing requirements, even late in development.

Working software is delivered frequently, a few weeks or a month or two apart, and tends to take shorter cycles.

Business people and developers must work together, and every day on a project is no exception.

Motivate individuals and build projects around them. Provide the environment and support needed, supplemented by trust, to achieve goals.

Face-to-face communication is the best and most efficient way to convey information.

Working software is the primary measure of progress.

Agile processes advocate sustainable development, where owners, developers, and users can work together to maintain a consistent pace.

Agility is enhanced by a relentless pursuit of technical excellence and good design.

Primed in simplicity, it is the art of minimizing unnecessary work.

The best architectures, requirements and designs come from self-organizing teams

The team regularly reflects on how it can improve its effectiveness and adjusts its behavior accordingly.

The four core values of Agile are:

Individuals and interactions over processes and tools

Working software trumps detailed documentation

Customer cooperation is higher than contract negotiation

Responding to changes higher than adherence plan

This is the opposite of the rigid planning style of the waterfall process. In agile processes, the customer is part of the development team, not just involved in defining project requirements at the beginning of the project and accepting the final product at the end of the project. The customer helps the team complete the acceptance criteria and remains engaged throughout the process. Agility also requires change and continuous improvement throughout the organization. The development team works with other teams, including the project management team and the testing team. What to do and plan when to do is led by assigned roles and agreed upon by the entire team.

agile software development

Agile software development requires adaptive planning, evolutionary development, and delivery. Many software development methods, frameworks, and practices follow Agile philosophy, including:

Scrum

Kanban(Visual Workflow)

Xtreme Programming(XP)

Lean Method

DevOps

Feature Driven Development(FDD)

Test-Driven Development(TDD)

Crystal Method Crystal

Dynamic Systems Development Method(DSDM)

Adaptive Software Development(ASD)

All of these have been used individually or together to develop and deploy software. The most commonly used are Scrum, Kanban (or Scrumban) and DevOps.

Scrum is a framework adopted by a team, usually composed of a Scrum Coach, Product Manager, and Developer, that operates in a cross-functional, autonomous manner to accelerate software delivery and deliver significant business value to customers. The focus is on fast iterations in small increments.

Kanban is an agile framework, sometimes called a workflow management system, that helps teams visualize their work to maximize efficiency (and thus become agile). Kanban is usually presented by digital or physical display boards. The team's work moves along the dashboard as it progresses, from never started to in progress, to testing, to completed. Kanban allows each team member to see the status of all work at any time.

DevOps values

DevOps is a culture, a state of mind, a way of software development or infrastructure, and a way of building and deploying software and applications. It assumes that there is no gap between development and operations, that they work together, and that there is no contradiction.

DevOps is based on the practices of two other domains: lean and agile. DevOps is not a position or role within a company; it is the relentless pursuit of continuous delivery, continuous deployment, and continuous integration by an organization or team. Gene Kim(author of Project Phoenix and Project Unicorn) believes that there are three ways to define the DevOps philosophy:

The first: process principles

Second: the feedback principle

The third principle: continuous learning

DevOps Software Development

DevOps doesn't happen out of thin air; it's a flexible practice, essentially a shared culture and way of thinking about software development and IT or infrastructure implementation.

When you think of automation, cloud, microservices, you think of DevOps. In an interview, Nicol Forsgren, Jez Humble, and Gene Kim, authors of Accelerating the Build and Scale of High Performance Technology Organizations, explained:

Software delivery capability is important and has a significant impact on organizational outcomes such as profitability, market share, quality, customer satisfaction, and the achievement of an organization's strategic goals.

Good teams achieve high levels of delivery, stability, and quality; they don't make trade-offs to achieve these attributes.

You can improve your capabilities by implementing practices in Lean, Agile, and DevOps.

Implementing these practices and competencies will also impact your organizational culture and will further improve your software delivery and organizational capabilities.

Understanding how to improve your abilities requires a lot of work.

DevOps vs Agile

DevOps and Agile have similarities, but they are not exactly the same, and some people think DevOps is better than Agile. To avoid confusion, it is important to understand them in depth.

similarities between

There is no doubt that both are software development techniques.

Agile has been around for more than 20 years and DevOps is a recent arrival.

Both pursue rapid software development, and their philosophy is based on how to develop software quickly without harming customers or operations interests.

the difference

The difference between the two is what happens after software development is complete.

In DevOps and Agile, there are phases of software development, testing, and deployment. However, agile processes terminate after these three phases. DevOps, on the other hand, involves ongoing operations. Therefore, DevOps continuously monitors software performance and conducts continuous development.

In Agile, different people are responsible for software development, testing, and deployment. DevOps engineering is responsible for all activities, development is operations, operations is development.

DevOps is more focused on cost reduction, while Agile is synonymous with lean and waste reduction, focusing on concepts like agile project accounting and minimum viable product.

Agile focuses on and embodies empiricism (adaptation, transparency and inspection) rather than predictive measures.

At this point, I believe that everyone has a deeper understanding of "what is the difference between DevOps and Agile". Let's actually operate it! Here is the website, more related content can enter the relevant channels for inquiry, pay attention to us, continue to learn!

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.