애자일

Published by Woong Geun Jang,

애자일은 정신이고, 그 정신이 내재화되어 있지 않으면,
애자일한 소프트웨어 개발은 이루어질 수 없다.

애자일한 정신이 갖추었을 때 비로소 애자일 방법론인 스크럼, 칸반 등이 효용을 발휘하는 것이다.
다시 한 번 애자일 정신을 보고 내재화하도록 노력하자.


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.


이러한 매니페스토는 다음의 12가지 원칙을 기반으로 정립되었다.

  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the primary measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly

참고문서