20 reasons why we don't need architects (@pavlobaron)
10 likes8,741 views
This document discusses the changing role of software architects and argues that they are no longer needed. It notes that agility has become mainstream and that conflicts between architects and developers are too large. It suggests that the team as a whole can serve as the architect and that what is needed are tools to help with architecture management, workflow, and reproducing architectures across teams. The document questions what an architect should be in this new landscape, listing roles like visionary, chief motivator, and worker.
20 reasons why we don't need architects (@pavlobaron)
- 1. Pavlo Baron 20 reasons why we don't need architects
- 2. Pavlo Baron Geek‘s Guide [email protected] To The Working Life @pavlobaron
- 3. Devs
- 4. Managers
- 5. Consultants
- 9. Why
- 10. 1
- 11. 2
- 12. 3
- 13. 4
- 14. 5
- 15. 6
- 16. 7
- 17. 8
- 18. 9
- 19. 10
- 20. 11
- 21. 12
- 22. 13
- 23. 14
- 24. 15
- 25. 16
- 26. 17
- 27. 18
- 28. 19
- 29. 20
- 30. What happened
- 33. We gave tradeoffs a try
- 34. But conflicts are too big
- 35. and still...
- 36. Now what
- 37. From theoretist
- 40. get on down and at IT
- 41. enter the Matrix
- 43. One boat, one pace
- 44. What architecture management tools do we need
- 45. Wetware
- 46. TEAM
- 47. Funnel
- 48. Scepticism 2.0
- 49. ARIS? Argus!
- 51. Eureka!
- 52. You drive!
- 53. Reproduce
- 55. So, what should an architect be
- 56. Champ
- 57. Visionary
- 58. Chief
- 59. Motivator
- 60. Worker
- 61. Thank you
- 62. Most images originate from istockphoto.com except few ones taken from Wikipedia and product pages or generated through public online generators