The DevOps Culture Shift -

Getting Team Collaboration

Simon Sabin, Director Engineering at Sabin

•Want to work

•on your own?

•Can’t do much

on your own

•Companies

need

collaboration

Simon Sabin

• Owner sabin.io

• Founded and runs SQLBits

• MVP and Microsoft Regional Director

• Passionate about DevOps

• Enable companies to make data work

• and deliver success

Today

Companies and People

People

• More work than one person

• One person can’t know everything

• Challenging yourself is hard

• Companies need people to work together

Business

Legal

Dev

Security

Business

Cross company

Challenge

• Need to get time

• Explain the problem statement

• Try to get agreement

• Co-ordinate multiple stakeholders/experts

• Document agreement

• Get sign off on

• Start work

Prioritisation

Prioritisation Challenge

• Time to understand requests

• Time to investigate

• Obtaining context and requirement

• Time to prioritise request

• Scheduling work

• Rework after delivery back to team

• Satisfaction

Team Scope

Cross team delivery

Dev Data

Cross Team Challenge

• Team focus on their requirement

• Big picture requirement lost

• Iterative development

• External requirements not managed

• Data quality big challenge

• Scope of ownership too narrow

• Typical of micro service world

Intra team

One teamAll the skills

•Does that exist?

Reality

Dev

process

Dev

writes

code

DBA

review

Code

checked

in

DBA

deploys

change

Tests

run

DBA

deploys

change

Tests

run

DBA

deploys

change

Users

Test

How do you get

autonomy?

Responsibility

Who is responsible

for security?

Who is responsible

for data quality?

Current

Target

Team ScopeTeam Scope

Cross team delivery

Ownership and responsibility

• Stakeholder/Expert

• owner of the process

• responsible for providing requirements

• NOT responsible for doing

• If you do the work

• you’re responsible

• you need to get scope right

Requirements

• Scope needs to be well defined

• Location of responsibility

• Teams need to consider big picture

• Business stakeholders included

Goal

• Stakeholders define requirements

• Per sprint

• Per project

• Organisation wide

• Team delivers to requirements

• Responsibility shifted to team

• Team autonomy

Autonomous

•Goals and KPIs

What is your goal?

What is your team goal?

What is your company goal?

Without alignment

collaboration or

cross team

delivery very hard

•Aligned goal

•Same direction

Dev Ops

DevOps & Why

• Focus on delivery

• Delivery based on goal

• Feedback success into process

• Deliver faster

• Stay focused on goal

How does DevOps help

• Collaboration brings agreement

• Incremental change

• Automation & testing maintains deficit

• Definition of Done enables progress

• Continuous ensures on going success

• Metric/Feedback driven

• Learn from change

• Agile highlights collaboration challenges

Current

Autonomous

Collaboration

& DevOps

Codify requirements

in your DevOps

Definition of Done

•Enforce peer

review

Requirements

as tests

Green is

the purest

•Add approval

for release

Codify process in DevOps

• Requirements review in sprint planning

• Audit traceability with commit policies

• Reviews in pull requests

• Functional requirements with tests

• Code quality with tests

• Security verification with tests

• Performance metrics with gates

• Approvals in releases

Dev Ops

Do

• Align on goals and KPIs

• Define ownership

• Define responsibility

• Codify into your DevOps

• Thrive on feedback

• Improve

Anyquestions?