Harmonizing
Requirements and
Business Architecture
Capabilities, Context, and
Connections
In partnership with:
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
Keith Ellis
President & CEO
Enfocus Solutions
0
What are we going to talk about?
• Business Architecture and Business Value
• Requirements are valuable when
Connected and in Context
• Action plan:
o Specific changes in how you do
requirements
o Specific techniques in support
o Other architecture stakeholders
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
1
Enfocus Solutions:
Achieving Business Analysis Outcomes
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
2
Requirements Excellence Framework™
Business Analysis Perspective
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
3
Business Architecture
What is it really?
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
4
When You Think Business Architecture…
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
5
Business Architecture – Enfocus Solution Definition
Ontology
Relationships
(What exists)
IS
Taxonomy
(Dynamic)
Context
View & Viewpoint
(Abstraction)
(is a common way to describe
and classify things)
Has
Content
•
•
•
Capability
Value Stream
Artifacts/models
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
Process
•
•
Scope of use
Governance
Purpose
•
•
•
Alignment
Prioritization
Communication
6
Business Architecture Framework
Customers
Product
Regulators
Business Drivers,
Goals & Strategic
Objectives
Vendors
Application
Inventory
Organization
Initiative/Investment
Inventory
Policy
Location
Roles
Rules
Business Information
Business Use Cases
The business architecture “framework” is a series of models which represent viewpoints
of the business and combine to create a “blueprint”.
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
7
Contrasting Concepts
Tend to talk about
What they are talking about is
Tend to be focused on
Techniques
Business Architecture
Business Analysis
Capabilities
Requirements
(Requirement types)
Stable
Pretty volatile
Planning
Project Execution
(alignment of business and IT)
Value streams, capability
map, gap analysis, etc.
Use Cases, Traceability,
BPMN, Context
diagramming, etc.
Across project teams
In a project team
Tend to work
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
8
What’s the relationship between the two?
The relationship depends on the viewpoint…
Business Architecture
Relationship
Business Analysis
When are you doing “Business Architecture”?
“Creates Structure for”
Before: Using to drive project strategy
and as input to Business Analysis
“Identifies Interdependencies in”
During: Describing how a project scope
fits into the context of an organization
“Assesses Value of”
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
After: Using as part of transition
requirements and value realization
9
Defining the Relationship
Harmonizing Requirements and Business Architecture
Business Architecture
Relationship
“Creates Structure for”
Relationship
Business Analysis
“Identifies Interdependencies in”
?
“Assesses Value of”
How does Business Analysis
change if we harmonize the
two perspectives
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
10
Why is Business Architecture so Critical?
It’s a question of scale!
On a single project:
• I want my analysts to be “proactive”
• I need to identify my project’s stakeholders
• I want improved project outcomes
• I must improve how I identify interdepartmental
requirements
Dozens, Hundreds, or Thousands of Projects or User Stories?
• Exponential interdependency growth
• Complexity is very high
• The description of Scope is always
frustratingly vague
• Can’t roll up critical information
• I’m coordinating large numbers of
increasingly time constrained stakeholders
• Can’t easily deal with cross-divisional
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
11
HARMONIZING
BUSINESS ARCHITECTURE
AND
BUSINESS ANALYSIS:
WHAT’S DIFFERENT
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
12
What are the Major Changes
• Your process of doing requirements
• How you identify stakeholders
• Where you put certain requirements information
• How you communicate SCOPE
• How you approach detailing requirements
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
13
Snapshot of the Typical Requirements Process
Changing the way you do requirements…
Elicit Needs
Develop
Requirements
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
Requirements
Document
Requirements
Validation
Validated
Requirements
Document
14
In the Harmonized World:
You START with what is Impacted
OR
PC-TADPOL
•
•
•
•
•
•
•
•
Capability Map
Impact
Product
Customer
Technology
Application
Data
Process
Organization
Location
OR
In a Business Analysis Repository
Capture the Nature (Issue/Outcome)
and Severity of the Impact
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
15
Establish Your Stakeholders Based on the Impact
Each has:
•
•
•
•
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
Owners
Subject Experts
Constraints
Interdependent initiatives
16
You can even
change your
elicitation
approach
depending on
where the major
areas of impact
are…
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
Process Analysis
is only ONE way
to identify the
features needed
to deliver value
17
Process Models Should not be in “Requirements” Documentation
Separate “Requirements” from “Business Architecture” Artifacts
Enterprise Architectural Models
Process Models
Data Models
System Models
Organization Models
Decision Models
Business Architecture Repository
Business
Process
Enterprise
Data
IT
Services
Stakeholder
Personas
Business
Rules
Process
Impacts
Data
Impacts
IT Service
Impacts
Stakeholder
Impacts
Rule Book
Impacts
Architectural Impact Assessment
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
18
Change How you Communicate Scope
• Need to communicate scope AND
how that scope impacts
(integrates) into the business
context (People, Process,
Technology)
• Need to use this to find the
functionality BETWEEN impacted
entities (this is the stuff that gets
missed)
• How you choose to ORGANIZE and
analyze projects determines what
dependencies you see
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
19
Project Control is About Closing the Communication Gap
What is the ANALYST communicating: What are the viewpoints created?
Business Viewpoint
Ideation to
Feature
•
•
What are the major components of the solution?
What is the problem/need? What is the gap? What is
impacted? What are the tradeoffs? What delivers the value?
“Solution Scope”
Developer Viewpoint
Feature to
Requirements
•
•
What does the solution need to do?
What is right level of detail? What are the priorities? What
visualizations or models to use? Do developers understand?
Can it be tested?
“Solution Requirements”
Transition Viewpoint
Requirements
to Value
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
•
•
Are we building the right solution?
Does the solution conform to the requirements? What is
needed to transition to new solution? Did the solution deliver
value?
“Transition and Solution Validation”
20
Are Analysts Forced to Use Techniques that
Don’t Support Reducing Risk?
70%
60%
How susceptible is
this Project to
REQUIREMENTS
RISK
(How frequently does the
project fail to meet
objectives if an AVERAGE
skill analyst is used)
Significantly re-engineering
the business processes
surrounding application
Reduce transaction
and indirect costs
Reduce direct costs
50%
Communications with employees,
suppliers or customers
40%
35%
30%
Better manage internal
information and access
to information
Launch New
Products
Data should be
clustered along
this line
20%
10%
Regulatory Compliance
(limited process change)
0%
15%
20%
25%
30%
35%
35%
Generally: How frequently do projects fail to meet this
objective?
Source: Business Analysis Benchmark, 2008
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
21
HARMONIZING
ARCHITECTURE AND
BUSINESS ANALYSIS:
WHAT’S DIFFERENT
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
22
Project
Layer
Connected Requirements
Requirements Repository (Project-focus, Transactional, Stakeholder oriented)
Architecture Repository (Planning-focus, Point-in-time snapshot, IT-oriented)
“CONNECTED
REQUIREMENTS”
Enterprise Architecture
Layer
1) Maintain the synchronization
between PLAN and ACTION
layers
2) Facilitate interaction
between the Owners and
Analysts
3) Make it a closed, selfupdating, loop
TOGAF
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
23
Architects Want the Opposite View…
Tell me all the things that impact the enterprise objects
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
24
Enterprise Data Traceability
Manage reusable product/services, business processes, business
rules, and stakeholder personas used by all projects
Diagram shows all related projects, features, requirements, etc. for one product/service in enterprise portfolio
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
25
What are we going to talk about?
• Business Architecture and Business Value
• Requirements are valuable when
Connected and in Context
• Action plan:
o Specific changes in how you do
requirements
o Specific techniques in support
o Other architecture stakeholders
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
26
REMINDER:
Enfocus Solutions - Achieving Business Analysis Outcomes
(psst… It’s the secret to successful projects)
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
27
Getting the Slides:
Email to: apalten@enfocussolutions.com
Give us a little feedback, and Andrea will be happy to send you
the slide deck
QUESTIONS AND DISCUSSION
PDU/CDU Information
You can submit this course/webinar for PDU/CDU credit to your association by providing them with the following information:
• Webinar Title: Harmonizing Requirements and Business Architecture
• Webinar Date/Time: October 23, 2013 (1:00 eastern)
• Provider: Modern Analyst Media LLC
• Email: webinars@ModernAnalyst.com
• Phone: (818) 284-6800
For PMI, you should select Category B for the live webinar.
For IIBA, use the "Professional Development Other Events" for live webinars. To track your CDUs, please keep track of your "Thank you for
attending this webinar email" as proof you attended the webinar.
© Copyright 2013 Enfocus Solutions Inc. All Rights Reserved.
28