This document discusses the role of an architect in agile development. It compares waterfall and agile architecture approaches. The architect's responsibilities in agile include incrementally documenting designs, communicating with the team, embracing change, and removing impediments. Best practices for agile architecture include inviting peer review, challenging assumptions, and learning from mistakes. The architect must understand coding and know how to work with people as technology alone is not enough.

1. 애자일 아키텍트를 위한 툴박스 삼성 SDS SW Eng 팀 황상철 책임 [email_address]

2. Agile vs. Waterfall Architecture in Agile Development Architect in Agile Development Agenda Q & A

3. About the Speaker 황상철 책임 삼성 SDS SW Eng 팀 자바 리더 / 애자일 확산 / 테스트 자동화 Java Community Master 번역 : SOA, Scrum 진행 블로그 : 실용주의 이야기 (http://pragmaticstory.com)

4. Agile vs. Waterfall

5. Get Agile vs Waterfall

9. Architecture in Agile Development

11. Coding Standards Sun Java Code Convetion Java Coding Convetion on One Page

12. Simplicity

14. Architectural Statement System Metaphor

15. SA must know how to code

16. Architect in Agile Development

17. To Structure or not to structure .

18. What is Agile Architect?

19. What is Agile Architect? document Incremental Communication

21. Value People

22. Communicate

23. Model and Document

25. Support change but control complexity

26. Remove impedance

28. Invite Peer Review

29. Be Subjective, Try before choosing

30. Challenge preconceived ideas

31. Communicate Architectural trade offs

32. Learn form Mistakes

33. “ 아키텍트는 기술로만 살 수 없다 !” “ 라면을 끓이는 것은 쉬운 일이나 300 명이 먹을 라면을 끓이는 건 다르다 .”

34. 실용주의 이야기 (http://pragmaticstory.com) [email_address]

35. References [1] http://www.agilearchitect.org [2] XP Site, http://www.extremeprogramming.org [3] Scrum Gathering April 2008, http://www.scrumalliance.org/resources/362 [4] Architecture in An Agile World, http://www.slideshare.net/jamescooper/architecture-in-an-agile-world