© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d©

201

5 Cl

oudB

ees,

Inc.

All

Righ

ts R

eser

ved

From 1 RPM to 1,000 RPM – Succeeding in a Software-Defined EconomyJAX London 2015

@SachaLabourey

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

2

Software development wasn’t always as easy…

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

3

It took us a lot of discovery to find our way…

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

4

Developers have always looked for “better ways”

Agile Manifesto – 2001“We are uncovering better ways of developing software by doing it and helping others do it.”

Hudson/Jenkins - 2005Scrum

XPKanban…

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

5

What did we gain?• We have gained tremendously from those innovations

– Earlier and more predictable releases– Improved quality– Flexibility / allows for changes– Cost control

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

6

What did we really gain?

IT

Dev IT OpsCustomer

Business requirement

Solution (software)

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

7

What did we really gain?

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

9

What we tend to forget

IT IS FOR BUSINESS(i.e. for the business to make more money or spend less money – yep, that’s it!)

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

10

And what we now MUST all realize…

IT IS FOR BUSINESSIT IS BUSINESS

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

11

“Software is eating the world.”

“Every business is in the software business.”

“It’s anapplication economy.”

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

12

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

13Photo courtesy of Bill Abbott via Flickr

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

14Photo courtesy of Naddsy via Flickr

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

15Photo courtesy of Steve Jurvetson via Flickr

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

16

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

17

Repeat after me: BUSINESS IT

SOFTWARE IS EATING YOUR WORLD AS WELL!

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

18

How to get there?• We have to essentially bring the “Development Smartness”

and apply it to … the business as a whole!

• This is not just how we develop “software”…• But how that software takes place in the business

differentiation– How business requirements & objectives get defined– How we structure “Business” teams to deliver value through

software– How frequently do we release software How frequently do we

gather feedback FAIL FAST & ADAPT QUICKLY

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

Traditional Development vs. Continuous Delivery

Version 1

• Released May 2011

Version 2

• Released May 2012

Version 3

• Released May 2013

Typical development methodologiesBonus:use of continuous Integration

CSS improvment1st of Feb

Move a button on the UI

1st of Feb

New Tab2nd of Feb

Change UI theme13th of Feb

Bug fix14th of Feb

This is Continuous Integration and Continuouns Delivery

CD

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

Time

v1.0 Release

v2.0 Release

Time

Continuous ReleasesRisk/Cost

Risk/Cost

Versioned Software Continuous Delivery – “As a Service”

Reduce risk, reduce experimentation cost, fail-fast

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

• A « Pipeline » defines all of the step that go from code-to-production

• Your software must always be in a “release-ready” stage

Problem:

FAST_ITERATION + FRICTION => HEAT!

Continuous Delivery – Define your pipeline!Code Build Test Stage Deploy

#FAIL#FAIL #FAIL#FAIL

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

22

Automation is Key to Fast Iteration

Photo courtesy of Steve Jurvetson via Flickr

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

Most of the time relatively complex (and growing!)

23

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

24

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

How to get there?

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

STEP “0”: EMBRACE CI

Dev BuildCommit Test

Feedback Loop

Feedback Loop

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

STEP 1: EMBRACE DEVOPS AND CD

ProdDev BuildCommit Test Stage Deploy

Feedback Loop

Feedback Loop

1. Simply a BETTER WAY!2. Doesn’t require changes

OUTSIDE of IT

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

STEP 2: EDUCATE THE BUSINESS

ProdDev BuildCommit Test Stage Deploy

Feedback Loop

Busi-ness

Project Team

Feedback Loop

1. Natural extension!2. YOU are the best positioned

to explain what’s happeningon the market and how youcan benefit from this! You arethe new Rain Maker!

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

28

STEP 3: START SMALL• Pick a Proof of Concept (PoC) project• Aim for “easy”, “non-critical”, “no edge cases”• Pick a MOTIVATED TEAM

– dynamic, eager to learn and change, etc.– MUST INCLUDE ALL TEAMS, INCLUDING BUSINESS!

• THE GOAL HERE IS TO WIN AND DEMONSTRATE VALUE

– SO… WIN!

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

29

STEP 4: ADVERTISE YOUR WIN• Now is time to BRAG! • Show the value, show metrics (time, risk, market-fit, etc.)

• Make it a BUSINESS CASE, not a technical one

– Remember business == IT

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

30

STEP 5: ITERATE!• Rinse and repeat!• Use your PoC team to train other teams, they are now your in-house experts!

• Start small and grow big• BIG BANG approaches never work. Ever.

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

31

Why should it matter to you – as a developer?• INDUSTRIALIZATION has profoundly impacted work organization, tools and processes

• Businesses are entering a similar transformation– IT is not just a way to optimize back-office operations

anymore…– IT becomes core to the products/services, IT is the

business• As a software developer you have first hand expertise on how this can be applied to your business

SOFTWARE DEVELOPERS ARE THE NEW KING MAKERS!

© 2

015

Clou

dBee

s, In

c. A

ll Ri

ghts

Res

erve

d

32

Conclusion• IT “industrialisation” has started• Software is what will make – or – kill

companies

• Developers have a HUGE OPPORTUNITY ahead…

• … But also a GREAT RESPONSIBILITY

YOU MUST RING THE WAKE-UP CALL“If you don't like change, you’re going to like irrelevance even less”

General Eric Shinseki