AgileKC - DEVOPS - June 2014

19
Shahzad Zafar Manager, Cerner Corporation @m_shahzad_z IS IT A DEV PROBLEM? IS IT AN OPS PROBLEM? NO, IT’S A DEVOPS PROBLEM!

description

Is it a Dev problem? Is it an Ops problem? No, it’s a DevOps problem! Presented at AgileKC on 6/25/14

Transcript of AgileKC - DEVOPS - June 2014

Page 1: AgileKC - DEVOPS - June 2014

Shahzad Zafar

Manager, Cerner Corporation

@m_shahzad_z

IS IT A DEV PROBLEM? IS IT AN OPS PROBLEM?

NO, IT’S A DEVOPS PROBLEM!

Page 2: AgileKC - DEVOPS - June 2014

SEE ENGINEERS FROM

TALK ABOUT

(AND MANY OTHER GREAT TALKS) AT JULY 14TH & 15TH

WWW.MIDWEST.IO

DevOps

DataMobile

WebRules Engines

Microservices

Security

Page 3: AgileKC - DEVOPS - June 2014

CULTURE AT CERNER• Cerner Engineering YouTube channel

• Cerner Tech Talk Series

• DevCon Talks

• Cerner DevCon 2014

• Cerner Engineering Blog

• http://engineering.cerner.com/

• Open Source projects participation

• Internal and external conferences participation

Page 4: AgileKC - DEVOPS - June 2014

WHAT IS DEVOPS?

According to wikipedia:

DevOps is a software development method that stresses communication, collaboration and integration between software developers and information

technology (IT) operations professionals.

Page 5: AgileKC - DEVOPS - June 2014

WHAT IS IT NOT…

Page 6: AgileKC - DEVOPS - June 2014

WHY DO WE WANT IT?

To deliver projects fast

Attain business value faster

With higher quality

Page 7: AgileKC - DEVOPS - June 2014

WHY IS IT* A PROBLEM?

Two different organizations with

Competing priorities

Different measuring stick

Independent organization structure

* Getting the teams to work in a DEVOPS mode

Page 8: AgileKC - DEVOPS - June 2014

WHY IS IT A PROBLEM?

Page 9: AgileKC - DEVOPS - June 2014

WHY IS IT A PROBLEM?

Lack of visibility to priorities on each side

Page 10: AgileKC - DEVOPS - June 2014

WHAT OTHER PROBLEMS HAVE YOU SEEN?

Page 11: AgileKC - DEVOPS - June 2014

WHAT WE WANT IT TO LOOK LIKE

Page 12: AgileKC - DEVOPS - June 2014

WHAT IT CAN LOOK LIKE

Page 13: AgileKC - DEVOPS - June 2014

5 DYSFUNCTIONS OF A TEAM

Page 14: AgileKC - DEVOPS - June 2014

BRINGING TEAMS TOGETHER

Co-location

Not just in the same building, but sitting next to each other

Page 15: AgileKC - DEVOPS - June 2014

BRINGING TEAMS TOGETHER

Joint Ops Scrum

Ideally, run as Kanban, with daily review of priorities

Page 16: AgileKC - DEVOPS - June 2014

JOINT ACTIVITIES

Dev teams sit in the deployments (and feel the pain )

Ops teams sit in design sessions, code review, releases etc.

Build tools to help both set of activities

Page 17: AgileKC - DEVOPS - June 2014

JOINT PLANNING

Regular Leadership Sync

As leaders, need to change mindset from them / their to us / ours

Give Ops a voice in Dev priorities and vice versa(hard thing to do)

Not all Dev teams/projects need an Ops counterpart

Page 18: AgileKC - DEVOPS - June 2014

ALIGNING GOALS

Success factor for each side should align to the same end goal(even harder to do)

At minimum, understanding and respecting each others’ goals

And learning to work within those constraints

Page 19: AgileKC - DEVOPS - June 2014

QUESTIONS