guiding agile solution delivery with the archimate language
TRANSCRIPT
1
Guiding Agile Solution Delivery With the ArchiMate® Language Iver Band and Chris McCurdy February 4, 2015 Open Group Conference, San Diego California
© 2015 Cambia Health Solutions, Inc.
2 2
Agenda
•Introduction •Elaboration of Solution Architectures •Best Practices •Your Questions?
© 2015 Cambia Health Solutions, Inc.
3 3 © 2015 Cambia Health Solutions, Inc.
Iver Band
• Enterprise Architect at Cambia Health Solutions
• Health Insurance Consumer Experience, Mobile Technology, Provider and Network Management, Architecture Tools and Techniques
• Vice Chair, Open Group ArchiMate Forum
• Co-Chair and Co-Founder, Oregon Enterprise Architects
• TOGAF and ArchiMate certified, CISSP, Certified Information Professional
http://www.linkedin.com/in/iverpdx http://www.cambiahealth.com/ http://www.twitter.com/iverband
4 4
Chris McCurdy
© 2015 Cambia Health Solutions, Inc.
http://www.linkedin.com/in/christophermccurdy http://www.cambiahealth.com/
Chris McCurdy:
• IT Architect at Cambia Health Solutions
• Architecture processes, operations and tools
• TOGAF and ArchiMate Certified
5 5
INTRODUCTION
© 2015 Cambia Health Solutions, Inc.
6 6 © 2015 Cambia Health Solutions, Inc.
Our Roots Born from an inspired idea
Our Cause Becoming catalysts for transformation
Our Vision Delivering a reimagined health care experience
Our Story
7 7 © 2015 Cambia Health Solutions, Inc.
8 8
About Cambia
22 companies and growing
© 2015 Cambia Health Solutions, Inc.
A tax-paying nonprofit headquartered in
the Pacific Northwest
Nationally recognized: Top 100 Healthiest
Workplaces
5,300 employees in 30 states
100 million people touched nationwide
9 9
Cambia Health Solutions
© 2015 Cambia Health Solutions, Inc.
Senior Services
Health Insurance
Retail Enablement
Provider Enablement
10 10 © 2015 Cambia Health Solutions, Inc.
Wholly Owned Companies Direct Investment Companies Health Insurance
Direct Investment Companies Health Insurance Wholly Owned
Companies
Cambia Health Solutions
11 11
What is Enterprise Architecture? • A product
• A design that shows the coherence between products, processes, organization, information supply and infrastructure, based on a vision and certain explicit starting points, principles and preferences
• A practice • Way of working
• Aimed at the development and use of enterprise architectures within an enterprise
• With people and resources
11
12 12
TOGAF® - The Open Group Architecture Framework
12
13 13
What is the ArchiMate® Language? • A language for building understanding, and
communicating and managing change • A graphical notation with formal semantics • A framework that describes and relates
business, application, and technology layers • Extensions for modeling motivation as well as
implementation and migration • Techniques for visualizations and analyses for
different stakeholders • An open standard managed by The Open Group
13
14 14
Business
Application
Technology
Motivation
TOGAF, ArchiMate Core and Extensions
14
Preliminary
D Technology Architecture
Requirements Management
A Architecture
Vision B
Business Architecture
C Information
Systems Architectures
H Architecture
Change Management
G Implementation
Governance
F Migration Planning E
Opportunities and
Solutions
TOGAF ADM
ArchiMate Core
Business Architecture
Application Architecture
Data Architecture
Technology Architecture
15 15
What is Agile Solution Delivery? • A group of methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams
• These methods promote adaptive planning, evolutionary development, early delivery and continuous improvement
• They encourage rapid and flexible response to change • Often, agile methods that work with small teams must be layered and augmented to enable large enterprises to deliver complex solutions
• The Scaled Agile Framework is one approach to this challenge
© 2015 Cambia Health Solutions, Inc.
Adapted from http://en.wikipedia.org/wiki/Agile_software_development
16 16
ELABORATION OF SOLUTION ARCHITECTURES
© 2015 Cambia Health Solutions, Inc.
17 17
Elaboration of Solution Architectures • Implementation analysts and engineers focused on data,
process, software and infrastructure typically elaborate solution architectures
• Solution architects can use the ArchiMate language to express their own decisions precisely, and to indicate what decisions are left to others
• Analysts and engineers can then update the model with the decisions they have made
• With the right tooling and repository, the implementation decisions can be traced
• Back to the solution architecture
• Forward to the design and code
© 2015 Cambia Health Solutions, Inc.
18 18
Some Elaboration Techniques To Answer Common Questions
© 2015 Cambia Health Solutions, Inc.
Question Technique
Why we doing this? Motivation View Creation
What do the requirements mean in detail? Requirements Elaboration
How can we satisfy the requirements? Requirements Realization
How do we develop the solution in stages? Sprint-Based Roadmapping
What system states will satisfy the requirements?
Requirement Realization Roadmapping
What are the contents of each plateau? Plateau Decomposition
When should we develop that feature? Sprint-Based Roadmap Elaboration
What is the structure and behavior of this component?
Application Component Elaboration
What infrastructure do we need? Infrastructure Usage View Creation
What must we develop in the next sprint? Gap Analysis
19 19
Case Study: Improving Project Management Tooling In Response to The Changing Role Of The Consumer
20 20
Current State: Disconnected Project Management Toolset Hampers Decision-Making and Execution
© 2015 Cambia Health Solutions, Inc.
21 21
Motivation View of US Healthcare Payer Challenges
21
Drivers from Gartner Group “Business Drivers of Technology Decisions for Healthcare Payers, 2015”, December 2013
22 22
Future State: Integrated Project Management Toolset Enables Better Decisions and More Efficient Execution
22
23 23
What do the requirements mean in detail?
© 2015 Cambia Health Solutions, Inc.
Requirements Elaboration
24 24
Requirements Realization
© 2015 Cambia Health Solutions, Inc.
How can we satisfy the requirements?
25 25
Sprint-Based Roadmapping
© 2015 Cambia Health Solutions, Inc.
How do we develop the solution in stages?
26 26
Requirements Realization Roadmapping
© 2015 Cambia Health Solutions, Inc.
What system states will satisfy the requirements?
27 27
Plateau Decomposition
© 2015 Cambia Health Solutions, Inc.
What are the contents of each plateau?
28 28
Sprint-Based Roadmap Elaboration
© 2015 Cambia Health Solutions, Inc.
When should we develop that feature?
29 29
Application Component Elaboration
© 2015 Cambia Health Solutions, Inc.
What is the structure and behavior of this component?
30 30
Feature Manager Component Elaboration
© 2015 Cambia Health Solutions, Inc.
What does this component really do?
31 31
Infrastructure Usage View
© 2015 Cambia Health Solutions, Inc.
What infrastructure do we need?
32 32
Gap Analysis: Start of Next Sprint
© 2015 Cambia Health Solutions, Inc.
What must we develop in the next sprint?
33 33
Best Practices
34 34
Getting Started With ArchiMate Modeling
© 2015 Cambia Health Solutions, Inc.
• Get trained in ArchiMate • Self-study is a possibility for experienced architects
and modelers, preferably with an experienced ArchiMate mentor
• Begin with a small number of standard ArchiMate viewpoints
• Develop and refine models in small groups • Keep most views simple, coherent and focused
• The occasional big picture poster in high-traffic areas can promote understanding and discussion
• Consider the arrangement, color, proximity, relative size, and visual flow of view elements
• Use legends, glossaries and explanations to broaden understanding
35 35
ArchiMate Modeling in Your Organization • Model only what is necessary to address stakeholder
concerns, make investment decisions and drive delivery • Automate repository population whenever possible • Peer-review ArchiMate models before publishing them • Publish models in a version-controlled repository that
allows models to reference each other • Do not commit to group tooling prematurely. Use
existing or free tools until you have a good idea of how you will use ArchiMate
• Do the right type of modeling for each situation • Sometimes catalogs, matrices or free-form diagrams
are best • Use appropriate languages for design, e.g. UML,
ERD, BPMN © 2015 Cambia Health Solutions, Inc.
36 36
Example Architecture and Design Modeling Responsibilities
© 2015 Cambia Health Solutions, Inc.
*Information Structure Views
Business Process Models
*Enterprise Data Model Business Capabilities
*Information Structure Views
Value Streams
Business Process Views with Capability Linkages
Application Cooperation Views
Infrastructure Usage Views
Infrastructure Views
Software Designs
Business Process Views with Application Service Usage
*Data Models
Business Architecture Managed Models
Business Architecture Deliverables
Project Delivery Team Design Responsibilities
IT Architecture Deliverables
Business Roadmaps: Motivation Views and Implementation and Migration Views
Solution Roadmaps: Motivation Views and Implementation and Migration Views
*Responsibility shared with data architecture and analysis practices
37 37
Your Questions?