Agile sw development

애자일 소프트웨어 개발(Agile software development) 혹은 애자일 개발 프로세스는 소프트웨어 엔지니어링에 대한 개념적인 구조로, 프로젝트 라이프 사이클동안 반복적인 개발을 촉진한다. 이는 어느 특정 개발 방법론을 가리키는 말은 아니고 “애자일(Agile=기민한, 좋은것을 빠르고 낭비없게 만드는 것) 개발을 가능하게 해 주는 다양한 방법론 전체를 일컫는 말이다. 예전에는 애자일 개발 프로세스는 “경량(Lightweight)” 프로세스로 불렸다.

We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
(개개인과 상호 작용/소통을 프로세스와 도구보다)
Working software over comprehensive documentation
(제대로 동작하는 소프트웨어를 폭넓은 문서보다)
Customer collaboration over contract negotiation
(고객과의 협력을 계약 협상보다)
Responding to change over following a plan.
(변화에 대응하는 것을 계획을 준수하는 것보다 더 가치있게 여긴다.)

That is, while there is value in the items on the right, we value the items on the left more.

Principles behind the Agile Manifesto

We follow these principles:

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Business people and developers must work together daily throughout the project.

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Continuous attention to technical excellence and good design enhances agility.

Simplicity--the art of maximizing the amount of work not done--is essential.

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

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile Information

폭포수 모델과 비교

파랑새 신드롬(애자일 컨설팅 김창준)

Scrum

1. Scrum 개요

2. 제품 백로그

3. 스프린트 계획

4. 스프린트 백로그

5. 일일 스크럼

6. 스프린트 검토 및 회고

7. 릴리즈 및 테스트

8. 스크럼 체크리스트

9. 스크럼과의 궁합

10. 엔터프라이즈 스크럼

11. 칸반 게임