Which Questions Must Enterprise Architecture Be Able to Answer
summary
Defines which questions enterprise architecture should and should not be expected to answer, and explains how to frame and answer corporate-level questions appropriately. Covers practical use of enterprise architecture (TOGAF-certified practices) for guiding organizational decision-making and stakeholder inquiries, with examples drawn from consulting and implementation experience.
AI-written summary · about
chapters (13)
- 0:00Introduction to topic
- 1:19Enterprise architecture domains
- 3:50Holistic view value
- 6:00Application investments
- 8:47Redundant functionalities
- 10:16Integrated risk management
- 12:22Automated job descriptions
- 14:46Data-driven decision making
- 16:13New project impact
- 17:39Project management with architecture
- 20:32Holistic decisions with architecture
- 21:13Practical results achieved
- 23:39Conclusion
related talks
30mEA Today and in the Future
50mEnterprise Architecture = Architecting the Enterprise
31mEnterprise Architecture Case: How to Run the Preliminary Phase
38mModern Enterprise Architecture: Architecting for Outcomes
43mModern Enterprise Architecture: architecting for outcomes "Modern Enterprise A..."
40mIs it possible for enterprise architects to be really agile?
37mThe Dark Gods of Enterprise Architecture. To Warp and Back
44mWhen your boss decides to have an architecture team…