Process Step 2: Define the Segment Scope and Strategic Intent    (3ZDS)

Activity 2.1: Establish segment scope and context    (3ZDT)

Activity Description:    (3ZDU)

This activity consists of identifying at a high-level the segment stakeholders, business domains, common / mission services, information exchanges, systems, security, and technical focus areas in the context of the “segment architecture development purpose statement” from process step 1. Some of these items may not be known at this point. However, the more information that is available to describe the proposed segment scope and formulate a clear understanding with the core team, the better.    (3ZDV)    (3ZDW)

Activity Inputs:    (3ZDX)

Tasks:    (3ZEC)

2.1.1 Review segment architecture development purpose statement    (3ZED)

The core team reviews the problem statement developed in process step 1 with the business owner(s) and executive sponsor to establish a firm understanding of the segment business drivers and mandates associated with the problem statement. The business drivers and mandates are the foundation from which the segment’s performance architecture will be built, demonstrating the linkage to the strategic, business, and investment improvement opportunities identified in subsequent activities and process steps. Business drivers and mandates include factors driving the prioritization and selection of the segment architecture development effort that may include agency strategic plans, policies, executive orders, legislation, budget priorities, and available PART and PAR program assessments.    (3ZEE)

2.1.2 Identify organization components    (3ZEF)

With a firm understanding of the problem statement and the organizations affected by the problem statement, the core team identifies the high-level relationships between the affected organization(s) and the organization components, as well as the relationships between those components, through any number of means, including the review of any existing enterprise architecture (EA) knowledge bases, PAR, and PART reports.    (3ZEG)

Organization components may include, when applicable and available, organization units, business functions and processes, common / mission services, applications, information exchanges. Any known relationships between each of the organization components are also identified within this task.    (3ZEH)

2.1.3 Identify stakeholders    (3ZEI)

This task requires a review of the organization components and the segment architecture development purpose statement in order to identify the segment stakeholders (e.g., consumers, participants, functional representatives). Each stakeholder may have a different perspective on how to overcome the business challenges articulated through the segment architecture development purpose statement. This task includes identifying the appropriate stakeholders and the relationships between them and the servicing organization(s).    (3ZEJ)

2.1.4 Establish segment summary description    (3ZEK)

After identifying the business drivers and mandates (e.g., GAO reports) for the segment, the organization components, and the stakeholders, the core team now establishes a segment summary description. The summary description is the synthesis of these items into a cohesive document that supports the segment architecture development purpose statement. This is a critical task, as it also summarizes the components and stakeholders that are engaged in subsequent activities to elaborate on the business’ needs to meet the intended purpose of the segment.    (3ZEL)

This task also includes augmenting the summary description with an illustration that depicts the current state of the operating environment. The summary description and the illustration provide the scope and context through which the subsequent process steps are bound. Defining segment scope helps build consensus within the core team on the range of strategic improvement opportunities and helps focus core team working sessions. Documenting the current-state operating environment could be depicted visually through a simple current operating environment diagram (e.g., Current state OV-1), which will help to provide a visual context around the problem statement.    (3ZEM)

2.1.5 Validate / approve segment scope and context    (3ZEN)

The core team formalizes the segment scope and context. Taking all available information into consideration, the executive sponsor and business owners validate and approve the parameters that define the segment boundaries.    (3ZEO)

2.1.6 Optional Task – Refine / update scope and context    (3ZEP)

It is understood that a more detailed analysis of the business and information in Process Step 3 and the technology and services in Process Step 4 may warrant adjustments to the segment scope and context. This task consolidates that information for consideration by the executive sponsor and business owners. The goal of this activity is to remain flexible on the scope while avoiding any arbitrary injection of scope creep in the segment architecture development process.    (3ZEQ)

Communications Considerations:    (3ZER)

The segment architect may need to facilitate meetings or provide other communication support to structure the decision-making process that occurs between the core team, executive sponsor, and business owner(s). The executive sponsor can be consulted to develop or adjust the communication strategy by which consensus can best be achieved.    (3ZES)

Activity Outputs:    (3ZET)

Suggested Analytical Techniques:    (3ZEY)    (3ZF2)

Next Activity: 2.2 /Identify_and_prioritize_strategic_improvement_opportunities    (3ZF3)