0
애자일 아키텍트를 위한 툴박스 삼성  SDS SW Eng  팀 황상철 책임 [email_address]
Agile vs. Waterfall Architecture in Agile Development Architect in Agile Development Agenda Q & A
About the Speaker 황상철 책임 삼성  SDS SW Eng 팀 자바 리더 /  애자일 확산 /  테스트 자동화 Java Community Master 번역 : SOA, Scrum  진행 블로그 :  실용주의...
Agile vs. Waterfall
Get Agile vs Waterfall
 
<ul><li>documenting, designing </li></ul><ul><li>direct work, contract </li></ul><ul><li>team work </li></ul><ul><li>value...
 
Architecture  in Agile Development
<ul><li>Coding Standards </li></ul><ul><li>System Metaphor </li></ul><ul><li>Simplicity </li></ul><ul><li>Spike </li></ul>...
Coding Standards Sun Java Code Convetion  Java Coding Convetion  on One Page
Simplicity
<ul><li>Iteration zero </li></ul><ul><li>Architectural statement is w/s </li></ul><ul><li>Architecture is defined as core ...
Architectural Statement System Metaphor
SA must know how to code
Architect  in Agile Development
To  Structure or not to  structure .
What is Agile Architect?
What is Agile Architect? document Incremental Communication
<ul><li>The 7 Golden Rule </li></ul><ul><li>Value People </li></ul><ul><li>Communicate! </li></ul><ul><li>Less is More </l...
Value People
Communicate
Model and Document
<ul><li>Responsibility </li></ul><ul><li>Consider change and complexity </li></ul><ul><li>Support change but control compl...
Support change but control complexity
Remove impedance
<ul><li>Best Practices </li></ul><ul><li>Invite Peer Review </li></ul><ul><li>Acknowledge Tech. is not your biggest  </li>...
Invite Peer Review
Be Subjective,  Try before choosing
Challenge preconceived ideas
Communicate Architectural trade offs
Learn form Mistakes
“ 아키텍트는 기술로만 살 수 없다 !” “ 라면을 끓이는 것은 쉬운 일이나  300 명이 먹을 라면을 끓이는 건 다르다 .”
실용주의 이야기 (http://pragmaticstory.com) [email_address]
References [1] http://www.agilearchitect.org [2] XP Site, http://www.extremeprogramming.org [3] Scrum Gathering April 2008...
Upcoming SlideShare
Loading in...5
×

애자일 아키텍트를 위한 툴 박스

1,931

Published on

애자일로 개발하는 프로젝트에서 아키텍처를 정의하는 아키텍트의 역할에 대해 이야기 합니다.

Published in: Technology
0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,931
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
29
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide

Transcript of "애자일 아키텍트를 위한 툴 박스"

  1. 1. 애자일 아키텍트를 위한 툴박스 삼성 SDS SW Eng 팀 황상철 책임 [email_address]
  2. 2. Agile vs. Waterfall Architecture in Agile Development Architect in Agile Development Agenda Q & A
  3. 3. About the Speaker 황상철 책임 삼성 SDS SW Eng 팀 자바 리더 / 애자일 확산 / 테스트 자동화 Java Community Master 번역 : SOA, Scrum 진행 블로그 : 실용주의 이야기 (http://pragmaticstory.com)
  4. 4. Agile vs. Waterfall
  5. 5. Get Agile vs Waterfall
  6. 7. <ul><li>documenting, designing </li></ul><ul><li>direct work, contract </li></ul><ul><li>team work </li></ul><ul><li>value </li></ul><ul><li>customer’s role, leader’s role </li></ul>
  7. 9. Architecture in Agile Development
  8. 10. <ul><li>Coding Standards </li></ul><ul><li>System Metaphor </li></ul><ul><li>Simplicity </li></ul><ul><li>Spike </li></ul><ul><li>In Extreme Programming </li></ul>
  9. 11. Coding Standards Sun Java Code Convetion Java Coding Convetion on One Page
  10. 12. Simplicity
  11. 13. <ul><li>Iteration zero </li></ul><ul><li>Architectural statement is w/s </li></ul><ul><li>Architecture is defined as core p/f </li></ul><ul><li>Evangelist for technology </li></ul><ul><li>SA must know how to code </li></ul><ul><li>In Scrum Gathering April 16,2008 </li></ul>
  12. 14. Architectural Statement System Metaphor
  13. 15. SA must know how to code
  14. 16. Architect in Agile Development
  15. 17. To Structure or not to structure .
  16. 18. What is Agile Architect?
  17. 19. What is Agile Architect? document Incremental Communication
  18. 20. <ul><li>The 7 Golden Rule </li></ul><ul><li>Value People </li></ul><ul><li>Communicate! </li></ul><ul><li>Less is More </li></ul><ul><li>Embrace Change: Plan It, Manage It. </li></ul><ul><li>Deliver Quality </li></ul><ul><li>Model and Document in an Agile Fashion </li></ul>
  19. 21. Value People
  20. 22. Communicate
  21. 23. Model and Document
  22. 24. <ul><li>Responsibility </li></ul><ul><li>Consider change and complexity </li></ul><ul><li>Support change but control complexity </li></ul><ul><li>Remove impedance </li></ul>
  23. 25. Support change but control complexity
  24. 26. Remove impedance
  25. 27. <ul><li>Best Practices </li></ul><ul><li>Invite Peer Review </li></ul><ul><li>Acknowledge Tech. is not your biggest </li></ul><ul><li>Problem. </li></ul><ul><li>Reuse is also about people. </li></ul><ul><li>Be Subjective, Try before choosing. </li></ul><ul><li>Continuously Integrate. </li></ul><ul><li>Challenge preconceived ideas. </li></ul><ul><li>Communicate Architectural trade offs. </li></ul><ul><li>Fail Early: Learn form Mistakes. </li></ul>
  26. 28. Invite Peer Review
  27. 29. Be Subjective, Try before choosing
  28. 30. Challenge preconceived ideas
  29. 31. Communicate Architectural trade offs
  30. 32. Learn form Mistakes
  31. 33. “ 아키텍트는 기술로만 살 수 없다 !” “ 라면을 끓이는 것은 쉬운 일이나 300 명이 먹을 라면을 끓이는 건 다르다 .”
  32. 34. 실용주의 이야기 (http://pragmaticstory.com) [email_address]
  33. 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
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×