The Emperors old clothes Engineering Culture Revived Finbarr Joy - - PowerPoint PPT Presentation

▶
the emperor s old clothes engineering culture revived
SMART_READER_LITE
LIVE PREVIEW

The Emperors old clothes Engineering Culture Revived Finbarr Joy - - PowerPoint PPT Presentation

Feb 24, 2024 33 likes •505 views

The Emperors old clothes Engineering Culture Revived Finbarr Joy Culture? A pattern of basic assumptions that the group has invented, discovered, or developed in learning to cope with its problems of external adaptation and internal

slide-1
SLIDE 1

The Emperor’s old clothes Engineering Culture Revived

Finbarr Joy

slide-2
SLIDE 2

Culture?

slide-3
SLIDE 3

A pattern of basic assumptions that the group has invented, discovered, or developed in learning to cope with its problems

  • f external adaptation and

internal integration.

Edgar Schein

slide-4
SLIDE 4

sharpening the organisation’s instinct:

  • how we compete
  • how we deal with challenges
  • how we relate to one another
  • how we agree the ‘right’ thing to do
  • how we behave
  • how we react
slide-5
SLIDE 5

What’s going on?

slide-6
SLIDE 6

React..? Vue..? Go..? Rust..? home..? pub..?

slide-7
SLIDE 7

Disruption! Cloud! DevOps! Agile! Scrum! DIGITAL TRANSFORMATION

slide-8
SLIDE 8

?

slide-9
SLIDE 9
slide-10
SLIDE 10

for when “employees balk at the new practices required by the new technologies.”

Culture Transformation is key..

slide-11
SLIDE 11
slide-12
SLIDE 12

th the best t way to

  • establis

lish a cu cultu lture?

DON’T ‘establish’ a culture !!

slide-13
SLIDE 13

Walk the walk

https://www.ozprinciple.com

slide-14
SLIDE 14

Leader? Be. Do. Say

  • What your focus is – what you’re measuring
  • How you react to incidents / crises
  • How you allocate resources
  • How you allocate rewards & status
  • How you recruit/ promote/ select

Role Modelling, teaching and coaching

slide-15
SLIDE 15

respect

slide-16
SLIDE 16

St Start rt with a mi mission

slide-17
SLIDE 17

‘why’ has never been so profound

AI/ Machine Learning AR/ VR blockchain serverless Voice activation Algorithmic IT Event streaming

slide-18
SLIDE 18
slide-19
SLIDE 19

INNOVATION LAB?

slide-20
SLIDE 20

if if you

  • u’re not
  • t in

innovatin ing wh why wr writ ite soft

  • ftwar

are ?

slide-21
SLIDE 21
slide-22
SLIDE 22

The ‘r ‘right’ ’ team

selection?

slide-23
SLIDE 23

"You can't have great software without a great team, and most software teams behave like dysfunctional families."

  • Jim McCarthy
slide-24
SLIDE 24

How we work

Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.

Lucius Annaeus Seneca

slide-25
SLIDE 25

Agile is regarded by the common people as true, by the wise as false, and by rulers as useful.

How we work

slide-26
SLIDE 26

“Four measly bullets, and all this s#!t happened?!“ Jon Kern

Contino - Secrets from the Agile Manifesto Authors on Flow

slide-27
SLIDE 27

is it SAFe?

slide-28
SLIDE 28

shortest possible time to release

Pattern of work: flow

slide-29
SLIDE 29

Remove all possible barriers / dependencies to release: automation

Pattern of work: flow

slide-30
SLIDE 30

CODE MAINTENANCE

slide-31
SLIDE 31

The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay

C.A.R Hoare

slide-32
SLIDE 32

Environment ?

slide-33
SLIDE 33

Environment ?

slide-34
SLIDE 34

Environment ?

slide-35
SLIDE 35

Must have ‘enough’ autonomy

  • Leadership clear on ‘why’ & ‘what'
  • tools, technologies and HOW
  • Developer evaluates best options for release
  • Developer releases to live
  • Invested in the customer lifecycle
slide-36
SLIDE 36

walk the walk: ’just’ programming?

slide-37
SLIDE 37

walk the walk: ’just’ programming?

slide-38
SLIDE 38

Architecture Development QA Operations Support

Team model?

slide-39
SLIDE 39

Architecture Development QA Operations Support

Team A Team B

Product Management Mkt Analytics CX

Team model?

slide-40
SLIDE 40

Structure

slide-41
SLIDE 41

To:

Structure

slide-42
SLIDE 42

From teams, build communities

slide-43
SLIDE 43
  • Walk the walk on your values
  • Create a mission
  • Embed Innovation
  • (Self)Select the best team members
  • Appreciate the developer ‘psyche’
  • Consider the ‘rhythm’ of release (avoid deathmarch)
  • Remove all impediments (bureacracy/ automation)
  • Stay on top of the ‘housekeeping’
  • Environment sustains communication
  • Don’t accept ‘proxies’ to customer
  • Re-imagine your team/ org shape – Network!
  • Re-claim engineering principles !
slide-44
SLIDE 44

Momentum is everything

slide-45
SLIDE 45
  • Make each service do one thing well. To do a new job,

build afresh rather than complicate existing services by adding new features.

  • Expect the output of every service to become the

input to another, as yet unknown, service..

  • Design and build software to be tried early, ideally

within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.

  • Use tools …to lighten an engineering task, even if you

have to detour to build the tools and expect to throw some of them out after you’ve finished using them.

slide-46
SLIDE 46
  • Make each service do one thing well. To do a new job,

build afresh rather than complicate existing services by adding new features.

  • Expect the output of every service to become the input

to another, as yet unknown, service..

  • Design and build software to be tried early, ideally

within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.

  • Use tools in preference to unskilled help to lighten an

engineering task, even if you have to detour to build the tools and expect to throw some of them out after you’ve finished using them.

agile

cloud/ micro-services

DevOps?

  • nly slightly modified from: ”Bell Labs’ Unix Timesharing Systems” Documentation 1978:

https://ia902701.us.archive.org/12/items/bstj57-6-1899/bstj57-6-1899.pdf

slide-47
SLIDE 47

Questions

linkedin.com/in/finbarrjoy finbarr.joy@gmail.com @FinbarrJoy

we’re hiring !