Post on 10-Aug-2015
Alliander IT CIO Office
Michel de Goede
The Impact of Consumerization
IT has become part of your employees’ daily life
Your employees have become
computer literate. And reviewed or
rated apps are available 24/7.
2
Your employees know better how to perform work safely and efficiently than your IT department
Source: Alliander Annual Report 2014
3
Your employees are creative and involved
Trying to stop our employees from
creatively managing their work is like
pushing water uphill with a rake.
4
Your employees write their own apps
5
Video: www.youtube.com/watch?v=WkDCS8xeobg
Shifting perspective then: IT in the lead
See also ISO/IEC 25010 for Software Quality considerations
6
Shifting perspective now: user in the lead
See also ISO/IEC 25010 for Software Quality considerations
7
What could possibly go wrong?
Image: www.taxistartup.com
1. Back-end integration
2. Data and file formats
3. API’s
4. Security
5. Privacy
6. Vendor lock-in
7. Non-functionals
8
1. Back-end integration
9
Source: Nuon (left), Marcel van Driel, Eduard Lagendijk (right)
From: To:
2. Data and file formats
• Prezi is a great tool, but can you REALLY
combine it with Powerpoint (corporate standard)?
• Your home-baked customer switching app is
great, but does it connect to (the Dutch legally
obliged) EDINE messaging services?
• Are you sure that the transactional integrity in the
ERP part of your BigSQL back-end is OK?
10
3. API’s
11
Quote from James Governor, RedMonk for TechTarget / Search SOA
‘it is like API management is the new SOA’
4. Security = goal - risk
12
5. Privacy
13
Image: EU
14
6. Vendor lock-in
Images: Kotler, www.startitup.co, www.bmimatters.com, SAP, Nest, Samsung, Oracle, Apple, Google, Amazon
15
7. Non-functionals
1. Security
2. Service Level
3. OTAP
4. Capacity Estimates
5. Management
6. Disaster Recovery
Source: IBM
Counter measure 1: complexity reduction
Adaptation of material from Roger Sessions, Object Watch. Productivity comparison: ISBSG
Total system complexity is a function of the number of
business functions, the number of system connections and
complexity of the platform. Calculation: bf3.1+ sc3.1+ pc3.1 16
Counter measure 2: decouple on interface specification
Images: Query Surge, Object Watch, Journal Dev, Microsoft, Free Powerpoint Templates, BI Tools
17
Counter Measure 3: maximally autonomous microservice API’s
18
Image: http://www.grahamlea.com/2015/03/microservices-tyro-evolution-presentation/
Counter measure 4: stop fortification, be resilient
19
Resilience can be obtained by moving away from typical barrier enhancement
risk-measures. Consider the following options:
• Ignore, the ostrich ‘see-no-evil-hear-no-evil’ tactic;
• Accept, the potential impact of some risks may be deemed acceptable to your organization;
• Reduce, e.g. the potential impact or probability of occurrence of a risk, like the banking app;
• Transfer, use insurance or subcontracting to transfer potential consequences of risk;
• Avoid, not entering the type of business that may incur potential risk impact deemed too high;
• Exploit, risk is also an opportunity and high risk investments may yield high returns.
Counter measure 5: Educate
20
You cannot stop water from flowing, but you CAN
educate staff on privacy concerns.
Counter measure 6: manage orchestration
21
Image: https://jcastellssala.wordpress.com/2012/03/27/webservices-orchestration-choreography/
22
Counter measure 7: share responsibility
Image: www.plainadventure.com
23
Seven measures (read: potential new tasks!)
1. Reduce complexity
2. Know thy interfaces
3. Understand API’s
4. Create resiliency
5. Educate
6. Orchestrate
7. Share responsibility
You!
25
Questions?
Thank you!
26