21
Transform The invisible Wall May Xu Oct 2014 House of DevOps

DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Embed Size (px)

DESCRIPTION

May Xu, Senior Consultant, Thoughtworks Australia The problem statement: at least 8 teams across department involved to deliver a new feature, with an average of 4-6 week. It becomes an issue when the senior management team has made a decision that they’re moving to cloud service. Should they do lift and shift, or should they adopt DevOps to revolutionise the way of working? Lift and shift seems to be a default option if the team has no idea; if you want DevOps, you have to know what’s your goal and fight hard. In our practise, senior management has played an important rule to get people agreed. Top 5 priorities to be addressed along the DevOps journey: 1. Different goals; 2. Ownership: Access and Permissions; 3. Job security; 4. Organisation structure; 5. Compliance requirement. As well as how to address these priorities; this is a long process and it could go back and forth, people needs to find their foot in the new world and they want to be valued. At last, I am going to share the methodologies to measure the result for the project as well as the team to ensure it’s a sustainable process. The tool set includes: quantify the value for automation; devOps skill matrix.

Citation preview

Page 1: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Transform The invisible WallMay Xu

Oct 2014

House of DevOps

Page 2: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

People are

disturbed not by

things, but by the

view which they

take of them.

Epictetus

2

Page 3: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Agenda

3

Context

What is DevOps

Why adopt DevOps

Build the house of DevOps in 4 steps

The Journey

Summary

Page 4: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Context

4

Page 5: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

What is DevOps ?

5

Page 6: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

What is DevOps ?

6

Environment: Laws, Regulations, Culture, Media …

People

Organization

Principle1.Self-directed team Over Command and Control2.Course correction over Perfection3.Automated over Manual

Team1.Respect2.Cross functional end-2-end delivery team3.Enable steady progress4.Share both the success and failures5.Continuous improvement

Practices1.Infrastructure as code2.Crystal dashboard: security3.Working backwards4.Open source 5.DevOps skill matrix6.Audit automation7.Self service8.And etc.

BUSINESS VALUEContinuously deliver customer value in a sustainable way with

improved lead time, resilience and quality

Page 7: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Why to adopt DevOps??

7

Stay Relevant In The

Fast Changing World

Page 8: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Build your House of DevOps in Four steps

8

a. Identify the goal

b. Understand the base

c. Develop the pillar

d. Keep iterating, continuous improving

Page 9: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – Discover the business value

9

Page 10: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – Understand Environment and people

10

The Sydney Morning Herald, July 18 2014

MIT Technology Review, June 12 2013

Page 11: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – Understand the organization

11

An organized group of people with a

particular purpose.

All organizations have a management structure that determines relationships between the

different activities and the members, and

subdivides and assigns roles, responsibilities and

authority to carry out tasks.

Organizations are open systems, they

affect and are affected by their

environment.

- From BusinessDictionary.com

Page 12: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Invisible – Fixed mindset vs. Growth Mindset

12

Page 13: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Develop Organizational growth mindset

Enable steady progress each day

Safe to fail environment

Innovation-friendly working environment

13

Page 14: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – Pillar of Principle

Self Directed team over Command and Control

Course Correction over Perfection

Automation over Manual

14

Page 15: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – pillar of Team: PAST

15

Page 16: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – pillar of team: Desired

16

Page 17: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – pillar of Practices

17

Page 18: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey – pillar of Practices:

18

• DevOps Skill Matrix

Page 19: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

The journey - business value

19

Before After

End to End infrastructure provision

4-6 weeks 4 hours

Mean time to recover Manual Auto

Deployment Lead time 30 minutes or more 90% less than 10 minutes

Infrastructure testing Manual Auto

Infrastructure security patching

Manual Auto

Environment consistency

No Yes

Page 20: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

Here IS what I’d like Help on

Access Control

Open Source

20

Page 21: DOES14 - May Xu - Thoughtworks - Transform the Invisible Wall

THANK YOU

May Xu

[email protected]

twitter: @may_ping_xu

May Xu

[email protected]

twitter: @may_ping_xu