Embed Size (px)
Citation preview
Architectural Thinking als Schlüssel für den Erfolg von Scaled Agile
Dr. Wolfgang GoeblLeipzig, 06.11.2018
1
About us
• Non Profit Association
• “Förderung des architekturellen Denkens in Unternehmen”
• Truly open Architectural Thinking Framework®
• architectural-thinking.com/participate
2
Basic Assumption of my Presentation
3
vs.? And!
Design by a Genius Team Design
see [Westerman15]
“The more participation in design, the better. This is surely not universally true.
Most great works of the human mind have been made by one mind, or two working closely. This is true of most of the great engineering feats of the 19th and early 20th centuries.
But now, team design has become the modern standard, for good reasons. The danger is the loss of conceptual integrity in the product, a very grave loss indeed. So the challenge is how to achieve conceptual integrity while doing team design, and at the same time to achieve the very real benefits of collaboration.”
[Brooks10]
4
Basic Assumption of my Presentation
Contents
1. The Problem
2. Attempts that verifiably do not work*• Enterprise/Software Architecture
• Agility/Design Thinking
3. What might work• Bringing things together
4. Conclusion
5. Open Discussion
5
Contents
1. The Problem
2. Attempts that verifiably do not work*• Enterprise/Software Architecture
• Agility/Design Thinking
3. What might work• Bringing things together
4. Conclusion
5. Open Discussion
6
The Problem
7
Dark Waters of Legacy IT
Disruptor Company
Agile! Agile! Agile!
Innovation!
? Architecture
?
Contents
1. The Problem
2. Attempts that verifiably do not work*• Enterprise/Software Architecture
• Agility/Design Thinking
3. What might work• Bringing things together
4. Conclusion
5. Open Discussion
8
Separated Disciplines
9
”It is all about Leadership”
“Cloud is the only remedy”
“Its all aboutInnovation” “Be Agile”
“Microservices to the Rescue!”
Contents
1. The Problem
2. Attempts that verifiably do not work• Enterprise/Software Architecture
• Agility/Design Thinking
3. What might work• Bringing things together
4. Conclusion
5. Open Discussion
10
‘Architecture’ done in ‘Agile’
11
Solution
EnterpriseZeroCurrent State
‘Architecture’ done in ‘Agile’
12
BizTekkieCurrent State
A sole Discipline as Connector
13
Vision/StrategyManagement
Design Thinking
Business Analysis
Business Process
Management
IT Operations
Project Management
ProgrammManagement
EAM
(Agile-)SolutionDevelopment
Business Units
Bloated EAM Frameworks
14
Archimate®
Zachmann
TOGAF®
[Carr18] [Kostic 16]
Ivory Tower Architects
Software/System Architecture only
Microservices as universal Remedy
https://de.slideshare.net/ITARENA/microservices-redundancy-maintainability-eberhard-wolff-technology-stream
Tiny modules to the rescue
Redundant Data makes Agile scale!
The Cloud as universal Remedy
18
Contents
1. The Problem
2. Attempts that verifiably do not work*• Enterprise/Software Architecture
• Agility/Design Thinking
3. What might work• Bringing things together
4. Conclusion
5. Open Discussion
19
Flavours of ‘Agile’
20
Hardcore
DisciplinedAnarchy
Structured
Current StateMean Value
Scope of ‘Agile’
21
Multiple Solutions
EnterpriseSolutionCurrent State
Hardcore Agility
22
23
Autonomous Teams without a Plan
24
Time-to-market Thinking only
25
Focus on Culture/Leadership only
Ch
ain
s o
f Le
gacy
Company
Be agile!
Lead agile!
Run like Hell!
26
Design Thinking
Let’s have Fun!
... and create yet another unrealizable
point solution!
28
Nexus™
Pros Cons
Extremely lean (12 pages) No real guidance
Architecture not mentioned
Large Scale Scrum (LeSS) - Quotes
https://less.works/less/technical-excellence/architecture-design.html
30
• What to model:• low-fidelity UI modeling • algorithm modeling with UML activity diagrams, • object-oriented software design modeling • database modeling likewise.
“The real software architecture evolves as people do programming.”
“Think ‘gardening’ over ‘architecting’—Create a culture of living, growing design”
31
Large Scale Scrum (LeSS)
Pros Cons
Evolutionary Approach No Inception Phase
Team creates Architecture
No ‘Architecture Owner’ – Integrity??
Tekkie Architecture only
Focus on Solution only
Enterprise Awareness?
Scaled Agile Framework® (SAFe®)
https://www.scaledagileframework.com/
32
33
Scaled Agile Framework® (SAFe®)
EA’s Responsibility:90% Tekkie
https://www.scaledagileframework.com/enterprise-architect/
34
Pros Cons
Nexus to BizArch(Value Stream)
No other BizArch Artefacts (Information, Capabilities)
Explicit Architecture Roles - No Inception Phase- Ignores Wisdom of EA&BA- 90% Tekkie Architecture
Enterprise Awareness Hard to understandExpensive Trainings needed.Too heavyweight?
Scaled Agile Framework® (SAFe®)
Disciplined Agile Delivery (DaD)
disciplinedagiledelivery.com/35
36
Disciplined Agile Delivery (DaD)
disciplinedagiledelivery.com/
Inception Phase:• foundation from which the project can be successful in a lightweight manner• Enterprise awareness• Vision, scope, connection with Biz-& EA of the company• Enterprise as another customer
37
Pros Cons
Understands Biz&ITArchitecture in depth
Not as widespread as SAFe®
‘Architecture Owner’ role
Evolves evolutionary from team
Inception Phase
Enterprise Awareness
Easy to understand
Disciplined Agile Delivery (DaD)
Contents
1. The Problem
2. Attempts that verifiably do not work*• Enterprise/Software Architecture
• Agility/Design Thinking
3. What might work• Bringing things together
4. Conclusion
5. Open Discussion
38
A new, more holistic Manifesto
39
40
YES
A new, more holistic Manifesto
Sustainable solutions over working software
41
A new, more holistic Manifesto
42
Considering all stakeholders over customer only
A new, more holistic Manifesto
Incl. Enterprise as a whole
43
Malleable plans over strict plans & anarchy
Business (Architecture) over IT (Architecture)
44
A new, more holistic Manifesto
New
45
Vision/StrategyManagement
Design Thinking
Business Analysis
Business ProcessManagement
IT Operations
Project Management
ProgrammManagement
(Agile-)SolutionDevelopment
Business Units
Architectural Thinking as a Mindset
46
• Overlapping responsibilities between departments
• Unclear data- and process ownership
• Acting in departmental silos
• Weak links between departments
• Short term thinking
• Bad (IT-) funding decisions
• Ordering the wrong IT solutions
Business aspects/decisions are the reason of IT Chaos
Focus on Business Architecture
Focus on Business Architecture
• Model of the Business Architecture drives IT Architecture• Capabilities
• Processes/Value Streams
• Business Information
• Applications
47
[BAGuild16]
Simple Model everybody agrees upon
48
Ear
Leg
Tooth
Trunk
Eye
Connect everything to Model
49
Ear
Leg
Tooth
Trunk
Eye
Requirement
Budget Solution
VisionStrategy
Project
Code
Architectural Thinking Framework® Metamodel
(Draft)
Governance
Connect Solution Stories and Biz Arch
50
Cap
abili
ty M
ap (
Exam
ple
Ban
k)
51
Solu
tio
n L
evel
Sto
ry M
ap
Bo
ard
Ente
rpri
se L
evel
Ca
pa
bili
ty M
ap
Connect Solution Stories and Biz Arch
52
Connect Solution Stories and EntArch
Modularize by Business Information
53
Manage technical Debt proactively
54
Dark Waters of Legacy IT
“Agility does not mean to maximize speed. It means maneuverability, i.e. finding the right speed to make the right deflection.”
55
Find right speed, modernize System
Culture to transform the System
• The “System” (business & IT structures) make a company Agile
• Agile culture• alone does not transform a company
• is important but not a means by itself
56
+ Culture+ (Reengineering-) Methods ----------------------------------= Transformation
Strict Governance & autonomous Teams
57
Add Architectural to Design Thinking
58
Design Thinking Workshops are cool! But….
*) Architecture Maps and Architecture Owner must be in the room
*)
Architectural Thinking Framework®
59
https://architectural-thinking.com/architectural-thinking-overview/
Contents
1. The Problem
2. Attempts that verifiably do not work*• Enterprise/Software Architecture
• Agility/Design Thinking
3. What might work• Bringing Things together
4. Conclusion
5. Open Discussion
60
Conclusion: How to scale Agile
• Disciplines working together using the same Enterprise Model
• Strong focus on Business Architecture
• Integration of Scaled Agile- & Lightweight Architecture Framework
• Centralized governance AND autonomous teams
• Cultural Change AND (engineering) methods
• Collaboration between Enterprise- and Solution Architecture
61
Recommended Reading
[Ambler10]: S. Ambler: ‘Disciplined Agile Delivery’
[BAGuild16]: Business Architecture Guild, “A Guide to the Business Architecture Body of Knowledge®” (BIZBOK® Guide, v6.5), http://www.businessarchitectureguild.org/
[Brooks10]: F. Brooks: ‘The Design of Design: Essays from a Computer Scientist’
[Carr18]: D. Carr 'State of Enterprise Architecture Survey: Results and Findings' https://eapj.org/wp-content/uploads/2018/05/EAPJ-Special-Edition-State-of-EA-Survey.pdf
[Eckstein18]: J. Eckstein: ‘Company-wide Agility’
[Kostic 16]: N. Kostic: ‘Demystifying Enterprise Architecture‘http://www.entarchs.com/blog/demystifying-enterprise-architecture.html
[Westerman15]: ‘Leading Digital Turning Technology into Business Transformation’
62
One last thing…
63
“Sometimes we are Agile without the Discipline.
Sometimes we are disciplined without the Agile.
We need both.”
Thank you!
64
Dr. Wolfgang Goeblwolfgang.goebl@architectural-thinking.comarchitectural-thinking.com
