DevOps 원칙

To realize the full potential of DevOps, teams should follow key DevOps principles

DevOps is more than just development and operations teams working together. It’s more than tools and practices. DevOps is a mindset, a cultural shift, where teams adopt new ways of working.

Atlassian DevOps 무한 고리

A DevOps culture means developers get closer to the user by gaining a better understanding of user requirements and needs. Operations teams get involved in the development process and add maintenance requirements and customer needs. It means adhering to the following key principles that help DevOps teams deliver applications and services at a faster pace and higher quality than organizations using the traditional software development model.


The key premise behind DevOps is collaboration. Development and operations teams coalesce into a functional team that communicates, shares feedback, and collaborates throughout the entire development and deployment cycle. Often, this means development and operations teams merge into a single team that works across the entire application lifecycle.

The members of a DevOps team are responsible for ensuring quality deliverables across each facet of the product. This leads to more ‘full stack’ development, where teams own the complete backend-to-frontend responsibilities of a feature or product. Teams will own a feature or project throughout the complete lifecycle from idea to delivery. This enhanced level of investment and attachment from the team leads to higher quality output.


An essential practice of DevOps is to automate as much of the software development lifecycle as possible. This gives developers more time to write code and develop new features. Automation is a key element of a CI/CD pipeline and helps to reduce human errors and increase team productivity. With automated processes, teams achieve continuous improvement with short iteration times, which allows them to quickly respond to customer feedback.

Continuous Improvement

Continuous improvement was established as a staple of agile practices, as well as lean manufacturing and Improvement Kata. It’s the practice of focusing on experimentation, minimizing waste, and optimizing for speed, cost, and ease of delivery. Continuous improvement is also tied to continuous delivery, allowing DevOps teams to continuously push updates that improve the efficiency of software systems. The constant pipeline of new releases means teams consistently push code changes that eliminate waste, improve development efficiency, and bring more customer value.

Customer-centric action

DevOps teams use short feedback loops with customers and end users to develop products and services centered around user needs. DevOps practices enable rapid collection and response to user feedback through use of real-time live monitoring and rapid deployment. Teams get immediate visibility into how live users interact with a software system and use that insight to develop further improvements.

Create with the end in mind

This principle encourages building software that meets real-world demands and expectations. A common failure scenario in software development is one in which a team ‘builds in a bubble’ That is they make assumptions about how consumers will use the software they are developing and build the software out to those assumed expectations. This principle is complementary to customer-centric action and both help to keep teams grounded in reality and build something that customers want.

인용 부호

DevOps는 한 사람이 하는 일이 아니라 모두가 함께해야 하는 일입니다.

Christophe Capel
Jira Service Management 수석 제품 관리자 로고

DevOps는 누가 수행합니까?

Chef는 DevOps 워크플로를 위한 Chef Automate 플랫폼을 제공하는 회사입니다. 수많은 개발자가 Chef를 사용하여 인프라를 테스트, 자동화 및 관리합니다. DevOps 혁신에 앞장서고 있으며 시애틀에 본사를 둔 Chef는 새로운 방식의 소프트웨어 및 애플리케이션 개발과 출시를 지원하는 Chef, InSpec, Habitat, Chef Automate 등의 제품을 릴리스했습니다. 내부 DevOps 관행을 실험하고 개선하기 위해 Chef는 Atlassian 플랫폼을 사용합니다.

History of DevOps

The DevOps movement began around 2007 when the IT operations and software development communities raised concerns about the traditional software development model. While agile methodologies were widely adopted by development teams to improve collaboration, among other benefits, the developers who wrote code often worked separately from the operations team that supported the code in production. This resulted in inefficient processes and a general lack of collaboration between these two siloed teams. 

The remedy was DevOps, which bridges the gap between these teams so they work cohesively. DevOps brings together the skills, processes, and tools together from both development and operations teams.

Benefits of DevOps

There are three primary categories of benefits for DevOps: technical benefits, cultural benefits, and business benefits. The technical benefits include reduced complexity, continuous delivery, and faster problem resolution. DevOps practitioners typically deploy higher-quality code faster than traditional siloed teams.

The cultural benefits are more productive and efficient teams, and happier customers. On the business end, the benefits include greater collaboration and trust between team members, which results in faster delivery and stable operating environments.

DevOps culture

DevOps is a cultural shift where teams embrace a software engineering culture, workflow, and toolset that elevates operational requirements to the same level of importance as architecture, design, and development. When developers who build software also run it, they have a greater understanding of user requirements and needs. The values of  a DevOps culture include increased transparency, communication, and collaboration across teams.

DevOps engineer

When organizations want to implement DevOps, they can turn to a DevOps engineer. This person has a wide-ranging skill set that spans both development and operations, but also the interpersonal skills to bridge divides between siloed teams. 

A DevOps engineer is an IT generalist with a wide range of knowledge around day-to-day software development, cloud infrastructure management, system administration, and automation.

Always-on services

Customers expect and demand always-on, always available services. DevOps is well suited to supporting “always-on” software, or software as a service. It reinforces the cycle of continuous deployment, feedback, and maintenance or incident response that teams need to keep always-on services, always on.

다음 주제

여러분께 도움을 드릴 자료를 추천합니다.

이러한 리소스에 책갈피를 지정하여 DevOps 팀의 유형에 대해 알아보거나 Atlassian에서 DevOps에 대한 지속적인 업데이트를 확인하세요.

DevOps 일러스트레이션

DevOps 커뮤니티

DevOps 일러스트레이션

시뮬레이션 워크숍

맵 일러스트레이션

무료로 사용해보기

DevOps 뉴스레터 신청

Thank you for signing up