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

삼성 SDS SW Eng 팀황상철 책임

k16wire@gmail.com

Agile vs. WaterfallAgile vs. Waterfall

Architecture in Agile Architecture in Agile DevelopmentDevelopmentArchitect in Agile Architect in Agile DevelopmentDevelopment

Agenda

Q & AQ & A

About the Speaker

황상철 책임삼성 SDS SW Eng 팀자바 리더 / 애자일 확산 / 테스트 자동화Java Community Master

번역 : SOA, Scrum 진행

블로그 : 실용주의 이야기 (http://pragmaticstory.com)

Agile vs. WaterfallAgile vs. Waterfall

Get Agile vs Waterfall

• documenting, designing• direct work, contract• team work• value• customer’s role, leader’s role

Architecture Architecture in Agile Developmentin Agile Development

•Coding Standards•System Metaphor•Simplicity•Spike

In Extreme Programming

Coding Standards

Java Coding Convetion on One Page

Sun Java Code Convetion

Simplicity

•Iteration zero•Architectural statement is w/s•Architecture is defined as core p/f •Evangelist for technology•SA must know how to code

In Scrum Gathering April 16,2008

Architectural Statement

System Metaphor

SA must know how to code

Architect Architect in Agile Developmentin Agile Development

To Structureor not to structure.

What is Agile Architect?

What is Agile Architect?

document

document

Incremental

IncrementalCommunicati

onCommunicati

on

The 7 Golden RuleThe 7 Golden Rule

• Value People• Communicate!

• Less is More• Embrace Change: Plan It, Manage It.

• Deliver Quality• Model and Document in an Agile Fashion

Value People

Communicate

Model and Document

ResponsibilityResponsibility • Consider change and complexity• Support change but control complexity• Remove impedance

Support change but control complexity

Remove impedance

Best PracticesBest Practices • Invite Peer Review• Acknowledge Tech. is not your biggest Problem.• Reuse is also about people.• Be Subjective, Try before choosing.• Continuously Integrate.• Challenge preconceived ideas.• Communicate Architectural trade offs.• Fail Early: Learn form Mistakes.

Invite Peer Review

Be Subjective, Try before choosing

Challenge preconceived ideas

Communicate Architectural trade offs

Learn form Mistakes

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

실용주의 이야기 (http://pragmaticstory.com)k16wire@gmail.com

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