• Develop business case for an IT architecture for presentation to Organization Executives
• Understand the scope of the IT architecture project (identify and include in project scope the technology directions and architecture planning and development efforts within Organization and Data Center)
• Identify "quick hit" success to rebuild business unit confidence in the IT organization.
• Craft a communications plan for soliciting and maintaining business unit involvement in the IT architecture process
• Enlist the required business unit and IT Organization resources to staff the IT architecture team
• Define IT architecture team members’ roles and responsibilities
• Assess the architecture team’s resource requirements going forward
• Establish the IT architecture team’s dynamics and norms
• Identify Organization project resources (IT and business unit)
• Create project timelines
• Complete the project budgets.

Completion of Project Planning Deliverables:

• Project organization chart
• Weekly status reports
• Presentation framework for technology forums (used to gain feedback from the project team, IT Steering Committee, Executive Committee and Branches)
• Technology bulletins
• Published project work on Organization’s Intranet.

• Review of baseline projects
• Project timeline
• Resource requirements matrix
• Specifies Enterprise-wide Technical Architecture continuation efforts and expectations of Branch participation
• Project budget by phase.

• Benefits analysis that identifies proposed value-added for the Enterprise
• Identification of quick-hit successes that help enable Branch buy-in
• Helps establish commitment to the continuation of the Architecture project by all major business areas and IT (Executive level)
• Identify integration efforts required for existing architecture projects.
• Defines level of detail required by Branches and IT Organization for each of the Architecture technology components
• Standards
• "Buy-lists"
• Procurement policies and procedures
• Procurement decision-making and authority
• Required detail of "buy-list" recommendations.
• Identification of critical success factors by Branch and IT Organization.

Project Proposal (sales document)

• Defines what the Architecture project and deliverables do not include
• Provides a complete Architecture deliverable "look and feel" template
• Outlines deliverables by phase
• Specifies level of commitment for the project team and business-area participants
• Identifies costs by phase
• Signed approval required to move forward.

The Phase I deliverable will identify the Business Drivers for an Enterprise-wide IT Architecture, and will include, at minimum, the following sections:

• Executive Summary(s) - covering the extent of the contract services and deliverables provided and approved for this phase during the partial or full term of the contract.
• Business Drivers
• Problem Statement
• Strategic Business Drivers
• Architecture Requirements
• Relevant Technology Trends report
• Architecture Vision
• Benefits.

The Phase II deliverable will document the Technical Architecture and will include, at minimum, the following sections:

• Executive Summary(s) - covering the extent of the contract services and deliverables provided and approved for this phase during the partial or full term of the contract.
• Conceptual Architecture
• Purpose
• Linkage to Business Case
• Conceptual Architecture Definitions.
• Defining and Documenting the Enterprise-wide Domain and Component Technical Architectures, including, but not limited to:
• Domain Definition
• Technology Components
• Principles
• Best Practices
• Recommendations for Target Architecture
• Technology Standards
• Technology Products/Vendors.
• Defining and Documenting the Baseline Architecture—in a form agreed to by Organization IT Branch
• Completion of a Gap Analysis—in a form agreed to by Organization IT Branch.

Includes leading and facilitating additional team discussions and meetings and producing weekly status reports.

The Phase II Augmentation deliverable will document the Technical Architecture for The XYZ Component and will include, at minimum, the following sections:

• Executive Summary(s) - covering the extent of the contract services and deliverables provided and approved for this phase during the partial or full term of the contract.
• Conceptual Architecture, linkage with the core Architecture Project, to provide and validate the following:
• Purpose
• Linkage to Business Case
• Conceptual Architecture Definitions.
• Defining and Documenting the Component Technical Architectures, including, but not limited to:
• Technology Components
• Design Principles
• Best Practices
• Recommendations for Target Architecture
• Technology Standards
• Technology Products/Vendors, utilizing the product "buy-list" process.
• Defining and Documenting the Component Baseline Architecture (existing)—in a form agreed to by the organization's IT management.
• Completion of a Gap Analysis—in a form agreed to by the organization's IT management.
• Providing a high-level Component migration strategy.

The Phase III deliverable will document the Migration Plan and Governance Strategies for Organization’s IT Architecture. It includes, at minimum, the following sections:

• Executive Summary(s) - covering the extent of the contract services and deliverables provided and approved for this phase during the partial or full term of the contract.
• Developing the Migration Strategy Report, including, but not limited to:
• Cost Analysis
• Resources Required
• Migration Timeline
• IT Architecture Review Plan
• Next Steps.
• Developing a report on the Product Selection Process
• Developing the Governance Strategies, including, but not limited to:
• Recommended methods to ensure compliance
• Determine the frequency of architecture reviews
• Identify how and when to modify the architecture.
• Formalize and document the consensus building process used for the ArchitectureP for general use
• Facilitating the integration of the Architecture into the organization and projects
• Advise the Organization senior managers on the organizational impact of, and the integration required by, the Architecture
• Advise the Organization senior managers on the methodology/process impact of the Architecture
• Advise the Organization project managers and senior managers on the execution of the Architecture’s migration plan
• Coach and advise the Organization’s Architecture team in the use of the application development component architecture as it applies to new development efforts
• Develop and publish the Organization’s Application Architecture Models.

The deliverables in Phase 0 fall under the authorship of the consultant and its practices and quality review. The deliverables indicated above for Phases I-III will be authored by the project team and will be developed according to Organization practices and quality review.

The consultant's role will be as a facilitator and reviewer of the process and its deliverables.

All deliverables will be provided in both paper and electronic forms. Each deliverable also includes a related Executive Summary for the purpose of IT Branch management and executive briefings.

The knowledge, skills and understanding associated with defining an Enterprise-wide IT architecture will be transferred to the Organization project staff. This knowledge transfer includes, but is not limited to: methodology, processes, information resource sources, techniques, tools, deliverables and any other specific capability necessary to establish, maintain and evolve Enterprise-wide technical architecture.