Any company creating a new EA organization must make many decisions throughout the process. How many architects do we need? How much, and what kind of experience should they have? Who reports to whom? Learn how the answers to these questions are informed by the goals and mission of the EA organization as a whole in this video.
- One of the first questions to ask when building … your EA team is, are you starting from scratch? … Do you currently have any architects? … Keep in mind that an architectural title doesn't always … mean a formal architectural background. … Unfortunately, the title architect is often conveyed … on senior developers to recognize their seniority, … which can be confusing for hiring managers. … The architect title doesn't necessarily relate … to specific architectural training and experience. … Senior developers with the architect title … may be doing a sort of de facto application architecture, … but they are unlikely to be doing it in a formal, … structured way. … They may be performing more as technical leads, … spending the majority of their time writing code … with little focus on architecture. … If you do have a team of architects … with a formalized process that includes frameworks … like Zachman or TOGAF and practices like peer review, … then you're really in a position to grow an existing team. …
- Why do enterprises need architecture?
- How do enterprise architects add value in an organization?
- Application, solution, and enterprise architecture
- Pursuing EA as a career
- Working with EA frameworks and practices
- Integrating EA with process systems
- Creating a new EA organization