Working Draft

This site is currently a working draft of the ITABoK 3.0. Release date is planned for summer of 2021. In the meantime please utilize the current ITABoK version 2.0 

What is an Engagement Model

The Iasa Engagement Model are the combined activities, deliverables, and work that an organization of architects use to achieve a mature and valuable architecture practice. The goal of the engagement model is to make the best use of architecture teams work to deliver on business technology strategy.

Lifecycles, Weave(s) and Threads

The Iasa Engagement Model includes many practical activities which help architects develop and grow their architecture capability. These activities are often labeled Weaves or Threads to help isolate specific activities in the engagement model. We use the term thread to delineate a specific arrangement of activities that is somewhat smaller than a Weave which has a much larger/multi-team based usage.

Business to Solution Architecture – The Value Weave

This method is built to optimize value streams and large solutions which require deep strategy to execution understanding throughout the lifecycle. Note: while the timeline is written sequentially, this is NOT considered a waterfall activity, it is simply the limitation of graphics and navigation lending itself to a somewhat sequential order. It should be understood that many of these activities happen concurrently, iteratively and with multiple team members leading and participating.

Preloader
  • Introduction

    Introduction

    The Value ‘Weave’ provides a view of using the ITABoK on a value stream or large solution.

  • Business Model

    Business Model

    The business model for an organization or a client provides deep understanding of how a solution or architecture impacts the customers, members, or citizens. It provides a perfect starting point for architects to design innovative outcomes and impact the core business of the organization. Resources: Digital Business Models: https://itabok.iasaglobal.org/itabok3_0/digital-outcome-model/business-models/ Business Model Canvas LS: https://itabok.iasaglobal.org/business-model-canvas/ Business..Read More

  • Personas

    Personas

    The customer persona helps create a deep understanding of the customer.

  • Customer Journey

    Customer Journey

    Once the customer personas are identified it is possible to map out their journey. The journey map is one of the most useful tools in understanding a solution, the services it needs and the final MVP (minimum valuable product). In addition CJs can provide many areas for innovation. They also are a great tool for..Read More

  • Business Capabilities

    Business Capabilities

    The business capabilities are awesome tools for developing an understanding a businesses operating model. Business capabilities are a way of organizing business activities into people, process and technology and provide an excellent tool for understanding business benefits and measures when used with OKRs and other strategic tools. Resources Business Capabilities Article: https://itabok.iasaglobal.org/itabok3_0/Business-Capabilities Business Capabilities LS:..Read More

  • Service Blueprints

    Service Blueprints

    The service blueprint aligns capabilities with services. At Iasa, services are capabilities that are managed by contract and that can be delivered via technology. Thus services are directly mapped to technical implementations in many cases. Using service blueprints an architect can decompose a service into layers of activity for the customer, the business and the..Read More

  • Roadmaps

    Roadmaps

    Roadmapping provides the architecture practice a clear runway for dependencies, major events (business and technical) and planning. Roadmapping is also critical to investment prioritization and planning based on lean business cases. The goal of the roadmap is to create a living description of the the elements of architecture and how they will roll out over..Read More

  • Objective Key Results

    Objective Key Results

    Objectives and key results is a technique used to derive measurements of success and goals on a specific set of capabilities and the enterprise. Resources Goals – this article outlines the use of OKRs and KPIs to drive outcomes. Value Management – this article describes methods for describing and deriving value Learning shot: https://itabok.iasaglobal.org/valuation/

  • Business Case

    Business Case

    The business case provides a codified set of benefits, costs and considerations for a product/project. The ITABoK uses a lean business case tool called the NABC (need, approach, benefits, considerations). This tool is used as an input to prioritization and roadmapping though there is considerable overlap and concurrency in their development. In addition LBC take..Read More

  • Team Design

    Team Design

    Product and project team assignments and structure are deeply important to the success of any solution. Aligning the competencies of the architect(s) and the team(s) will have a huge impact on the outcomes. The goal of the Team Designer, Assignments and prioritization activities go together very well whether using agile or more traditional methods of..Read More

  • Stakeholder Management

    Stakeholder Management

    The ITABoK is driven by a Stakeholder Led Approach which provides many tools for the architect and team to create a rigorous stakeholder community. Resources Stakeholder article: https://itabok.iasaglobal.org/itabok3_0/Stakeholders Organization article: https://itabok.iasaglobal.org/itabok3_0/Organization Stakeholder Approach LS: https://itabok.iasaglobal.org/stakeholder-driven-approach/

  • Requirements

    Requirements

    Requirements management is a full art and science but what the architect is interested in are Architecturally Signficant Requirements. These requirements come in many shapes and sizes but the architect is interested in requirements that impact structural issues (mostly quality attributes), value (measurable benefits and cost), and constraints (standards, compliance, risk). Resources Article: https://itabok.iasaglobal.org/itabok3_0/Requirements Learning..Read More

  • Options

    Options

    Options are included hear separately but form part of the ITABoK Design Triumvirate (requirements, options, decisions). Understanding and identifying options for a particular design decision is a part of understanding the industry and maintaining and healthy current knowledge base of available technology and strategy offerings. We have included a modern architecture landscape which includes options..Read More

  • Decisions

    Decisions

    Decisions are the heart of architecture. Understanding why a decision was made, how it impacts the solution, how it interacts with other decisions is the core of a great architecture. Being able to trace decisions to cost, benefit and outcome is the pinnacle of delivery and design. The ITABoK is centered on making decisions easier,..Read More

  • Quality Attributes

    Quality Attributes

    Quality Attributes are the cross-cutting concerns of an architecture related to its structure and quality attribute requirements. Scalability, usability, flexibility, etc are all considered as a part of the quality attribute assessments and design activities. Each area impacts the others so quality attribute design can be a very powerful tool in understanding the overall functioning..Read More

  • Viewpoints

    Viewpoints

    Views and Viewpoints give the architect different ways to look at an architecture using different decision making and design paradigms. For example, one might look at the information view of an architecture to understand the data, information and entities in the system or systems. The availability of views is a hallmark of great architecture thinking..Read More

  • Agile DevOps

    Agile DevOps

    Agile DevOps delivery is the heart of most development and IT shops. The ITABoK makes plenty of room for both agile and traditional methods. The basis for the ITABoK is bottom up architecture, meaning architects are actively involved during delivery not in up front design. This means that architects are actively engaged with teams, projects,..Read More

  • Assessment

    Assessment

    Architecture Assessments are the methods employed to design, review and assess architecture choices against options and to review the choices made in relation to the outcomes expected in the product/project. The goals of assessment are to find missing elements of architecture, things that wont meet quality attribute requirements or design tradeoffs that are not effective..Read More

  • Usage and Value

    Usage and Value

    Usage and Value is achieved after a product/project is deployed. Many architects and organizations ignore the measurements of how well the product measures against the objects and key results that were used to justify it in the first place. The ITABoK heavily suggests usage information measured on dashboards against OKRs in retrospectives against the deployed..Read More


The Red Thread

For smaller solutions and products, the Red Thread will generally be enough to ensure the product delivers value and is aligned with the technology strategy and outcomes of the organization.

Preloader
  • Introduction

    Introduction

    The red thread represents the minimum architecture steps which provide traceability, rigorous decision making and value management measured against real business outcomes.

  • Objective Key Results

    Objective Key Results

    Objectives and key results is a technique used to derive measurements of success and goals on a specific set of capabilities and the enterprise. Resources Goals – this article outlines the use of OKRs and KPIs to drive outcomes. Value Management – this article describes methods for describing and deriving value Learning shot: https://itabok.iasaglobal.org/valuation/

  • Business Case

    Business Case

    The business case provides a codified set of benefits, costs and considerations for a product/project. The ITABoK uses a lean business case tool called the NABC (need, approach, benefits, considerations). This tool is used as an input to prioritization and roadmapping though there is considerable overlap and concurrency in their development. In addition LBC take..Read More

  • Requirements

    Requirements

    Requirements management is a full art and science but what the architect is interested in are Architecturally Signficant Requirements. These requirements come in many shapes and sizes but the architect is interested in requirements that impact structural issues (mostly quality attributes), value (measurable benefits and cost), and constraints (standards, compliance, risk). Resources Article: https://itabok.iasaglobal.org/itabok3_0/Requirements Learning..Read More

  • Options

    Options

    Options are included hear separately but form part of the ITABoK Design Triumvirate (requirements, options, decisions). Understanding and identifying options for a particular design decision is a part of understanding the industry and maintaining and healthy current knowledge base of available technology and strategy offerings. We have included a modern architecture landscape which includes options..Read More

  • Decisions

    Decisions

    Decisions are the heart of architecture. Understanding why a decision was made, how it impacts the solution, how it interacts with other decisions is the core of a great architecture. Being able to trace decisions to cost, benefit and outcome is the pinnacle of delivery and design. The ITABoK is centered on making decisions easier,..Read More

  • Quality Attributes

    Quality Attributes

    Quality Attributes are the cross-cutting concerns of an architecture related to its structure and quality attribute requirements. Scalability, usability, flexibility, etc are all considered as a part of the quality attribute assessments and design activities. Each area impacts the others so quality attribute design can be a very powerful tool in understanding the overall functioning..Read More

  • Viewpoints

    Viewpoints

    Views and Viewpoints give the architect different ways to look at an architecture using different decision making and design paradigms. For example, one might look at the information view of an architecture to understand the data, information and entities in the system or systems. The availability of views is a hallmark of great architecture thinking..Read More

  • Agile DevOps

    Agile DevOps

    Agile DevOps delivery is the heart of most development and IT shops. The ITABoK makes plenty of room for both agile and traditional methods. The basis for the ITABoK is bottom up architecture, meaning architects are actively involved during delivery not in up front design. This means that architects are actively engaged with teams, projects,..Read More

  • Usage and Value

    Usage and Value

    Usage and Value is achieved after a product/project is deployed. Many architects and organizations ignore the measurements of how well the product measures against the objects and key results that were used to justify it in the first place. The ITABoK heavily suggests usage information measured on dashboards against OKRs in retrospectives against the deployed..Read More

Building an Engagement Model

What is essential in understanding the architecture engagement model and its relationship to digital transformation is that the architect team is the primary driver for true digital transformation. The team is not the only party involved in delivering such fundamental changes in the enterprise but is the core professional kernel of that activity.

The engagement model is divided into three primary rings  which represent the architect team mandate, the components they use, and the outcomes that the enterprise will achieve achieve if the team delivers.
You may utilize the engagement model in two primary ways. First click on any element in the engagement model be taken to directly to  that section. The second way is to use the navigation on the right to journey through the implementation of an engagement model.