Tweet
Tweet

Slide 1

Slide 1 text

armakuni.com Lean Agile Delivery & Coaching Network London - February 2020 Benedict Steele - @benedictsteele How to be an Evil Scientist

Slide 2

Slide 2 text

Why are we evil enough to be standing in front of you?

Slide 3

Slide 3 text

How to be an Evil Scientist 1. Choose an evil name

Slide 4

Slide 4 text

Your first name A The Evil N The Crazy B The Terrifying O The Iron C The Big P The Poison D The Dangerous Q The Bloody E Captain R The Annoying F The Ghostly S The Dangerous G Professor T The Rancid H Doctor U The Invisible I Phantom V The Dastardly J The Brutal W The Atomic K The Unstoppable X The Mega L The Vile Y The Grand M The Dark Z The Vicious

Slide 5

Slide 5 text

Your last name A Shadow N Child B Wizard/Witch O Corpse C Tarantula P Slayer D Skull Q Spider E Mastermind R Creature F Wizard S Werewolf G Ninja T Monster H Devil U Vampire I Freak V Mutant J Beast W Robot K Criminal X Claw L Master Y Machine M Lord/Lady Z Clown

Slide 6

Slide 6 text

How to be an Evil Scientist 1. Choose an evil name 2. Share the most evil thing you’ve ever done

Slide 7

Slide 7 text

This is Billie ● Consulting Engineer for Armakuni ● Quite tall ● Helps people use best practices ● Favourite animal is the capybara ● Evil Name - The Terrifying Monster ● We stole this talk from her, turned it into a workshop and didn’t even say “thank- you”!

Slide 8

Slide 8 text

Not evil enough for you?

Slide 9

Slide 9 text

How to be an Evil Scientist 1. Choose an evil name 2. Share the most evil thing you’ve ever done 3. Learn the rules every evil scientist must follow

Slide 10

Slide 10 text

Evil Scientist Rules Always have lots of evil schemes - you never know if there’s going to be a sequel Always start small Always have an arch-enemy Always have an escape plan Always boast, there’s no point in being evil if you don’t boast about it Never wear capes Never get caught monologuing Always measure everything Always splice things together

Slide 11

Slide 11 text

How to be an Evil Scientist 1. Choose an evil name 2. Share the most evil thing you’ve ever done 3. Learn the rules every evil scientist must follow 4. Discover our arch enemies

Slide 12

Slide 12 text

Our Arch Enemies Waiting Around Kid Captain Defect General Heroics The Crimson Handoff Gold Plated Features Girl Mr Unneeded Process El Manual Work Awful Comms Boy Knowledge Drain Man Constance “Task” Switching The Relearner Rework

Slide 13

Slide 13 text

Our Arch Enemies Partially Completed Work Woman Dr Overly Complex Solutions The Siloed Worker Poor Visibility Man

Slide 14

Slide 14 text

Refuses to collaborate or attend meetings Works unsociable hours Code structure is in their head Believe they don’t need training Poor mentors The go-to person for QAs and support

Slide 15

Slide 15 text

How to be an Evil Scientist 1. Choose an evil name 2. Share the most evil thing you’ve ever done 3. Learn the rules every evil scientist must follow 4. Discover our arch enemies

Slide 16

Slide 16 text

armakuni.com Lethal, Aggressive, Deadly & Cruel Network London - January 2020 The Terrifying Werewolf How to be an Evil Scientist

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Ladies and gentlemen: the story you are about to hear is true. Only the names have been changed to protect the innocent.

Slide 20

Slide 20 text

Department for Feline Empowerment

Slide 21

Slide 21 text

This Dastardly Ashley

Slide 22

Slide 22 text

Pair Programming Pipelines Test-Driven Development

Slide 23

Slide 23 text

?

Slide 24

Slide 24 text

It worked!

Slide 25

Slide 25 text

Superheroes were being defeated

Slide 26

Slide 26 text

She was asked to help Sam and Alex do it too

Slide 27

Slide 27 text

So she did

Slide 28

Slide 28 text

...but she had demands!

Slide 29

Slide 29 text

They did exactly the same thing, but it didn’t work

Slide 30

Slide 30 text

They were thwarted by super heroes at every turn

Slide 31

Slide 31 text

And they all went to jail

Slide 32

Slide 32 text

Thankfully Ashley always has an escape plan

Slide 33

Slide 33 text

The future is already here - it’s just not evenly distributed — William Gibson

Slide 34

Slide 34 text

Every team is different

Slide 35

Slide 35 text

The Department for Feline Empowerment needed to go back to the drawing board

Slide 36

Slide 36 text

Ashley’s first few weeks

Slide 37

Slide 37 text

Ashley didn’t monologue - she listened and observed

Slide 38

Slide 38 text

Found the pain points and the gaps between vision and reality

Slide 39

Slide 39 text

Worked out what the problems were and what potential fixes could be

Slide 40

Slide 40 text

Tried them out one by one in real world villainous situations

Slide 41

Slide 41 text

She then looked back to see if they worked

Slide 42

Slide 42 text

What if Alex and Sam took the same approach and experimented with their teams?

Slide 43

Slide 43 text

What does Ashley know about teams?

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

No content

Slide 46

Slide 46 text

TEAM Tools Process People

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

Never get caught monologuing Evil Scientist Rules Always have lots of evil schemes - you never know if there’s going to be a sequel Always start small Always measure everything Always splice things together

Slide 49

Slide 49 text

Empathise Design Thinking Ideate Prototype Test Synthesise

Slide 50

Slide 50 text

Design thinking is a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success. — Tim Brown, CEO of IDEO

Slide 51

Slide 51 text

Stakeholder Mapping Team Metrics Empathise

Slide 52

Slide 52 text

Defining the stakeholders ● Who will be impacted by the project? ● Who will be responsible or accountable for the project? ● Who will have decision authority on the project? ● Who can support the project? ● Who can obstruct the project? ● Who has been involved in this type of project in the past? Keep informed Manage closely Monitor Anticipate and meet needs PMO CEO SA Ops Data PO BA UX EA Dev QA

Slide 53

Slide 53 text

A pattern of shared tacit assumptions that was learned by a group as it solved its problems of external adaptation and internal integration, that has worked well enough to be considered valid and, therefore, to be taught to new members as the correct way to perceive, think, and feel in relation to those problems. — Edgar Schein

Slide 54

Slide 54 text

Westrum typology to define culture Statement Your Score On my team, information is actively sought. On my team, failures are learning opportunities, and messengers of them are not punished. On my team, responsibilities are shared. On my team, cross-functional collaboration is encouraged and rewarded. On my team, failure causes enquiry. On my team, new ideas are welcomed. Scale Strongly Disagree - 1 Disagree - 2 Somewhat disagree -3 Neither agree nor disagree - 4 Somewhat agree - 5 Agree - 6 Strongly agree - 7

Slide 55

Slide 55 text

Westrum typology to measure culture Pathological (power- oriented) Score 6-18 Bureaucratic (rule-oriented) Score 19 - 30 Generative (performance- oriented) Score 31-42 Low co-operation Modest co-operation High co-operation Messengers shot Messengers neglected Messengers trained Responsibilities shirked Narrow responsibilities Risks are shared Bridging discouraged Bridging tolerated Bridging encouraged Failure leads to scapegoating Failure leads to justice Failure leads to enquiry Novelty crushed Novelty leads to problems Novelty implemented

Slide 56

Slide 56 text

Team Cohesion Trust Conflict Commitment Accountability Results Building trust requires vulnerability Healthy conflict implies candid debate Commitment follows healthy conflict To take accountability takes prior commitment Focus on delivering measurable results. Collective and individual accountability, and feedback

Slide 57

Slide 57 text

Deployment frequency Four Key Metrics Lead Time for change Mean time to recovery Change failure percentage Stability Speed

Slide 58

Slide 58 text

Empathise Service Health Check

Slide 59

Slide 59 text

The intent of maturity models is usually benign… because “maturity” sounds a bit… well…. patronizing. Plus, most of our models don’t involve progressing through different levels, and the primary audience is the team itself rather than management. — https://labs.spotify.com/2014/09/16/squad-health-check-model/

Slide 60

Slide 60 text

“Deployment is all automatic” “We security test git on push” “Commit to VCS and the customers have it in seconds” “Anyone can do a deploy!” Continuous Delivery Continuous Delivery “Deployment Joe is the only one who can do that” “That’s the security team’s job” “The customers get it a quarter later” “Only some people can deploy” “We find out direct from our users by... “Our kanban board shows all the work, and where it is” “Our stories usually last no than half a sprint” "We weren’t sure so we ran an experiment” Product & Process Product & Process “I don’t really know what our users think” “Sometimes work comes from the backlog except...” “Sometimes stories last multiple sprints” “That’s the way we’ve always done it” Insert here.... “Good statement” “Another good statement” “Good thing number three” “Fourth good thing” “Number five in the list of things that are good...” Insert here.... “Bad statement” “This thing is bad too” “Terrible, terrible, bad thing” “Bad thing which is the norm, everyone does it but really shouldn’t” “Bad thing that we didn’t even know was bad” “Rather than a sign off process we pair program” “The app gathers metrics and decide what’s next” “Our checks spotted the problem before our customers DID” “We only take on one thing at a time” Lean Management & Monitoring Lean Management & Monitoring “Oh we need to wait for CAB before we release” “No idea how the business decides what to do next” “The customer reported it” “We’re constantly doing 7 or 8 things” “It was a week before we even noticed” Code Quality “Absolutely everything is in source control” “We automatically test on every commit” “There’s only really the master branch” “I can add as many or as few examples as I need” Code Quality “It’s in source control except...” “We manually have a look” “Our branches are around forever and there are loads of them” “...but the data wasn’t like that on prod”

Slide 61

Slide 61 text

Value Stream Mapping Service Blueprint Empathise

Slide 62

Slide 62 text

Value Stream Mapping CUSTOMER CREATE STORY --------- ANALYST DEVELOP FEATURE --------- ENGINEER DEPLOY TO PRE --------- DEL MGR TEST FEATURE --------- LCO AUTO. DEPLOY LT: 1D PT: 1H C&A: 90% AR: 14% LT: 15D PT: 1D C&A: 20% AR: 7% LT: 2D PT: 30 M C&A: 80% AR: 3.5% LT: 14D PT: 10D C&A: 60% AR: 71% TLT: 32D TPT: 11D 1H 30M AC&A: 60% TAR: 35%

Slide 63

Slide 63 text

Synthesise

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

Ideate 1-2-4-All

Slide 66

Slide 66 text

Ideate Hypothesis Generation

Slide 67

Slide 67 text

We believe Will result in We will know we have succeeded when

Slide 68

Slide 68 text

What is our one priority? What do we need to learn? What is our riskiest assumption?

Slide 69

Slide 69 text

Time Box Is the experiment timely? Can we get data faster? Would less data be sufficient? Metrics Qualitative or quantitative? Is it actionable? Is it Measurable? Fail Condition (If this happens, our hypothesis is clearly false!) Early Stop (If this happens, stop! Experiment is broken, retro!) Plan How will you collect the data? Is it Specific? Is it Achievable? Link to any supporting documents.

Slide 70

Slide 70 text

Prototype

Slide 71

Slide 71 text

Test (and share)

Slide 72

Slide 72 text

The future is already here - it’s just not evenly distributed — William Gibson

Slide 73

Slide 73 text

Journal

Slide 74

Slide 74 text

Many different ways Micro Journal Daily Journal Week Notes Blog Talks Ad-hoc

Slide 75

Slide 75 text

Measure

Slide 76

Slide 76 text

What is AWKSS? Awareness Willing Knowledge Skills Support

Slide 77

Slide 77 text

AWKSS Awareness Willing Knowledge Skills Support 1 2 3 4 5

Slide 78

Slide 78 text

AWKSS Awareness Willing Knowledge Skills Support 1 2 3 4 5

Slide 79

Slide 79 text

Copying Ashley’s first week they designed an experiment to run on with their teammates

Slide 80

Slide 80 text

x

Slide 81

Slide 81 text

x

Slide 82

Slide 82 text

No content

Slide 83

Slide 83 text

No content

Slide 84

Slide 84 text

Formulating it as an experiment made it easy get permission to fail (even with a terrifying boss)

Slide 85

Slide 85 text

Focus on value

Slide 86

Slide 86 text

Iterate and work out what works for that specific team

Slide 87

Slide 87 text

This allowed them to crush all opposition

Slide 88

Slide 88 text

And take over the world!

Slide 89

Slide 89 text

89 Today I learned hopefully something I will test that by doing something I will know it works for me when measure shows change in reading

Slide 90

Slide 90 text

Thank you! Come and say ‘Hi!’ @armakunihq @benedictsteele benedict.steele@armakuni.com

Slide 91

Slide 91 text

Thank you!