登录查看更多内容

What are the most common communication gaps between Business Architecture and other domains?

由人工智能和领英社区提供技术支持

Business Architecture (BA) is a discipline that aligns the strategic vision, goals, and capabilities of an organization with its processes, systems, and stakeholders. BA helps to bridge the gap between business and IT, and to ensure that the organization delivers value to its customers and stakeholders. However, BA also faces many communication challenges with other domains, such as project management, enterprise architecture, business analysis, and change management. In this article, we will explore some of the most common communication gaps between BA and other domains, and how to overcome them.

此文章中的业界达人

由社区从 8 条内容中精选。了解更多

1 Project Management

One of the most common communication gaps between BA and project management is the lack of clarity and alignment on the scope, objectives, and benefits of a project. BA often has a broader and longer-term perspective on the business value and outcomes of a project, while project management focuses on the deliverables, timelines, and resources. This can lead to misunderstandings, conflicts, and missed opportunities. To avoid this gap, BA and project management should collaborate early and often, and establish a common language and framework for defining and measuring the project scope, objectives, and benefits. BA should also communicate the business context, assumptions, and risks of the project to project management, and help them prioritize and validate the requirements and solutions.

添加您的观点

Hariom Singh ??.?. ???? ???? ???

Gen AI & Data Product Innovator | MBA, PMP, RMP | Leading Complex Program Management & Data-Driven Solutions at Fortune 500
举报内容
Bridging communication gaps in Business Architecture is crucial for organizational coherence. I'd focus on aligning Business Architecture with Enterprise Architecture to ensure consistent architectural strategies. Addressing the translation of insights into project plans mitigates misalignment with Project Management. Clear communication with business analysis is essential to accurately transform strategies into business requirements. Effective communication regarding the impact of changes aids in smoother Change Management processes. Pro tip: Use Confluence or SharePoint to document and share information, enhancing communication and alignment between Business Architecture and other domains.

已翻译

赞

2 Enterprise Architecture

Another common communication gap between BA and enterprise architecture is the lack of alignment and integration on the architecture principles, standards, and models that guide the design and implementation of the business processes and systems. BA often has a deeper and more detailed understanding of the business needs, capabilities, and processes, while enterprise architecture has a wider and more holistic view of the technical architecture, platforms, and services. This can lead to inconsistencies, redundancies, and gaps in the architecture design and delivery. To avoid this gap, BA and enterprise architecture should collaborate closely and regularly, and share and align their architecture principles, standards, and models. BA should also communicate the business drivers, constraints, and dependencies of the architecture to enterprise architecture, and help them evaluate and select the best-fit architecture options.

添加您的观点

Sumardi Fu Guo Zhang

Agile Leadership | Technology Risk Governance | Architecture Practices | Cloud, Data & AI | Leading Operational Excellence | ACLP, CISSP, CCSP, CGEIT, CDPSE, CISM, CRISC, CISA, COBIT, TOGAF, ITIL, PMP, CSP-SM, CAL
举报内容
The communication gap between BAs and EAs is that it can be caused by different levels of abstraction. BAs tend to focus on the specific details of business processes and systems, while EAs focus on the high-level design and integration of the overall architecture. This can make it difficult for the two groups to communicate effectively, as they are often speaking different languages. To bridge this gap, it is important for BAs and EAs to have common vocabulary & a shared understanding of the business goals and objectives.

已翻译

赞
Nick Free

CITP MBCS, Architecture, Service, Delivery & Continuous Improvement professional
举报内容
A solid grounding in an underpinning framework such as TOGAF will help, if all have that baseline. At least then, the language is universally understood. I also found doing my BCS Foundation Certificate in Enterprise Architecture contributed to my overall general awareness, not to say I am an expert but that I understand common principles, that will help me develop good ways of working.

已翻译

赞
Nima Javanbakht

Enterprise Architecture PhD | @CapitaLand | Chess International Master (IM) #TOGAF Certified #Research
举报内容
One thing I have found useful is to first have a lightweight, common EA knowledge between all architects. Thereafter, the communication gap would be much less between domain architects (in this case BA) and overall EA.

已翻译

赞
Robert Liu

Account Director @ IBM | Business Growth, Large Account Sales - Enterprise Integration Technology
举报内容
To bridge the gap between Business Analysts (BAs) and Enterprise Architects (EAs), a unified platform is essential. This platform should enable both BAs and EAs to collaborate on a common ground, with tools for visualizing and analyzing business processes and architecture. By sharing a repository of information and collaborative planning tools, they can align their strategies with business objectives. This approach not only enhances communication but also supports strategic alignment, informed decision-making, and business agility. I do not wish to promote a product to this but check my profile if you need to learn more about the No.1 Forester solution to this….

已翻译

赞
Asmaa Ahmed

Head of Business Analysis
举报内容
One thing that I have found very helpful to bridge this gap is the Sub Domain Analysis and the Domain Driven Design, in which the business analyst discovers and breaks down the software solution into sub domains. This would help the architecture to map these sub domains to design boundaries.

已翻译

赞

加载更多内容

3 Business Analysis

A third common communication gap between BA and business analysis is the lack of coordination and integration on the elicitation, analysis, and specification of the business requirements and solutions. BA often has a higher and more strategic level of abstraction and scope on the business requirements and solutions, while business analysis has a lower and more operational level of detail and granularity. This can lead to duplication, fragmentation, and ambiguity in the requirements and solutions documentation. To avoid this gap, BA and business analysis should coordinate and integrate their activities and deliverables, and use a consistent and coherent methodology and notation for eliciting, analyzing, and specifying the requirements and solutions. BA should also communicate the business vision, goals, and capabilities to business analysis, and help them trace and validate the requirements and solutions against them.

添加您的观点

4 Change Management

A fourth common communication gap between BA and change management is the lack of awareness and engagement on the impact, readiness, and adoption of the business changes resulting from the projects and initiatives. BA often has a more technical and analytical focus on the business changes, while change management has a more human and emotional focus. This can lead to resistance, confusion, and dissatisfaction among the stakeholders and users affected by the changes. To avoid this gap, BA and change management should work together and communicate frequently, and use a structured and systematic approach for assessing and managing the business changes. BA should also communicate the rationale, benefits, and risks of the business changes to change management, and help them design and deliver the change interventions and support.

添加您的观点

5 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Estelle Sinclair

Improving Business Processes with Simple Steps, Cool Online Tools, and Smart AI | Business Process and Digital Workflow Consultant ??????
举报内容
One of the core issues stems from a lack of clarity on who spearheads the enterprise architecture (EA) strategy. Is it driven by business architecture, technology architecture, or perhaps data architecture? There's a prevailing notion that these blueprints should be reactive, following cues from other domains, rather than being a guiding force. This ambiguity often leads to underutilization of business architect blueprints. This misalignment is further complicated by discrepancies between current and target architectures. The availability, completeness, and accuracy of blueprints at the needed time can significantly impact their effectiveness.

已翻译

赞

Business Architecture

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

What are the most common communication gaps between Business Architecture and other domains?

1

2

3

4

5

1 Project Management

2 Enterprise Architecture

3 Business Analysis

4 Change Management

5 Here’s what else to consider

Business Architecture

给文章评分

感谢您的反馈

更多Business Architecture相关文章

更多相关阅读内容

What are the most common communication gaps between Business Architecture and other domains?

1

2

3

4

5

1 Project Management

2 Enterprise Architecture

3 Business Analysis

4 Change Management

5 Here’s what else to consider

Business Architecture

给文章评分

感谢您的反馈

查看其他技能