📌  相关文章
📜  DevOps vs敏捷

📅  最后修改于: 2020-12-30 01:18:25             🧑  作者: Mango

DevOps与敏捷

DevOps和Agile是两种具有相似目标的软件开发方法，旨在尽可能快，高效地获得最终产品。尽管许多组织都希望采用这些做法，但两种方法之间常常会有一些混淆。

每种方法论包含什么?它们在哪里重叠?他们可以一起工作，还是我们应该选择一个?

在继续之前，请看一下DevOps和Agile。

什么是DevOps?

DevOps是两个词的组合，一个是软件开发，另一个是Operations。这样一来，一个团队就可以处理从开发到测试，部署和操作的整个应用程序生命周期。 DevOps可帮助您减少软件开发人员，质量保证(QA)工程师和系统管理员之间的联系。

DevOps促进开发和运营团队之间的协作，以自动化和可重复的方式将代码更快地部署到生产中。

DevOps帮助提高组织交付应用程序和服务的速度。它还使组织可以更好地为客户服务，并在市场上更强大地竞争。

DevOps也可以定义为具有更好的沟通和协作的一系列开发和IT运营。

DevOps已成为企业或组织最有价值的业务学科之一。借助DevOps，在很大程度上提高了应用程序交付的质量和速度。

DevOps只是使“开发人员”和“运营”人员一起工作的一种实践或方法。 DevOps代表着IT文化的一种变化，它完全专注于在面向系统方法的上下文中通过采用敏捷实践来快速交付IT服务。

什么是敏捷?

敏捷涉及SDLC流程中开发和测试的连续迭代。与瀑布模型不同，开发和测试活动是同时进行的。这种软件开发方法强调增量，迭代和渐进式开发。

它将产品分解成小块，并将其集成以进行最终测试。它可以通过多种方式实现，例如看板，XP，Scrum等。

敏捷软件开发专注于四个核心价值，例如：

  • 工作软件超过全面的文档。
  • 响应按照计划进行的转换。
  • 通过合同谈判进行客户协作。
  • 在流程和工具上的个人和团队交互。

以下是DevOps和Agile之间的一些本质区别：

Parameter DevOps Agile
Definition DevOps is a practice of bringing development and operation teams together. Agile refers to the continuous iterative approach, which focuses on collaboration, customer feedback, small, and rapid releases.
Purpose DevOps purpose is to manage end to end engineering processes. The agile purpose is to manage complex projects.
Task It focuses on constant testing and delivery. It focuses on constant changes.
Team size It has a large team size as it involves all the stack holders. It has a small team size. As smaller is the team, the fewer people work on it so that they can move faster.
Team skillset The DevOps divides and spreads the skill set between development and the operation team. The Agile development emphasizes training all team members to have a wide variety of similar and equal skills.
Implementation DevOps is focused on collaboration, so it does not have any commonly accepted framework. Agile can implement within a range of tactical frameworks such as safe, scrum, and sprint.
Duration The ideal goal is to deliver the code to production daily or every few hours. Agile development is managed in units of sprints. So this time is much less than a month for each sprint.
Target areas End to End business solution and fast delivery. Software development.
Feedback Feedback comes from the internal team. In Agile, feedback is coming from the customer.
Shift left principle It supports both variations left and right. It supports only shift left.
Focus DevOps focuses on operational and business readiness. Agile focuses on functional and non-functional readiness.
Importance In DevOps, developing, testing, and implementation all are equally important. Developing software is inherent to Agile.
Quality DevOps contributes to creating better quality with automation and early bug removal. Developers need to follow Coding and best Architectural practices to maintain quality standards. The Agile produces better applications suites with the desired requirements. It can quickly adapt according to the changes made on time during the project life.
Tools Puppet, Chef, AWS, Ansible, and team City OpenStack are popular DevOps tools. Bugzilla, Kanboard, JIRA are some popular Agile tools.
Automation Automation is the primary goal of DevOps. It works on the principle of maximizing efficiency when deploying software. Agile does not emphasize on the automation.
Communication DevOps communication involves specs and design documents. It is essential for the operational team to fully understand the software release and its network implications for the enough running the deployment process. Scrum is the most common method of implementing Agile software development. Scrum meeting is carried out daily.
Documentation In the DevOps, the process documentation is foremost because it will send the software to an operational team for deployment. Automation minimizes the impact of insufficient documentation. However, in the development of sophisticated software, it’s difficult to transfer all the knowledge required. The agile method gives priority to the working system over complete documentation. It is ideal when you are flexible and responsive. However, it can harm when you are trying to turn things over to another team for deployment.