Copyright © 2015 ITpreneurs. All rights reserved.
#ITpreneursLIVE Go-To-Market Enablement Session
Agile, TOGAF and
Enterprise Architecture:
Will They Blend?
Copyright © 2015 ITpreneurs. All rights reserved.
Welcome
Copyright © 2015 ITpreneurs. All rights reserved.
Low Barrier & High Impact:
How ITpreneurs can help increase revenues and save costs
Stay on the Cutting-Edge
Access a Comprehensive Library
Enjoy Convenience
Save content Costs by up to 80%
● No Content Development Costs
● No Content Maintenance Costs
● Lower costs with increased usage
● 1000+ Titles
● Across most IT Domains
● 12 Languages
● Anytime, Anywhere ordering
● Marketing Support
● Exam Services
● Accreditation
● Trainer Services
● First to Market
● Consistent Quality
● Various Delivery Formats
● Always Up-to-Date
● Partner Enablement
Copyright © 2014 ITpreneurs. All rights reserved.
Today’s Speakers
Moderators:
Corjan Bast
Marketing Manager, ITpreneurs
Presenter:
Danny Greefhorst
Enterprise Architecture Expert
Director at ArchiXL
Copyright © 2014 ITpreneurs. All rights reserved.
Today’s Speakers
Presenter:
Danny Greefhorst
Enterprise Architecture Expert
Director at ArchiXL
● Instructor on Enterprise Architecture
● Background in software engineering
● Chair of Via Nova Architectura and
Architecture Section of Dutch Computer Society
● Honorary Medal | Dutch Architecture Forum
● Author of books on architecture principles and digital
transformation
Copyright © 2015 ITpreneurs. All rights reserved.
Agenda
The TOGAF Approach to Enterprise Architecture (EA)
Agile and Scrum
Do Agile, EA and TOGAF Relate?
Do Agile, EA and TOGAF Overlap?
Copyright © 2015 ITpreneurs. All rights reserved.
The TOGAF Approach to
Enterprise Architecture
Copyright © 2015 ITpreneurs. All rights reserved.
Enterprise Architecture (EA)
“Those properties of a thing and its
environment that are necessary and
sufficient for it to be fit for purpose for its
mission” (L. Fehskens)
“Managing the execution of the
corporate strategy” (J. Scott)
“Fundamental concepts or properties of
a system in its environment embodied in
its elements, relationships, and in the
principles of its design and evolution”
(ISO/IEC 42010)
Copyright © 2015 ITpreneurs. All rights reserved.
EA aligns strategy to operations, and
business demand to IT supply, ensuring
changes are in line with strategy and goals
Enterprise Architecture provides insight into
the current and desired state of the
organization, information systems and
technology
EA improves quality of individual solutions,
simplifies their development and
maintenance, and prolonging their life time
Why Enterprise Architecture?
Alignment
Insight
Quality
Copyright © 2015 ITpreneurs. All rights reserved.
TOGAF
● Framework for Enterprise Architecture (EA)
● Originally developed by the US government
in the 80s, now owned by the Open Group
● De facto EA standard in the market
● A description of processes, techniques and
products for EA
● A generic framework that can be tailored to
the situation
Copyright © 2015 ITpreneurs. All rights reserved.
● The core of TOGAF
● A proven way of developing an
architecture
● Specifically designed to address
business requirements
● An iterative method
● A set of architecture views to ensure
that a complex set of requirements
are adequately addressed
TOGAF Architecture Development Method
Copyright © 2015 ITpreneurs. All rights reserved.
How Enterprise Architecture relates to TOGAF
Enterprise Architecture TOGAF
A way of thinking about EA
A detailed description of the
techniques
The knowledge and
experience of practitioners
Other EA frameworks and
techniques (ArchiMate, FEAF,...)
Product-line architecture
Solution architecture
Tactical planning
Business & IT consulting
Architecture
Development Method
+
Guidelines and Techniques
Architecture
Content Framework
Architecture
Capability Framework
Copyright © 2015 ITpreneurs. All rights reserved.
Why TOGAF and TOGAF training?
★ Formal standard, governed by a standardization organization
★ Broadly adapted by user organizations, consultants and IT suppliers
★ Includes formal certification process
★ Broad availability of training
★ Freely available for reading online
★ Based on broad experience and practices
★ Can be adapted to specific organizational context
★ Describes EA process as well as EA content and EA governance
★ You can contribute to the standard
Copyright © 2015 ITpreneurs. All rights reserved.
Agile and Scrum
Copyright © 2015 ITpreneurs. All rights reserved.
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
source: http://agilemanifesto.org
Copyright © 2015 ITpreneurs. All rights reserved.
Principles behind the agile manifesto
● Our highest priority is to satisfy the customer
through early and continuous delivery of
valuable software.
● Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
● Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
● Business people and developers must work
together daily throughout the project.
● Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done.
● The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
● Working software is the primary measure of
progress.
● Agile processes promote sustainable
development. The sponsors, developers, and
users should be able to maintain a constant
pace indefinitely.
● Continuous attention to technical excellence and
good design enhances agility.
● Simplicity--the art of maximizing the amount of
work not done--is essential.
● The best architectures, requirements, and designs
emerge from self-organizing teams.
● At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts its
behavior accordingly.
source: http://agilemanifesto.org
Copyright © 2015 ITpreneurs. All rights reserved.
Scrum
Source: neon rain interactive
Copyright © 2015 ITpreneurs. All rights reserved.
DevOps applies Agile principles to operations
Development IT OperationsDevOps
Copyright © 2015 ITpreneurs. All rights reserved.
Do Agile, EA and
TOGAF Relate?
Copyright © 2015 ITpreneurs. All rights reserved.
Architecture vision
Architecture model
Agile starts where Enterprise Architecture ends
building
block
building
block
Goal
Business
Requirement
Architecture
Principle
Agile project
Application
epic user story
Architecture roadmap
candidate
project
candidate
project
component component
componentcomponent
Copyright © 2015 ITpreneurs. All rights reserved.
Architecture Vision
Architecture model
Agile starts where Enterprise Architecture ends
building
block
building
block
Goal
Business
Requirement
Architecture
Principle
Agile project
Application
epic user story
Architecture roadmap
candidate
project
candidate
project
Pay for order online Pay via Paypal
Increase
customer
satisfaction
Self-service
Customers do not have
direct access to back-
office applications
Portal project
component
componentcomponent
component
Customer Portal
Copyright © 2015 ITpreneurs. All rights reserved.
Positioning EA and Agile
Copyright © 2015 ITpreneurs. All rights reserved.
Scaled Agile Framework
source: http://scaledagileframework.com
Agile is designed for
small teams
Dean Leffingwell
The boys from Rational
Unified Process are back.
Building on the profound
failure of RUP, they are
now pushing the Scaled
Agile Framework as a
simple, one-size fits all
approach to the agile
organization
Ken Schwaber
We do not face,
analyse failures and
limitations of our
assertions, claims,
practices
Philippe Kruchten
Copyright © 2015 ITpreneurs. All rights reserved.
Role of Enterprise Architect in SAFe
source: http://scaledagileframework.com
- maintain holistic vision
- aligns business drivers with
technical decisions
- sets technology standards
- drive common infrastructure
- influences modeling, design
and coding practices
- facilitates reuse of emergent
solutions, knowledge & patterns
- synchronizes issues and NFRs
across solutions
Copyright © 2015 ITpreneurs. All rights reserved.
Scaling Agile @ Spotify
Chief architect
- coordinates work on high-level
architectural issues that cut
across multiple systems
- reviews development of new
systems to make sure they
avoid common mistakes, and
that they are aligned with
architectural vision
- the feedback is always just
suggestions and input - the
decision for the final design of
the system still lies with the
squad building it
source: Henrik Kniberg & Anders Ivarsson, 2012
Copyright © 2015 ITpreneurs. All rights reserved.
What does this mean for training?
There remains a role for Enterprise Architects
○ Need for training on Enterprise Architecture and TOGAF
Some Enterprise Architects will become part of Scrum teams
○ Need for training on Agile and Scrum
People need better understanding of how EA and Agile relate
○ Opportunity for new training and consulting
Copyright © 2015 ITpreneurs. All rights reserved.
Do Agile, EA and
TOGAF Overlap?
Copyright © 2015 ITpreneurs. All rights reserved.
Enterprise Architecture versus Agile?
The “old way” versus the “new way”
Copyright © 2015 ITpreneurs. All rights reserved.
Misconceptions about EA and TOGAF
Copyright © 2015 ITpreneurs. All rights reserved.
Misconceptions about EA and TOGAF
● EA is about modelling everything
● You need to follow all the steps in TOGAF
● Architecture principles are laws that cannot be deviated from
● Developing an EA takes a long time
● TOGAF is a waterfall approach
● EA prescribes things that should be left to the project
Copyright © 2015 ITpreneurs. All rights reserved.
Example architecture principles
● Our highest priority is to satisfy the customer
through early and continuous delivery of valuable
software.
● Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
● Deliver working software frequently, from a couple
of weeks to a couple of months, with a preference
to the shorter timescale.
● Business people and developers must work
together daily throughout the project.
● Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done.
● The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
● Working software is the primary measure of
progress.
● Agile processes promote sustainable
development. The sponsors, developers, and
users should be able to maintain a constant pace
indefinitely.
● Continuous attention to technical excellence and
good design enhances agility.
● Simplicity--the art of maximizing the amount of
work not done--is essential.
● The best architectures, requirements, and designs
emerge from self-organizing teams.
● At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts its
behavior accordingly.
source: http://agilemanifesto.org
Agile is an architecture
Copyright © 2015 ITpreneurs. All rights reserved.
Example architecture model
source: neon rain interactive
Scrum is also an architecture
Copyright © 2015 ITpreneurs. All rights reserved.
Applicability of Agile Manifesto to EA
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
source: http://agilemanifesto.org
Business
outcome
Copyright © 2015 ITpreneurs. All rights reserved.
Applicability of agile principles to EA process
● Our highest priority is to satisfy the customer
through early and continuous delivery of valuable
software.
● Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
● Deliver working software frequently, from a couple
of weeks to a couple of months, with a preference
to the shorter timescale.
● Business people and developers must work
together daily throughout the project.
● Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done.
● The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
● Working software is the primary measure of
progress.
● Agile processes promote sustainable
development. The sponsors, developers, and
users should be able to maintain a constant pace
indefinitely.
● Continuous attention to technical excellence and
good design enhances agility.
● Simplicity--the art of maximizing the amount of
work not done--is essential.
● The best architectures, requirements, and designs
emerge from self-organizing teams.
● At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts its
behavior accordingly.
source: http://agilemanifesto.org
The draft
version of the
architecture
Copyright © 2015 ITpreneurs. All rights reserved.
Our principles for EA
★ Architects focus on what is essential
★ Architects provide concrete and useful results
★ Architects facilitate a collaborative process
★ Architects provide knowledge and skills
★ Architects use reference architectures
★ Architects use open standard methods and techniques
source: http://www.tdan.com/view-articles/16108
Copyright © 2015 ITpreneurs. All rights reserved.
How Enterprise Architecture overlaps with Agile
Enterprise Architecture Agile
Focus on management support
Produces paper and insight
Pre-project
Not necessarily daily
Abstraction
Focus on user support
Produces working software
Project
Daily work
Technical excellence
Iterative
Multi-disciplinary
Mandated business
representative(s)
Collaborative
Soft skills
Only the essentials
Copyright © 2015 ITpreneurs. All rights reserved.
Conclusions
★ Enterprise Architecture provides an Agile project with a vision
★ Agile provides Enterprise Architecture with a good set of principles
★ Agile and Scrum can be seen as reference architectures
Copyright © 2015 ITpreneurs. All rights reserved.
Get Started
Copyright © 2015 ITpreneurs. All rights reserved.
Available Courses
Togaf Level 1
Togaf Level 2
Togaf Practitioner
Agile Scrum Foundation
AgilePM Foundation
AgilePM Practitioner
Certified Scrum Master
Certified Scrum Product Owner
Agile Certified Practitioner
Copyright © 2015 ITpreneurs. All rights reserved.
Business Simulation = The Power of Persuasion
Create business opportunities with Framing the
Future for ENTERPRISE ARCHITECTURE business
simulation.
Framing the Future challenges the participants to
enter into a dialog together on Enterprise
Architecture in relation to the organizational strategy.
The simulation follows a solid instructional design approach to achieve results.
There is a planning phase (what is the plan), and execution phase (building and
deploying), followed by a reflection phase (what happened). During the reflection
phase reference is made to Project management principles and theory, and these
are connected to real life situations of the organization the participants are working
for.
Differentiate Your Offering with Simulations
Your change management toolkit for every organization you work with.
TOGAF
Enterprise
Architecture
View Fact Sheet
Copyright © 2015 ITpreneurs. All rights reserved.
In Development
AgilePM Advanced
Agile Scrum Advanced
Agile for Business Analysts
Managing the Agile Product Development Lifecycle
Planning and Managing Agile Projects
Copyright © 2015 ITpreneurs. All rights reserved.
How You Can Get Started 1/2
Partner
A Full Service
Partner
B Use Your own trainer
Partner
C Only use our Courseware
Courseware Exams Services Trainers
Courseware Exams Services
Courseware Exams
Copyright © 2015 ITpreneurs. All rights reserved.
How You Can Get Started 2/2
Visit the ITpreneurs.com Website
Review the Product of Interest
Get in touch either through the Contact
Form, send us an email, or call!
Copyright © 2015 ITpreneurs. All rights reserved.
Q&A
Copyright © 2014 ITpreneurs. All rights reserved.
+31 107.110.260
corjan.bast@itpreneurs.com
Contact Us
Corjan Bast
Products & Solutions Marketing
ITpreneurs | Rotterdam | The Netherlands

Agile, TOGAF and Enterprise Architecture: Will They Blend?

  • 1.
    Copyright © 2015ITpreneurs. All rights reserved. #ITpreneursLIVE Go-To-Market Enablement Session Agile, TOGAF and Enterprise Architecture: Will They Blend?
  • 2.
    Copyright © 2015ITpreneurs. All rights reserved. Welcome
  • 3.
    Copyright © 2015ITpreneurs. All rights reserved. Low Barrier & High Impact: How ITpreneurs can help increase revenues and save costs Stay on the Cutting-Edge Access a Comprehensive Library Enjoy Convenience Save content Costs by up to 80% ● No Content Development Costs ● No Content Maintenance Costs ● Lower costs with increased usage ● 1000+ Titles ● Across most IT Domains ● 12 Languages ● Anytime, Anywhere ordering ● Marketing Support ● Exam Services ● Accreditation ● Trainer Services ● First to Market ● Consistent Quality ● Various Delivery Formats ● Always Up-to-Date ● Partner Enablement
  • 4.
    Copyright © 2014ITpreneurs. All rights reserved. Today’s Speakers Moderators: Corjan Bast Marketing Manager, ITpreneurs Presenter: Danny Greefhorst Enterprise Architecture Expert Director at ArchiXL
  • 5.
    Copyright © 2014ITpreneurs. All rights reserved. Today’s Speakers Presenter: Danny Greefhorst Enterprise Architecture Expert Director at ArchiXL ● Instructor on Enterprise Architecture ● Background in software engineering ● Chair of Via Nova Architectura and Architecture Section of Dutch Computer Society ● Honorary Medal | Dutch Architecture Forum ● Author of books on architecture principles and digital transformation
  • 6.
    Copyright © 2015ITpreneurs. All rights reserved. Agenda The TOGAF Approach to Enterprise Architecture (EA) Agile and Scrum Do Agile, EA and TOGAF Relate? Do Agile, EA and TOGAF Overlap?
  • 7.
    Copyright © 2015ITpreneurs. All rights reserved. The TOGAF Approach to Enterprise Architecture
  • 8.
    Copyright © 2015ITpreneurs. All rights reserved. Enterprise Architecture (EA) “Those properties of a thing and its environment that are necessary and sufficient for it to be fit for purpose for its mission” (L. Fehskens) “Managing the execution of the corporate strategy” (J. Scott) “Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution” (ISO/IEC 42010)
  • 9.
    Copyright © 2015ITpreneurs. All rights reserved. EA aligns strategy to operations, and business demand to IT supply, ensuring changes are in line with strategy and goals Enterprise Architecture provides insight into the current and desired state of the organization, information systems and technology EA improves quality of individual solutions, simplifies their development and maintenance, and prolonging their life time Why Enterprise Architecture? Alignment Insight Quality
  • 10.
    Copyright © 2015ITpreneurs. All rights reserved. TOGAF ● Framework for Enterprise Architecture (EA) ● Originally developed by the US government in the 80s, now owned by the Open Group ● De facto EA standard in the market ● A description of processes, techniques and products for EA ● A generic framework that can be tailored to the situation
  • 11.
    Copyright © 2015ITpreneurs. All rights reserved. ● The core of TOGAF ● A proven way of developing an architecture ● Specifically designed to address business requirements ● An iterative method ● A set of architecture views to ensure that a complex set of requirements are adequately addressed TOGAF Architecture Development Method
  • 12.
    Copyright © 2015ITpreneurs. All rights reserved. How Enterprise Architecture relates to TOGAF Enterprise Architecture TOGAF A way of thinking about EA A detailed description of the techniques The knowledge and experience of practitioners Other EA frameworks and techniques (ArchiMate, FEAF,...) Product-line architecture Solution architecture Tactical planning Business & IT consulting Architecture Development Method + Guidelines and Techniques Architecture Content Framework Architecture Capability Framework
  • 13.
    Copyright © 2015ITpreneurs. All rights reserved. Why TOGAF and TOGAF training? ★ Formal standard, governed by a standardization organization ★ Broadly adapted by user organizations, consultants and IT suppliers ★ Includes formal certification process ★ Broad availability of training ★ Freely available for reading online ★ Based on broad experience and practices ★ Can be adapted to specific organizational context ★ Describes EA process as well as EA content and EA governance ★ You can contribute to the standard
  • 14.
    Copyright © 2015ITpreneurs. All rights reserved. Agile and Scrum
  • 15.
    Copyright © 2015ITpreneurs. All rights reserved. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. source: http://agilemanifesto.org
  • 16.
    Copyright © 2015ITpreneurs. All rights reserved. Principles behind the agile manifesto ● Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. ● Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. ● Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ● Business people and developers must work together daily throughout the project. ● Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ● The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. ● Working software is the primary measure of progress. ● Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. ● Continuous attention to technical excellence and good design enhances agility. ● Simplicity--the art of maximizing the amount of work not done--is essential. ● The best architectures, requirements, and designs emerge from self-organizing teams. ● At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. source: http://agilemanifesto.org
  • 17.
    Copyright © 2015ITpreneurs. All rights reserved. Scrum Source: neon rain interactive
  • 18.
    Copyright © 2015ITpreneurs. All rights reserved. DevOps applies Agile principles to operations Development IT OperationsDevOps
  • 19.
    Copyright © 2015ITpreneurs. All rights reserved. Do Agile, EA and TOGAF Relate?
  • 20.
    Copyright © 2015ITpreneurs. All rights reserved. Architecture vision Architecture model Agile starts where Enterprise Architecture ends building block building block Goal Business Requirement Architecture Principle Agile project Application epic user story Architecture roadmap candidate project candidate project component component componentcomponent
  • 21.
    Copyright © 2015ITpreneurs. All rights reserved. Architecture Vision Architecture model Agile starts where Enterprise Architecture ends building block building block Goal Business Requirement Architecture Principle Agile project Application epic user story Architecture roadmap candidate project candidate project Pay for order online Pay via Paypal Increase customer satisfaction Self-service Customers do not have direct access to back- office applications Portal project component componentcomponent component Customer Portal
  • 22.
    Copyright © 2015ITpreneurs. All rights reserved. Positioning EA and Agile
  • 23.
    Copyright © 2015ITpreneurs. All rights reserved. Scaled Agile Framework source: http://scaledagileframework.com Agile is designed for small teams Dean Leffingwell The boys from Rational Unified Process are back. Building on the profound failure of RUP, they are now pushing the Scaled Agile Framework as a simple, one-size fits all approach to the agile organization Ken Schwaber We do not face, analyse failures and limitations of our assertions, claims, practices Philippe Kruchten
  • 24.
    Copyright © 2015ITpreneurs. All rights reserved. Role of Enterprise Architect in SAFe source: http://scaledagileframework.com - maintain holistic vision - aligns business drivers with technical decisions - sets technology standards - drive common infrastructure - influences modeling, design and coding practices - facilitates reuse of emergent solutions, knowledge & patterns - synchronizes issues and NFRs across solutions
  • 25.
    Copyright © 2015ITpreneurs. All rights reserved. Scaling Agile @ Spotify Chief architect - coordinates work on high-level architectural issues that cut across multiple systems - reviews development of new systems to make sure they avoid common mistakes, and that they are aligned with architectural vision - the feedback is always just suggestions and input - the decision for the final design of the system still lies with the squad building it source: Henrik Kniberg & Anders Ivarsson, 2012
  • 26.
    Copyright © 2015ITpreneurs. All rights reserved. What does this mean for training? There remains a role for Enterprise Architects ○ Need for training on Enterprise Architecture and TOGAF Some Enterprise Architects will become part of Scrum teams ○ Need for training on Agile and Scrum People need better understanding of how EA and Agile relate ○ Opportunity for new training and consulting
  • 27.
    Copyright © 2015ITpreneurs. All rights reserved. Do Agile, EA and TOGAF Overlap?
  • 28.
    Copyright © 2015ITpreneurs. All rights reserved. Enterprise Architecture versus Agile? The “old way” versus the “new way”
  • 29.
    Copyright © 2015ITpreneurs. All rights reserved. Misconceptions about EA and TOGAF
  • 30.
    Copyright © 2015ITpreneurs. All rights reserved. Misconceptions about EA and TOGAF ● EA is about modelling everything ● You need to follow all the steps in TOGAF ● Architecture principles are laws that cannot be deviated from ● Developing an EA takes a long time ● TOGAF is a waterfall approach ● EA prescribes things that should be left to the project
  • 31.
    Copyright © 2015ITpreneurs. All rights reserved. Example architecture principles ● Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. ● Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. ● Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ● Business people and developers must work together daily throughout the project. ● Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ● The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. ● Working software is the primary measure of progress. ● Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. ● Continuous attention to technical excellence and good design enhances agility. ● Simplicity--the art of maximizing the amount of work not done--is essential. ● The best architectures, requirements, and designs emerge from self-organizing teams. ● At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. source: http://agilemanifesto.org Agile is an architecture
  • 32.
    Copyright © 2015ITpreneurs. All rights reserved. Example architecture model source: neon rain interactive Scrum is also an architecture
  • 33.
    Copyright © 2015ITpreneurs. All rights reserved. Applicability of Agile Manifesto to EA We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. source: http://agilemanifesto.org Business outcome
  • 34.
    Copyright © 2015ITpreneurs. All rights reserved. Applicability of agile principles to EA process ● Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. ● Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. ● Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ● Business people and developers must work together daily throughout the project. ● Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ● The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. ● Working software is the primary measure of progress. ● Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. ● Continuous attention to technical excellence and good design enhances agility. ● Simplicity--the art of maximizing the amount of work not done--is essential. ● The best architectures, requirements, and designs emerge from self-organizing teams. ● At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. source: http://agilemanifesto.org The draft version of the architecture
  • 35.
    Copyright © 2015ITpreneurs. All rights reserved. Our principles for EA ★ Architects focus on what is essential ★ Architects provide concrete and useful results ★ Architects facilitate a collaborative process ★ Architects provide knowledge and skills ★ Architects use reference architectures ★ Architects use open standard methods and techniques source: http://www.tdan.com/view-articles/16108
  • 36.
    Copyright © 2015ITpreneurs. All rights reserved. How Enterprise Architecture overlaps with Agile Enterprise Architecture Agile Focus on management support Produces paper and insight Pre-project Not necessarily daily Abstraction Focus on user support Produces working software Project Daily work Technical excellence Iterative Multi-disciplinary Mandated business representative(s) Collaborative Soft skills Only the essentials
  • 37.
    Copyright © 2015ITpreneurs. All rights reserved. Conclusions ★ Enterprise Architecture provides an Agile project with a vision ★ Agile provides Enterprise Architecture with a good set of principles ★ Agile and Scrum can be seen as reference architectures
  • 38.
    Copyright © 2015ITpreneurs. All rights reserved. Get Started
  • 39.
    Copyright © 2015ITpreneurs. All rights reserved. Available Courses Togaf Level 1 Togaf Level 2 Togaf Practitioner Agile Scrum Foundation AgilePM Foundation AgilePM Practitioner Certified Scrum Master Certified Scrum Product Owner Agile Certified Practitioner
  • 40.
    Copyright © 2015ITpreneurs. All rights reserved. Business Simulation = The Power of Persuasion Create business opportunities with Framing the Future for ENTERPRISE ARCHITECTURE business simulation. Framing the Future challenges the participants to enter into a dialog together on Enterprise Architecture in relation to the organizational strategy. The simulation follows a solid instructional design approach to achieve results. There is a planning phase (what is the plan), and execution phase (building and deploying), followed by a reflection phase (what happened). During the reflection phase reference is made to Project management principles and theory, and these are connected to real life situations of the organization the participants are working for. Differentiate Your Offering with Simulations Your change management toolkit for every organization you work with. TOGAF Enterprise Architecture View Fact Sheet
  • 41.
    Copyright © 2015ITpreneurs. All rights reserved. In Development AgilePM Advanced Agile Scrum Advanced Agile for Business Analysts Managing the Agile Product Development Lifecycle Planning and Managing Agile Projects
  • 42.
    Copyright © 2015ITpreneurs. All rights reserved. How You Can Get Started 1/2 Partner A Full Service Partner B Use Your own trainer Partner C Only use our Courseware Courseware Exams Services Trainers Courseware Exams Services Courseware Exams
  • 43.
    Copyright © 2015ITpreneurs. All rights reserved. How You Can Get Started 2/2 Visit the ITpreneurs.com Website Review the Product of Interest Get in touch either through the Contact Form, send us an email, or call!
  • 44.
    Copyright © 2015ITpreneurs. All rights reserved. Q&A
  • 45.
    Copyright © 2014ITpreneurs. All rights reserved. +31 107.110.260 [email protected] Contact Us Corjan Bast Products & Solutions Marketing ITpreneurs | Rotterdam | The Netherlands