DevOps is not only for IT Players - cdn2-ecros.pl · DevOps flow/chain MEET CUSTOMER QUICK/IMPROVED...

Post on 21-Aug-2020

2 views 0 download

Transcript of DevOps is not only for IT Players - cdn2-ecros.pl · DevOps flow/chain MEET CUSTOMER QUICK/IMPROVED...

© 2017 Nokia1

DevOps is not only for IT Players

Benoît LE CALVEZ

Code:Dive

Wroclaw November 14th 2017

© 2017 Nokia2

© 2017 Nokia3

Take your phone and go to

https://app.klaxoon.comAccess code for today is :

BYYNJP

Are you coming from Dev or from Ops ?

© 2017 Nokia4

DEVOPS is not only for IT Players

Intro

• Back to the context

Our first experience

• Internal Project

A successful try

• With a partner

© 2017 Nokia5

• R&D and Operational Services colocalized

• Innovation platform with « Le Garage »

• COP CI : Community Of Practice for Continuous Integration

LANNION

© 2017 Nokia6

© 2017 Nokia7

DEV view OPS view

For the same internal product

Microservices

Architecture

© 2017 Nokia8

Take your phone and go to

https://app.klaxoon.comAccess code for today is :

BYYNJPWhich words would define DevOps for you ?

© 2017 Nokia9

Dream of DevOps model Everybody works hands

in hands for the best

© 2017 Nokia10

© 2017 Nokia11

DEVOPS is not only for IT Players

Intro

• Back to the context

Our first experience

• Internal Project

A successful try

• With a partner

© 2017 Nokia12

Our Internal Project foundations

Enthusiasm Small Teams Colocalized Leaders Support

© 2017 Nokia13

WHAAAT !! This product is bugged !I can’t use it !

© 2017 Nokia14

Our weakness

How to CHANGE THE MINDSET?

© 2017 Nokia15

Learn DevOps through LEGO !

✓Serious Gaming

✓Fun

✓Quick

✓Efficient

© 2017 Nokia16

The DEV team The OPS team

lego4DevOps

© 2017 Nokia17

LEGO4DEVOPS CREATIVITY

© 2017 Nokia18

Impact Upgrade

Risk analysis

Customers needs clearly shared on all

DevOps flow/chain

Dev invited at customer’s premises to see the

product in « real conf/envt »

Demos from Ops to Dev

Deployment of a new version

without service interruption with

offline validation

Delivery alpha/beta possibleAutomatic config Simplifying the interface (GUI

System installation (automatization)

Less manual actions

Propose one new interface per module

(extract or migration) -> mobile display

Automatic upgrade

as soon as new version available, automatically

deployed at customer site

More ergonomic interface allowing smooth

“jobs commands”

Simplified installation/delivery

(App Store ?)

Ergonomic

Usage simplification GUI

Parameters

Parameters defined earlier (not the dev which

give values sites/countries

ERGONOMIYGUI

SERVICEABILITYINSTALLATION SIMPLIFICATION

Meet the customer

Better access to customers

(feedbacks)

R&D (Dev) direct involvement with

customersFeedback customer’s requests

Stronger link between customers &

R&D

(requirement, feedbacks, priorities)

Customers needs clearly shared on all

DevOps flow/chain

MEET CUSTOMER QUICK/IMPROVED

FEEDBACK

INTERNAL COMMUNICATION

Full industrialization (build + tests)Implementation & quick validation of

customers requests

DEV CYCLES

DEV EFFICIENCY

Common tools for Dev & Ops (Config,

HW/tablet)

Utility

Faster Delivery Cycles

Fast & Modern development

(tool, archi, process…)

Dev / R&D Tooling Environment

Fast prototyping

Customer request -> POC -> GO/NO GO

Fast prototyping

Customer request -> POC -> GO/NO GO

Opening to external components

Open for Extensions (API)

API/EXT

Add usage metrics

Automatic log export when issue

Event log journal like in Windows

DEBUG

BUSINESS MODEL

More Budget !!Identify new needs, new use cases

for the product

Vision

Short-Mean-Long term

Economically viable

(pricing model & controlled R&D

costs)

Alignment with other

products closed to SDL

KPI/Usage Logs

Automatic management of usefull functions -> all unused

functionalities are logged and after a delay/discussion with

customer, features are removed

Feedbacks on real usage and

preventive maintenance

Database loading timing)

Aligned end-user expectations

Extraction timing

Collect feature activation for

deprecation SDME + SDM/SDL

Implement Usage KPI

SIMPLICITY

- Automatization of installation

- Usage

- MAJ

Open to other developpers

Don’t be dependent on customer’s

tooling (Eg. Customers specific clouds VZ

& ATT)

Generic Product

Feature activation by the customer

Improved modularity

Remove « the useless »

PRODUCT SIMPLIFICATIONMODULARITY

Make features/

components modular

EXTERNAL COMMUNICATION

Documentation

SUPPORT

Availability of databases

problems/solutions

Job creation / usage

Communication with customer (efficient tool)

Create internal forum for better communication

between teams (PLM, DEV, OPS, Customre r type)

Eg. Slack

Security // Simplicity

- Access

- - Usage

In conformity with regulatory requirements

(security, HSA/Privacy)

SECURITY

Log monitoring for proactive degradation

detection and automatic bug generation

(SDME + SDL)

LEGO4DEVOPS CREATIVITY BACKLOG

© 2017 Nokia19

CONTROL ZONE

INFLUENCE ZONECONCERN ZONE

ERGONOMIYGUI

SERVICEABILITY

MEET CUSTOMER QUICK/IMPROVED

FEEDBACK

INTERNAL COMMUNICATION

DEV CYCLESDEV EFFICIENCY

API/EXT

DEBUG

BUSINESS MODEL

KPI/Usage Logs

PRODUCT SIMPLIFICATIONMODULARITY

SECURITY

COMMUNICATION

LEGO4DEVOPS CREATIVITY BACKLOG INFLUENCE

© 2017 Nokia20

ERGONOMIYGUI

SERVICEABILITYINSTALLATION SIMPLIFICATION

CUSTOMER FEEDBACK

INTERNAL COMMUNICATION

DEV CYCLESDEV EFFICIENCY

API/EXT

DEBUG

BUSINESS MODEL

KPI/Usage Logs

PRODUCT SIMPLIFICATIONMODULARITY

SECURITY

IMPACT

EFFORT

low

low

high

high

LEGO4DEVOPS CREATIVITY BACKLOG INFLUENCE FEASIBILITY

© 2017 Nokia21

• Prototype• Documentation• Live my life• Requirements• Features used

LEGO4DEVOPS

CREATIVITY BACKLOG INFLUENCE FEASIBILITYQUICK WINS

© 2017 Nokia22

Take your phone and go to

https://app.klaxoon.comAccess code for today is :

BYYNJPHow many features are rarely or infrequently used in products ?

© 2017 Nokia23

DEVOPS is not only for IT Players

Intro

• Back to the context

Our first experience

• Internal Project

A successful try

• With a partner

© 2017 Nokia24

Our customer request

Fast

Efficient

Innovative

© 2017 Nokia25

Our rules & outcomes

Focus on essentialsTry + Try + TryPragmatic reportsRequirement defCommon lite docPrototype Development

© 2017 Nokia26

Our results

R&D Dev spec readyCommercial discussion can start4 month instead of a yearCust CSO raised the success !

Success key

Trust + Common MindsetProximity of Lab & teamsSmall squad

© 2017 Nokia27

© 2017 Nokia28

© 2017 Nokia30

© 2017 Nokia31

© 2017 Nokia32

© 2017 Nokia33