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)

4,654

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
4,654
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
2
Likes
10
Embeds 0
No embeds

No notes for slide

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

  1. 1. Pavlo Baron20 reasons why wedont need architects
  2. 2. Pavlo Baron Geek‘s Guide pavlo.baron@codecentric.deTo The Working Life @pavlobaron
  3. 3. Devs
  4. 4. Managers
  5. 5. Consultants
  6. 6. Softwarearchitects
  7. 7. Enterprise architects
  8. 8. Chiefarchitects
  9. 9. Why
  10. 10. 1
  11. 11. 2
  12. 12. 3
  13. 13. 4
  14. 14. 5
  15. 15. 6
  16. 16. 7
  17. 17. 8
  18. 18. 9
  19. 19. 10
  20. 20. 11
  21. 21. 12
  22. 22. 13
  23. 23. 14
  24. 24. 15
  25. 25. 16
  26. 26. 17
  27. 27. 18
  28. 28. 19
  29. 29. 20
  30. 30. What happened
  31. 31. Agility becamemainstream
  32. 32. We gave tradeoffs a try
  33. 33. But conflicts are too big
  34. 34. and still...
  35. 35. Now what
  36. 36. Fromtheoretist
  37. 37. Throughexcercise
  38. 38. (again) to practitioner
  39. 39. get on down and at IT
  40. 40. enter the Matrix
  41. 41. Team is architect
  42. 42. One boat, one pace
  43. 43. What architecturemanagement tools do we need
  44. 44. Wetware
  45. 45. TEAM
  46. 46. Funnel
  47. 47. Scepticism2.0
  48. 48. ARIS?Argus!
  49. 49. Run, Forrester, Run!
  50. 50. Eureka!
  51. 51. You drive!
  52. 52. Reproduce
  53. 53. Eat yourowndog food
  54. 54. So, what should anarchitect be
  55. 55. Champ
  56. 56. Visionary
  57. 57. Chief
  58. 58. Motivator
  59. 59. Worker
  60. 60. Thank you
  61. 61. Most images originate from istockphoto.com except few ones takenfrom Wikipedia and product pages or generated through public online generators

×