Save my name, email, and website in this browser for the next time I comment. To succeed, CIOs need to focus more resources in communicating and building Business Architecture change maps that will involve not just enterprise architects, but also business executives, business architects and obviously, the CIO. It is very important to note that the frameworks below are not standards. Integrates all aspects of strategic analysis and planning through solution deployment, Provides a complete business and IT perspective to issue analysis and cost/benefit analysis, and, Aligns multiple disciplines cross the business and technology teams to maximize investments while optimizing value.”[19], © Copyright 2019 Benchmark Consulting Canada. They are suggestive (rather than prescriptive) tools that help IT shops design and manage towards meeting the axioms above. A capability model is an integral part of the business architecture deliverables and is a significant component of BizBok (Business Architecture Book of Knowledge). In such scenarios, an organisation runs the risk of doing EA without Business Architecture. As I’ve tried to illustrate above, there is not a single framework that can cover all of your needs (i.e. ISO27001 / ISO31000. The business architect works with various IT architects to develop a project plan along with roles and responsibilities. [15] The TOGAF Capability and TOGAF Value Stream video Guides are available on these webpages: https://youtu.be/epQ09u9hUCw and https://youtu.be/W3yHCffXDM0. Please refer to BIZBOK v3.5, Section 6.2 for details. Therefore, you won’t technically implement COBIT processes from the bottom up, but use it as a tool to help you control processes from top down as a part of a larger governance initiative. Deploy frameworks in phases. But to what end? While there is general agreement that Business Architecture should help frame business requirements for IT, this represents a limited view of the role of Business Architecture within an organization according to BIZBOK®. My advice is both. Too often CIOs fight this trend by transforming their department using enterprise architects, focusing on what they know best: technical infrastructure, information/data, application/integration and leaving too many times hardly any resources for Business Architecture. All live classes 100% available with RemoteLive! infra, integration). How SABSA can be integrated with TOGAF. Fortunately, Enterprise Architecture (“EA”) is not always only about enterprise and IT documentation anymore. The Object Management Group (“OMG”) and the Business Architecture Guild® are currently working hard to establish a formal metamodel to enable BIZBOK® based tool automation. Of course, you don’t have to follow this by the book, but considering the challenges in our industry with respect to achieving project goals (generally attributed to scope, time and budget constraints), you should spend some time seriously contemplating the benefits of using this as a means to formalizing your project management methodology. This is when I encountered a new issue…the IT department. However, these efforts risk falling short of becoming something much more meaningful and sustainable investment for business and not just IT.”[9], How Enterprise Architecture and Business Architecture Fit Together, There has regrettably been some contention between business architects and enterprise architects in the past and still today. To succeed, an organization and its CIO(s) need to focus more resources in building and communicating Business Architecture change maps that will involve not just enterprise architects, but also business executives, business architects and obviously, the CIO(s). In an excellent article entitled “Business Architects vs Enterprise Architects: The Battle Must End”[10], John Maynen[11] explains how both disciplines can be reconciled by asserting that “simplistically, Business Architecture is about what a business does while Enterprise Architecture is about what a business knows.”.