Skip to main content

Certified Enterprise Architect Professional (CEAP) - Module 6 - Module 6: Business Architecture

Business Architecture:

The exchange of services and information is defined in terms of business.

In enterprise architecture, "business architecture" refers to a specific component that focuses solely on the organizational structure, strategy, processes, and capabilities of a company, essentially acting as a blueprint for how the business operates and aligns with its strategic goals, while the broader enterprise architecture encompasses the business architecture alongside data, applications, and technology aspects to create a holistic view of the entire organization.

Business Architecture objectives include:

  • Development of the desired Business Architecture
  • Describe what is required to achieve business goals
  • Respond to the defined strategic initiatives
  • Address stakeholder concerns and architecture requests

Business Architecture Structure and Behavior is a topic comprised of the following

elements:

  • Business Functions
  • Business Capability and Capability Based Planning
  • Business Model
  • Business Terms and Concepts
  • Value Chain Diagram
The Value Chain is a strategic diagram that allows the primary and secondary activities in an organization to be modeled.

Value Chain diagram for Business Service:


Business Function Portfolio or Catalog:

A business portfolio is a dynamic document that provides a comprehensive overview of a company's activities, goals, and identity. It can include a variety of information, such as:
  • Products and services
  • Strategic business units (SBUs)
  • Mission statement
  • Organizational goals
  • Investments and amounts
  • Branding elements
  • Company assets and holdings
  • Certifications
  • Strategic alliances
  • Potential future acquisitions 
Business Capability and Capability Based Planning :
A "business capability" refers to what an organization can do, essentially a high-level function or activity that represents a core competency, while "capability-based planning" is a strategic planning method that focuses on aligning organizational initiatives and investments with these core capabilities to achieve business goals, prioritizing "what" the company can do over specific tactics or processes to achieve it; essentially, it's a way to plan by understanding and leveraging an organization's key strengths and abilities rather than just individual tasks or projects.

Example:

Let's say a company wants to implement a new CRM system. Business Architecture can be used to:

  • Define the program vision: "To improve customer satisfaction and increase sales by implementing a new CRM system that enables a 360-degree view of the customer."
  • Identify stakeholders: Sales, Marketing, Customer Service, IT
  • Map business capabilities: Customer Relationship Management, Sales Management, Marketing Automation
  • Define the target operating model: A customer-centric organization with streamlined sales and marketing processes
  • Manage dependencies: Integration with existing systems, data migration
  • Measure progress: Increased customer satisfaction scores, increased sales revenue

By applying Business Architecture in this way, the company can ensure that the CRM implementation program is aligned with its overall business strategy and that it delivers the desired business outcomes.


Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .