DOES16 London - Scott Potter - DevOps: To Autonomy and Beyond

Scott Potter
(former) Head of Digital Engineering
To Autonomy & Beyond
Considerations for Leaders and Senior Management as their Teams Grow their
Capability, Responsibility and Autonomy

The Company & Organisation
Scott Potter – To Autonomy & Beyond

The Company
• Founded 1700s
• 5,000 people
• Under CIO, 350 – 500 people
TNL Ltd. turned a profit in 2015
following substantial revenue growth
from Digital subscriptions

The Technology Organisation
DigitalD&AEnterprise

Headed up software engineering
Approx. 100 people
- plus some external agencies Peak of
200 people
DigitalD&AEnterprise
The Times Tablet App
- Highest Grossing (non-game) app in the
Apple UK store
Sun Goals App
- Top 5 downloaded sports app in the UK

Headed up software engineering
Approx. 100 people
- plus some external agencies Peak of
200 people
Digital
AppsWeb
ACSCPS
Android
Obj C & Swift
HTML & JS, Single Page Apps
Groovy, NodeJS, Java, Ruby
Wordpress, php
AWS Based Cloud Infrastructure
Pop-up envs, Chef, Lambda …

A bit about me

A bit about me…
I started coding on one of these...
When he was still considered clever...
Before he released this!
My Engineering career started
the same year this man launched
the WWW to the public.
He launched Linux, and...
this phrase was coined!

A bit about me
I’m currently consulting with Equal Experts
Previously Head of Engineering at News UK
Prior to that at some point… Xerox

A bit about me
I’m currently consulting with Equal Experts
Previously Head of Engineering at News UK
Prior to that at some point… Xerox
Mechanical Design Engineer, R&D,
Electronic Engineering & Manufacturing Engineering
Science based experimentation,
Exploration & Prototyping
Componentisation
Design for Reuse
Interfaces
EVERYWHERE

Lean Software Development Black Belt
Engineer - Agile Coach
At News UK 4 years
Initiated dept. transformation in Oct 2013

What Business Problem I’m trying to Solve

What Business Problem Was I Trying To Solve?
The Business Problem
- Build a Digital Software Engineering dept.
...with a culture of quality, agile, based in London on average
salaries

To increase cash flow
To increase adaptability and agility
To reduce project risks
… With a vibrant culture that supports motivated staff, workforce stability and a real desire to continually improve standards.
And be able to sustain this.
This requires capable, motivated and correctly aligned people, working on tangible value.
Provide Business Agility
To provide adaptive software development which supports greater business agility:
(by releasing value early with quality and operational integrity)
(via practices such as xP, processes / frameworks such as scrum, tech, people, behaviours)
(early and continual feedback, able to pivot, accurate progress tracking as ‘Done’ means done)
What Business Problem Was I Trying To Solve?

Achieving DevOps from the Dev Side

What does it mean to be an Engineer?
Initial step – what do I bring to this role?
Direction & Leadership
Core Competencies, Professional Behaviours
Vision & Identity
Core Values: To Nurture, To Inspire, To Engineer, To Deliver
Initiating Change

Reorganised to ensure that:
• Every Team was aligned to a set of real users
• Every Team was as cross functional and autonomous as possible
• Every Team had a core of permanent staff
Done with full collaboration with my 4 Engineering Managers
Initiating Change

Stabilise
Recruit
Grow Competencies (Engineering Excellence Model)
Retain Key Staff
Increase Productivity
Strive for Engineering Excellence
Provide Great Careers
Phases 1 & 2

Environment
Capabilities & Behaviours
Values
Vision & Identity
Engineering Excellence Model

Environment
Values
Vision & Identity
Engineering Excellence Model
The Skill
Technical Agility
Organisational Agility
Process Agility
Personal Agility
The Will
Sense of Purpose
Autonomy
Opportunity to Grow

An Extract from a communication
The objectives of this strategy are to:
● Ensure that each development team is as self sufficient as possible,
● Ensure that each development team is cross functional & resilient, with no single points of failure,
● Create an environment of ownership behaviour where teams:
are empowered,
have flexibility,
build up trust to rely upon one another,
to be able to challenge one another and therefore continuously improve,
● Sufficient knowledge to design end-to-end systems more successfully than was previously capable,
● Ensure teams are able to respond to changing requirements,
● Avoid poorly designed & hard to use environments and stacks experienced from a pooled sys eng team.
Systems Engineering & DevOps Strategy

Establishing High Performing Teams
• They have a common goal
• High Standards & Expectations
• Able to Resolve Conflict
• Frequent Feedback, Team-based rewards

Establishing High Performing Teams
• They have a common goal
• High Standards & Expectations
– Know what to expect from one another
– Able to make decisions
– Culture of learning & improvement
– Personal Responsibility & Ownership behaviour
– Have a ‘resourceful state of mind’
– Take the responsibility to hold one another accountable
• Able to Resolve Conflict
• Frequent Feedback, Team-based rewards

• To Ensure our Employers / Our Company can produce and provide products or solutions that
successfully meet their customers needs (better than our competitors).
• To do so in a cost effective and timely manner.
• To do so such that it supports the business needs, goals and ambitions.
• To be able to do this consistently and sustainably.
What do we all have in common? What are we trying to achieve?

What Did We Achieve? What can I observe? Leading KPIs
• Close collaboration - share the problem to be solved or the desired outcome and work through it together. No
dictating of solutions, architectures or process.
• Frequent, continuous and quick feedback to amplifying learning. We all know more today than we did
yesterday. How much more can we learn? How can we derisk a complex project or product build?
• Empowered teams are essential as they know the most about the options available and are more motivated
when closely aligned to and able to influence the outcome.
• Empowered teams can also ensure that they only do what is needed and no more, keeping solutions as
simple as possible, making time to market quicker and enhancement and maintenance easier.
• Micro services architecture:
• Release working software early & often to increase feedback, and opportunity to learn and optimise the product.
• Initiate new builds with the lightest build and deployment pipeline to production.
• Prove the technology choices, base architecture, processes and tooling as early as possible so that be every
subsequent product increment is known to be a true, complete increment (no more work required).

What Next?

What Now?
As a Leader / Senior Manager, do I still have a role to play?

What Now?
Nice Problems to Have

What Now?
Building a New Culture, with Resilience

People are always the common factor.
Capable & Motivated people who can assist one another at the coal-face and rely on one another.
The proof is in delivering value, frequently and sustainably.
Process Product
People
Under-damped
What Now?
The Pendulum

The Agile Manifesto
• Underlying structure based on Patrick Lencioni’s 5 Dysfunctions of Teams:
– Absence of Trust
– Fear of Conflict
– Lack of Commitment
– Avoidance of Accountability
– Inattention to Results
What Now?
Personal Agility

Artificial Harmony
Low Standards
What Now?
Personal Agility

What Now?
Personal Agility

Takeaways
Stabilise
Recruit
Grow Competencies (Engineering Excellence Model)
Retain Key Staff
Increase Productivity
Strive for Engineering Excellence
Provide Great Careers
Environment
Values
Vision & Identity

Thank you
Scott Potter
To Autonomy & Beyond

DOES16 London - Scott Potter - DevOps: To Autonomy and Beyond

More Related Content

What's hot (20)

Similar to DOES16 London - Scott Potter - DevOps: To Autonomy and Beyond (20)

More from Gene Kim (20)

Recently uploaded (20)

DOES16 London - Scott Potter - DevOps: To Autonomy and Beyond