This document discusses DevOps and the challenges of integrating development and operations teams. It notes that having separate Dev and Ops teams with competing priorities can cause problems in delivering projects quickly and with high quality. Some solutions proposed include co-locating teams, having joint planning activities, and aligning team goals so both sides are working towards the same end success metrics. The overall message is that DevOps aims to break down barriers between Dev and Ops for better collaboration and integration to speed up delivery of business value.

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

2. SEE ENGINEERS FROM
TALK ABOUT
(AND MANY OTHER GREAT
TALKS) AT JULY 14TH & 15TH
WWW.MIDWEST.IO
DevOps
Data
Mobile
Web
Rules Engines
Microservices
Security

3. 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

4. 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.

5. WHAT IS IT NOT…

6. WHY DO WE WANT IT?
To deliver projects fast
Attain business value faster
With higher quality

7. 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

8. WHY IS IT A PROBLEM?

9. WHY IS IT A PROBLEM?
Lack of visibility to priorities on each side

10. WHAT OTHER PROBLEMS HAVE YOU SEEN?

11. WHAT WE WANT IT TO LOOK LIKE

12. WHAT IT CAN LOOK LIKE

13. 5 DYSFUNCTIONS OF A TEAM

14. BRINGING TEAMS TOGETHER
Co-location
Not just in the same building, but sitting next to each other

15. BRINGING TEAMS TOGETHER
Joint Ops Scrum
Ideally, run as Kanban, with daily review of priorities

16. 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

17. 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

18. 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

19. QUESTIONS