Scrum, Lean, XP, and DevOps

[곽영어]

Scrum

Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. Scrum co-creators Ken Schwaber and Jeff Sutherland have written The Scrum Guide to explain Scrum clearly and succinctly.  This Guide contains the definition of Scrum. This definition consists of Scrum’s accountabilities, events, artifacts, and the rules that bind them together. 

The Scrum framework focuses on developing, delivering, and sustaining complex products, with an initial emphasis on software, and hardware, based development, although it has been used in other fields including research, sales, marketing and advanced technologies. It is designed for teams of ten or fewer members, who break their work into goals that can be completed within time-boxed iterations, called sprints, no longer than one month and most commonly two weeks. The Scrum Team track progress in 15-minute time-boxed daily meetings, called daily scrums. At the end of the sprint, the team holds sprint review, to demonstrate the work done, and sprint retrospective to improve continuously.

Lean

Lean is an agile framework that promotes an incremental flow of work to the customer. Lean promotes visualizations of work status, and working with small tasks. Lean prescribes focusing on a core set of tasks in a flow environment and completing them. This process then repeats. Lean has 7 principles :

• Eliminate waste: Review the value chain and eliminate wait time

• Build quality in : Test all features that are built

• Create knowledge: Train workers and take on challenges.

• Deliver fast: Work with tasks that are as small as possible and get them done

• Respect people: People do the work

• Optimize the whole: Work with the complete solution that is deliverable to the customer, not the solution components.

XP

Extreme programming (XP) is an Agile methodology which is intended to improve product quality and responsiveness to changing customer requirements. XP it advocates frequent "releases" in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted. Other elements of extreme programming include: programming in small batches, pair programing, extensive code review, and automated and manual unit testing of all code. XP also prescribes continuous integration of code. Integration is a difficult activity. However, if it is done continuously, in small batches the difficulty is reduced.

DevOps

DevOps is another Agile methodology that bridges the gaps between the development team, and the team that operates the product delivery and runtime. The business and development team are tasked with adding new features and functionality to the solution. They also fix issues that were discovered in production. The Operations teams looks to support a stable product that delivers value to the customer. The introduction of new features, and updates can disrupt that operation stability. This causes a conflicting goals between development and operations. The DevOps methodology has practices that allow teams to continuously improve the product, and continuously stabilize the product.

스크럼

스크럼은 사람들이 복잡한 적응형 문제를 해결하면서 생산적이고 창의적으로 최고의 가치를 지닌 제품을 제공할 수 있는 프레임워크입니다.

스크럼은 사람, 팀 및 조직이 복잡한 문제에 대한 적응형 솔루션을 통해 가치를 창출할 수 있도록 지원하는 가벼운 프레임워크입니다. 스크럼을 명확하고 간결하게 설명하기 위해 스크럼의 공동 창시자인 Ken Schwaber와 Jeff Sutherland가 스크럼 가이드를 작성했습니다.  이 가이드에는 스크럼의 정의가 포함되어 있습니다. 이 정의는 스크럼의 책임, 이벤트, 아티팩트 및 이들을 하나로 묶는 규칙으로 구성되어 있습니다. 

스크럼 프레임워크는 연구, 영업, 마케팅, 첨단 기술 등 다른 분야에서도 사용되었지만 초기에는 소프트웨어 및 하드웨어 기반 개발에 중점을 두고 복잡한 제품을 개발, 제공 및 유지하는 데 중점을 두었습니다. 스크럼은 10명 이하의 팀원으로 구성된 팀을 위해 설계되었으며, 스프린트라고 하는 시간 상자 반복, 즉 한 달 이상, 가장 일반적으로 2주 이내에 완료할 수 있는 목표로 작업을 세분화합니다. 스크럼 팀은 일일 스크럼이라고 하는 15분 단위의 일일 회의에서 진행 상황을 추적합니다. 스프린트가 끝나면 팀은 스프린트 검토를 통해 완료된 작업을 시연하고 스프린트 회고를 통해 지속적으로 개선합니다.



린

린은 고객에게 점진적인 업무 흐름을 촉진하는 애자일 프레임워크입니다. 린은 작업 상태의 시각화 및 소규모 작업 작업을 장려합니다. 린은 흐름 환경에서 핵심 작업 세트에 집중하고 이를 완료하도록 규정합니다. 그런 다음 이 과정을 반복합니다. 린에는 7가지 원칙이 있습니다:

낭비를 제거하세요: 가치 사슬을 검토하고 대기 시간을 제거합니다.

에서 품질을 구축합니다: 빌드된 모든 기능을 테스트합니다.

지식을 창출하세요: 직원을 교육하고 도전 과제에 도전하세요.

빠르게 제공하세요: 가능한 한 작은 작업으로 작업하고 완료하세요.

사람을 존중하세요: 사람이 일을 합니다

전체를 최적화하세요: 솔루션 구성 요소가 아닌 고객에게 제공할 수 있는 전체 솔루션으로 작업하세요.

XP

익스트림 프로그래밍(XP)은 변화하는 고객 요구 사항에 대한 제품 품질과 대응력을 개선하기 위한 애자일 방법론입니다. XP는 생산성을 개선하고 새로운 고객 요구 사항을 채택할 수 있는 체크포인트를 도입하기 위해 짧은 개발 주기로 자주 "릴리스"하는 것을 옹호합니다. 익스트림 프로그래밍의 다른 요소로는 소규모 배치 프로그래밍, 페어 프로그래밍, 광범위한 코드 검토, 모든 코드의 자동 및 수동 단위 테스트 등이 있습니다. XP는 또한 코드의 지속적인 통합을 규정하고 있습니다. 통합은 어려운 작업입니다. 그러나 소량으로 지속적으로 수행하면 난이도가 줄어듭니다.

데브옵스

데브옵스는 개발 팀과 제품 배포 및 런타임을 운영하는 팀 간의 격차를 해소하는 또 다른 애자일 방법론입니다. 비즈니스 팀과 개발 팀은 솔루션에 새로운 기능을 추가하는 임무를 맡습니다. 또한 프로덕션 환경에서 발견된 문제를 해결합니다. 운영 팀은 고객에게 가치를 제공하는 안정적인 제품을 지원합니다. 새로운 기능과 업데이트의 도입은 이러한 운영 안정성을 방해할 수 있습니다. 이로 인해 개발과 운영 간의 목표가 상충될 수 있습니다. 데브옵스 방법론에는 팀이 지속적으로 제품을 개선하고 제품을 지속적으로 안정화할 수 있는 관행이 있습니다.