View
1.617
Download
0
Category
Tags:
Preview:
DESCRIPTION
This is a slidedeck about a topic I already talk about for a while: Every company is affected by the economic darwinism, i.e. the companies that respond best to change will survive. And the IT is not a bland cost center, it is the neural system of every company. No IT, no business! Combining those two observations it becomes obvious that the responsiveness of the IT about new business features is a crucial survival factor in the long run - we are no longer talking about months or years for new business features, but about weeks or days. In this slide deck I explain why the approaches most IT departments are not helping (sometimes even being counter-productive) and which building blocks you have to implement in order to survive the economic darwinism. Some of the slides badly miss the audio track but the core ideas should become clear.
Citation preview
Dr. Hectic and Mr. Hype How to survive the economic darwinism
Uwe Friedrichsen, codecentric AG, 2012-2013
Uwe Friedrichsen
@ufried
Charles Robert Darwin
(1809 – 1882)
Survival of the Fittest
Fitness
=
Ability to adapt to the demands of the environment
Author: J. Alves Gaspar
Typical
reasons
for failure
to adapt
The business department …
… and the IT
IT needs to be
quick and flexible
Agile ! … ?
Source: Dein Freund der Baum
Let‘s start over …
Observation #1
Everyone is affected by economic darwinism
• All sectors
• Growing globalisation on all levels
• Internet business
• More competitors per customer
• Higher customer expectations
• Lower customer loyalty
In the long run only those will survive who
meet the customer needs and demands best
Observation #2
IT is vital
• All companies
• IT is not just supporter or „cost center “ …
• … but it is the central nervous system
• Even short IT outages considered critical
• No business change without IT
• No new products without IT
The importance of IT for today‘s companies
cannot be overestimated
Consequence
IT is a key success factor for belonging to
the survivors of the economic darwinism
Current state
Design
Implement
Execute Monitor
Optimise
BPM Cycle
Analysis
Software
Engineering
Disciplines
Architecture
Development Build Test
Deployment
Operations Management
Analysis Architecture Development Build Test Deployment Operations
Management
Local Optimization Local Optimization Local Optimization Local Optimization Local Optimization Local Optimization Local Optimization
Rudimentary connection
via artefacts
Isolated optimizations,
no overall vision
Fault avoidance as driver
Artefacts
Process Framework
Artefacts Artefacts Artefacts Artefacts Artefacts Artefacts
Artefacts
Required state
Short cycle times
High flexibility
Continuous output
High reliability
Extreme added-value orientation
Holistic consideration Equally valued goals
But, but … that‘s agile and lean! Isn‘t it?
Source: Dein Freund der Baum
Organisation Processes
Infrastructure People
Lean
Agile
? ?
?
Building blocks
Darwinistic Software Development
Organisation Processes
Infrastructure People
Darwinistic
software development
Agile
Lean
Organisation Processes
Infrastructure People
Lean
Agile Darwinistic
software development
DevOps
Organisation Processes
Infrastructure People
Lean
Agile Darwinistic
software development
DevOps
Continuous Delivery
Organisation Processes
Infrastructure People
Lean
Agile Darwinistic
software development
DevOps
Continuous
Delivery
Feature Flow
Organisation Processes
Infrastructure People
Lean
Agile Darwinistic
software development
DevOps
Continuous
Delivery
Feature Flow
Cloud Computing
Organisation Processes
Infrastructure People
Lean
Agile Darwinistic
software development
DevOps
Continuous
Delivery
Feature Flow
Cloud Computing
Software Craftsmanship
Organisation Processes
Infrastructure People
Lean
Agile Darwinistic
software development
DevOps
Continuous
Delivery
Feature Flow
Cloud Computing Software
Craftsmanship
Organisation Processes
Infrastructure People
Lean
Agile Darwinistic
Software Development
DevOps
Continuous
Delivery
Feature Flow
Cloud Computing Software
Craftsmanship
Systemic
Optimisation
Challenges
Organisation Processes
Infrastructure People
Software Development
tomorrow
Professionalism
(Excellence)
Dissolving the
Disciplines
Consistent
Automation
Cross-department
Collaboration
Systemic
Optimisation
How to start
• No specific order
• Think global, act local
• Improve continuously
• Avoid over-optimization
• Start!
Source & Copyright: CapGemini
Do you really think this is
the strategy to survive
the economic darwinism?
And then one day you find
Ten years have got behind you
No one told you when to run
You missed the starting gun
Pink Floyd, Time
Uwe Friedrichsen
@ufried
uwe.friedrichsen@codecentric.de
http://www.slideshare.net/ufried/
http://blog.codecentric.de/author/ufr
Recommended