Statement of Architecture Work
<insert initiative name here>
Info-Tech Research Group tools and template documents are provided for the free and unrestricted use of subscribers to
Info-Tech Research Group services. These documents are intended to supply general information only, not specific
professional or personal advice, and are not intended to be used as a substitute for any kind of professional advice. Use
this document either in whole or in part as a basis and guide for document creation. To customize this document with
corporate marks and titles, simply replace the Info-Tech information in the Footer fields of this document.
Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice.
Info-Tech’s products and services combine actionable insight and relevant advice with
ready-to-use tools and templates that cover the full spectrum of IT concerns.
© 1997-2014 Info-Tech Research Group Inc.
Info-Tech Research Group
1
Introduction: How to use this template
1.22
Use Statement of Architecture Work to get funding and secure resources to
work on the envisioned EA engagement.
Step 1.22.1: Use this template to create a Statement of
Architecture Work document. Append your EA Vision
Document to the Statement of Architecture Work.
Step 1.22.2: Present the Statement of Architecture Work
document to your key stakeholders for the enterprise
architecture work (identified earlier). Obtain formal sign-off.
Delete all information where text is colored GREY (such as
this paragraph). Fill in or delete all form fields shaded in
GREY. Change all necessary text to BLACK before printing
or sending.
Info-Tech recommends including the following content in the
Statement of Architecture Work document:
• Executive summary.
• Engagement scope (defined in the EA Vision document).
• Scope management procedure.
• Engagement deliverables.
• Engagement schedule.
• Engagement team structure.
• Engagement cost estimate.
• Assumptions.
• Sign-offs.
Info-Tech Insights
1. Think of your Statement of Architecture Work as of a
contract between the EA team and EA stakeholders.
2. Define a formal scope management procedure, include it
into the Statement of Architecture Work, and follow it
closely to prevent scope creep.
Info-Tech Research Group
2
Revision history
This section is used to document any changes made to the original Statement of Architecture Work. Use the table below to
organize and track the development and distribution of the Statement of Architecture Work up until the end of the
engagement.
Sample revision history:
Version
1.0
Revision Date
06/02/2012
Author/Editor
Joe Smith
Comments
Original document
Info-Tech Research Group
3
Executive summary
An introduction describing the purpose of the Statement of Architecture Work and defining the
Enterprise Architecture development engagement name and/or number.
Sample Executive Summary:
•
Purpose:
o This Statement of Architecture Work outlines the objectives and scope of the Enterprise Architecture engagement as
well as the necessary resources to complete the development and execution of the engagement.
•
Engagement Name:
o Post-merger integration
•
Engagement Number.
•
Architecture effort request and background.
Info-Tech Research Group
4
Engagement scope
The scope of this Enterprise Architecture Engagement defined in the Appendix A, Enterprise Architecture Vision.
Info-Tech Research Group
5
Scope management procedure
• Any requested changes to the scope of this engagement must be submitted <choose applicable methods: in writing/by
email/using the Change Request form>.
• The engagement lead must assess the impact and cost of the requested change on the engagement schedule and submit
this information along with the request to the engagement sponsor within <insert the number of days> days of receiving the
request.
• The engagement sponsor must make a decision and communicate it to the EA engagement team and the requestor of the
scope change.
• In the scope of this engagement, the engagement team shall address only those changes that were requested in
compliance with this scope management procedure and approved by the engagement sponsor. All other requested scope
changes shall be deemed outside of the scope of this engagement.
Info-Tech Research Group
6
Engagement deliverables
This section contains a list of Enterprise Architecture engagement deliverables that will collectively define Enterprise
Architecture scope, level of detail, planning horizon and the number of alternative options to be considered.
Sample deliverables:
#
File Name
Format
Description
1
Executive Summary
PowerPoint
Contains a high-level outline and summary of the Enterprise Architecture.
2
Reference Architecture
Visio and Word
Architectural description of the target state of the in-scope enterprise.
3
Weekly Status Update
PowerPoint (.pptx)
Includes summary of Enterprise Architecture development progress.
Info-Tech Research Group
7
Engagement schedule
The engagement approach outlines the timeline of the engagement, and includes milestones, target dates, activities, and
outputs that are to be completed by a certain time. An Enterprise Architecture can consist of one or more work streams (e.g.
applications strategy, technology strategy, etc.) and each will have its own milestones and deliverables.
Outputs
Activities
Milestones
Sample approach:
July 30, 2014
Aug 6, 2014
Aug 13, 2014
Aug 20, 2014
Aug 27, 2014
Phase 1:
Understand Enterprise
Direction
Phase 2:
Assess Current
Environment
Phase 3:
Define Targets and Gaps
Phase 4:
Define Strategic
Roadmap
Phase 5:
Communicate Enterprise
Architecture
Applications Strategy
Workshop 1
Infrastructure Strategy
Workshop 1
Applications Strategy
Workshop 2
Infrastructure Strategy
Workshop 2
Executive Review 1
• Engagement kick-off
meeting
• Interviews with key
stakeholders
• Gather existing data for
success metrics
• IT assessment and
brainstorming
• Interviews with key
stakeholders
• Corporate Goals
Analysis
• PEST analysis
• Emerging Trends
Assessment
• Goals and Target State
Analysis
• IT Self-Assessment
Scorecard
• IT Performance by
Business Unit
• Prioritize Top Areas of
Need
Applications Strategy
Workshop 3
Infrastructure Strategy
Workshop 3
Executive Review 2
Applications Strategy
Workshop 4
Infrastructure Strategy
Workshop 4
Executive Review 3
Enterprise Architecture
Document Review Meeting
• Draft specific
communications
packages for each
stakeholder group
• Top Business-IT Goals
• Goals Analysis
• Detailed Action Plan for
Goals
• IT Organizational Plan
• IT Target Capability Cost
Analysis
• IT Target Capability Risk
Assessment
• IT Strategic Roadmap
• Target State Reference
Architecture Blueprint
Info-Tech Research Group
8
Engagement team structure
An organizational chart depicting the team structure for the Enterprise Architecture development engagement, including
engagement sponsor(s), steering committee, engagement lead, core team, subject matter advisors, working committee
(workshop participants from the business and IT); and a table that defines responsibilities, authorities, and estimated effort
required.
Sample team structure:
Executive committee
• VP Architecture: Carl Rippy
• VP Development: Rodney Wurth
• VP Operations: Sarah Forest
•
•
•
•
•
Engagement sponsor
• Chief Information Officer: Joe Smith
Working committee
Engagement core team
Subject matter advisors
Director of Operations: Edward Eng
Director of Finance: Ryan Fuentes
Director of HR: Adrienne Tardif
Director of IT: Jacob Brim
Chief Architect: Jack Fore
• Engagement Lead: Nancy Jones
• Strategy Specialist 1: Theresa Sadler
• Strategy Specialist 2: Eric Goddard
• Subject Matter Advisor 1: Juan Silvia
• Subject Matter Advisor 2: Rod Dahl
Info-Tech Research Group
9
Engagement team structure
Name
Role
Responsibilities
Effort
Joe Smith
Engagement Sponsor
Provide executive support.
Authorize funding and approve the Statement of
Architecture Work.
4 hrs/week
Executive Committee
Carl Rippy
VP Architecture
Rodney Wurth
VP Development
Sarah Forest
VP Operations
4 hrs/week
Provide executive support.
Monitor the progress of Enterprise Architecture
development and help resolve issues.
4 hrs/week
4 hrs/week
Engagement Core Team
Nancy Jones
Engagement Lead
Manage day-to-day execution.
Create and distribute status reports.
Escalate issues to executive committee/engagement
sponsor in a timely manner.
Theresa Sadler
Strategy Specialist 1
Produce applications strategy deliverables.
40 hrs/week
Eric Goddard
Strategy Specialist 2
Produce Infrastructure Strategy deliverables.
40 hrs/week
40 hrs/week
Subject Matter Advisors
Juan Silvia
Subject Matter Advisor 1
Provide expertise in applications strategy.
Rod Dahl
Subject Matter Advisor 2
Provide expertise in Infrastructure Strategy.
16 hrs/week
Working Committee
Edward Eng
Director of Operations
Jacob Brim
Director of IT
Jack Fore
Chief Architect
Participate in workshops.
Provide input for current state analysis.
Validate that the Enterprise Architecture under
development is appropriate and realistic.
20 hrs/week
20 hrs/week
20 hrs/week
Info-Tech Research Group
10
Engagement cost estimate
This section outlines the estimated cost of the engagement. Optionally, you can include the working committee’s time as part
of the cost estimate.
Sample estimate:
Role
Effort (hrs)
Rate ($/hr)
Cost ($)
Notes
Engagement Team
Engagement Lead
200
$100/hr
$20,000
40 hrs/week * 5 weeks
Strategy Specialist 1
200
$75/hr
$15,000
40 hrs/week * 5 weeks
Strategy Specialist 2
200
$75/hr
$15,000
40 hrs/week * 5 weeks
Subject Matter Advisor 1
90
$150/hr
$13,500
16 hrs/week * 5 weeks
Subject Matter Advisor 2
90
$150/hr
$13,500
16 hrs/week * 5 weeks
Working Committee
Director of Operations
100
$90/hr
$9,000
20 hrs/week * 5 weeks
Director of Finance
100
$110/hr
$11,000
20 hrs/week * 5 weeks
Director of HR
100
$90/hr
$9,000
20 hrs/week * 5 weeks
Director of IT
100
$100/hr
$10,000
20 hrs/week * 5 weeks
Chief Architect
100
$90/hr
$9,000
20 hrs/week * 5 weeks
TOTAL
1280
$125,000
252 hrs/week * 5 weeks
• The total cost of the engagement is estimated to be $125,000.
Info-Tech Research Group
11
Engagement assumptions
This section outlines the assumptions under which the estimates of the engagement timeline, cost, and staffing requirements
are drawn, e.g. resource availability, existing documentation.
Sample assumptions:
• Resources (i.e. time, documentation) from business leaders and organizational teams will be made available as necessary
to assess viability and impact of future Enterprise Architecture initiatives.
• An agreement can be reached with external consultants to provide additional expertise in needed areas.
• The engagement team is fully staffed as requested, and all new hires, including external consultants, will be onboarded by
[DATE].
• Data for existing success metrics will be available.
Info-Tech Research Group
12
Statement of Architecture Work sign-offs
This section contains the signatures of the engagement sponsor, engagement manager, and other key stakeholders,
signifying their agreement to the content of the Statement of Architecture Work as well as their level of contribution to the
engagement as outlined in the Statement of Architecture Work.
We hereby recommend the Statement of Architecture Work in its entirety (including Appendix A, Enterprise Architecture
Vision):
Signature: __________________
Date: __________________
Name and Title:__________________
Signature: __________________
Signature: __________________
Date: __________________
Name and Title:__________________
Date: __________________
Name and Title:__________________
Signature: __________________
Date: __________________
Name and Title:__________________
I hereby accept the Statement of Architecture Work in its entirety (including Appendix A, Enterprise Architecture Vision), and
authorize the engagement execution:
Signature: __________________
Date: __________________
Name and Title:__________________
Info-Tech Research Group
13
Appendix A: Enterprise Architecture Vision
Append the Enterprise Architecture Vision Document to this Statement of Architecture Work.
Info-Tech Research Group
14