Pavlo Baron20 reasons why wedont need architects
Pavlo Baron            Geek‘s             Guide    pavlo.baron@codecentric.deTo The Working Life                @pavlobaron
Devs
Managers
Consultants
Softwarearchitects
Enterprise architects
Chiefarchitects
Why
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
What happened
Agility becamemainstream
We gave tradeoffs a try
But conflicts are too big
and still...
Now what
Fromtheoretist
Throughexcercise
(again) to practitioner
get           on      down   and               at             IT
enter the Matrix
Team is architect
One boat, one pace
What architecturemanagement tools      do we need
Wetware
TEAM
Funnel
Scepticism2.0
ARIS?Argus!
Run, Forrester, Run!
Eureka!
You drive!
Reproduce
Eat yourowndog food
So, what  should anarchitect be
Champ
Visionary
Chief
Motivator
Worker
Thank you
Most images originate from                istockphoto.com          except few ones takenfrom Wikipedia and product pages  ...
20 reasons why we don't need architects (@pavlobaron)
Upcoming SlideShare
Loading in …5
×

20 reasons why we don't need architects (@pavlobaron)

8,615 views

Published on

Slides of my controversial talk at DOAG and JUG in Germany

Published in: Technology, Design, Business
2 Comments
10 Likes
Statistics
Notes
No Downloads
Views
Total views
8,615
On SlideShare
0
From Embeds
0
Number of Embeds
296
Actions
Shares
0
Downloads
0
Comments
2
Likes
10
Embeds 0
No embeds

No notes for slide

×