Inspect and Adapt Then What? @coreyhaines Agile! Agility! - - PowerPoint PPT Presentation

▶
inspect and adapt
SMART_READER_LITE
LIVE PREVIEW

Inspect and Adapt Then What? @coreyhaines Agile! Agility! - - PowerPoint PPT Presentation

Jan 18, 2023 1.08k likes •1.64k views

Inspect and Adapt Then What? @coreyhaines Agile! Agility! Agility Feedback Agility Minimize time between Doing Something Agility Finding out if it was the Right Thing To Do Agile Methodology (XP, Scrum, etc) vs Agility

slide-1
SLIDE 1

Inspect and Adapt

Then What? @coreyhaines

slide-2
SLIDE 2
slide-3
SLIDE 3
slide-4
SLIDE 4

Agile!

slide-5
SLIDE 5

Agility!

slide-6
SLIDE 6

Agility

Feedback

slide-7
SLIDE 7

Agility

Minimize time between
 Doing Something

slide-8
SLIDE 8

Agility

Finding out if it was the 
 Right Thing To Do

slide-9
SLIDE 9

Agile

Methodology (XP, Scrum, etc)
 vs
 Agility

slide-10
SLIDE 10

Inspect and Adapt

slide-11
SLIDE 11

Inspect and Adapt

Fixed Methodology
 and
 Context-Specific Practices

slide-12
SLIDE 12

This talk

Example from my last two companies Different Techniques Different Contexts

slide-13
SLIDE 13

ME!

That’s Squeaks ——>

slide-14
SLIDE 14

Me!

  • Software Developer
  • Introduced to Extreme Programming (XP) in 2004
  • Been running that way ever since
  • Currently CTO of Hearken
  • Does not have the answers, only experiences
  • Loves Cats!
slide-15
SLIDE 15
slide-16
SLIDE 16

Examples

slide-17
SLIDE 17

Planning

  • Two companies: PowerReviews and Hearken
  • Different Contexts
slide-18
SLIDE 18

PowerReviews

  • Small, 20-person company
  • 5 different stakeholder sections
  • 3 developers
  • Single platform
slide-19
SLIDE 19

Planning Problem #1: Estimation

  • 3 developers
  • Only one familiar with codebase
  • One developer very junior
  • How do you estimate?
slide-20
SLIDE 20

How do you estimate?

Wrong Question

slide-21
SLIDE 21

Why must we estimate?

slide-22
SLIDE 22

What value do we get from Estimation?

slide-23
SLIDE 23

Deadline vs Scope

slide-24
SLIDE 24

Replace with small, similar tasks by splitting feature?

slide-25
SLIDE 25

Focus on scope

sequence appropriately

slide-26
SLIDE 26

Often don’t have to do everything

slide-27
SLIDE 27

Prefer Removing Something

If find struggle or problem with process

slide-28
SLIDE 28

Planning Problem #2: Prioritization

  • 5 stakeholder sections for 3 products
  • Everyone votes for their own cards
  • Loudest person gets their cards selected
slide-29
SLIDE 29

Sales Content Moderation Technology Data Prioritization Queue

slide-30
SLIDE 30

Priority???

slide-31
SLIDE 31

Value???

slide-32
SLIDE 32

Time Value to Company

Low Value High Value Quick To Do Long To Do

Courtesy Arlo Belshi
slide-33
SLIDE 33

Value-Based Sequencing

  • Based on Financial Value
  • Money Earned
  • Money Saved
  • Sequence by value
slide-34
SLIDE 34

Example: Fraud Flags

  • Moderators look for fraudulent reviews
  • 4 steps
  • Click name to get IP
  • Navigate to IP Search Page
  • Enter IP
  • See how many / frequency of reviews from IP
slide-35
SLIDE 35

Hard to get this prioritized

  • ver Sales team requests
slide-36
SLIDE 36

Value Calculation

  • Have to do for every review
  • 20 seconds per review
  • ~ 200 per day
  • (20 sec / review * 200 review / day ) ~ 1 hour / day
  • 75 reviewers = 75 hours per day
  • $20 / hour * 75 hours = $1500 / day
slide-37
SLIDE 37

Got Sequenced!

slide-38
SLIDE 38

This can’t work!

  • Time-boxed experiments
  • Let’s try for 2 months
  • Put meeting on calendar to

address whether this works

slide-39
SLIDE 39

Hearken

Tiny, 9-person company (started at 3, now at 9) 1 stakeholder section for single product 3 developers

slide-40
SLIDE 40

Planning

  • Start with no estimation
  • Start with weekly planning meeting
  • Stakeholders sequence tasks
slide-41
SLIDE 41

Problems

  • Value???
  • Money? Hard to gauge. Early-stage.
  • Save time for customers? Hard to gauge. Early-

stage.

  • Sequencing becomes rubber-stamp
  • Rarely changes order of sequence
  • Take time from everyone’s day
slide-42
SLIDE 42

Communication

slide-43
SLIDE 43

Communication

  • Small team => Fairly regular communication
  • “Story cards as placeholder for conversation”
  • Each story card is defined at time of draw
  • Expect that story card is split into more than one,

put new cards into backlog

slide-44
SLIDE 44

Weekly Planning

  • Present suggested sequence
  • Anyone have objections?
  • Done!
slide-45
SLIDE 45

New Product Weekly Planning

  • Building new product
  • Lots of features to build
  • Sequencing difficult as no context
  • Regular “showcase” demos of progress
  • Using new language/framework (Elm)
slide-46
SLIDE 46

Script-based Planning

Create script for the showcase What does the product currently do? What doesn’t it do? Work until it can do what it doesn’t do.

slide-47
SLIDE 47

Return to story cards

after release of product

slide-48
SLIDE 48

Context Matters

You are special Time-based experiments Frequently change

slide-49
SLIDE 49
slide-50
SLIDE 50

Inspect and Adapt

Then What? @coreyhaines

Buy my book! https://leanpub.com/4rulesofsimpledesign/

Inspect and Adapt

Inspect and Adapt, Then What? @coreyhaines