Video: SWARMing: Scaling Without A Religious Methodology - Katherine Kirk & Dan North

November 13th, 2020

SWARMing: Scaling Without A Religious Methodology - Katherine Kirk & Dan North

(https://www.youtube.com/watch?v=q87wNNiygaM)

 

no description for image available

 

no description for image available

 

no description for image available

 

lead time: time between 'I have a need' and 'thank you'

 

no description for image available

...oh crap...

I'll wait till you get back to me

 

no description for image available

"we need to do the method better!"

"we need to do it more!"

 

2 simple concepts

trigger leadership and help go from large to small scale delivery

 

1)

no description for image available

aka 3 characteristics of context

 

what if we work with the model?

no description for image available

dissatisfaction as feedback for learning

 

 

no description for image available

"""

What's happening, that these elements are going wrong?

we need to do the method better?

we need to do it more?

"""

 

no description for image available

 

 

no description for image available

degradation:

dysfunction: eg. body illness

expiry

 

no description for image available

 

no description for image available

any method: will degrade and expire

 

no description for image availableno description for image available

 

no description for image availableno description for image available

 

no description for image available

things we need

things we do

 

no description for image available

education: eg. don rinontsen's product development flow is really hard ; safe is intro to how flow works

practice

time: 3-5 years

investment

influence: access to ppl who can change structure, privilege

communications:

external help

leadership:

- consistent: if you rotate CTO every x months, don't bother

- invested: not a side project

- resilient: up and down the org

 

[ ] don rinontsen's product development flow

 

no description for image available

assume positive intent

pathological behaior is from the system

ToC: you can't know the next one, until this one is done

 

no description for image available

see what is there

1) vidualize: value stream mapping

- work, queue, blockers, dependency, interdepency

2) stabilize, even if it's bad, as long as it's consistent

3) optimize

 

no description for image available

based on data, learn

 

no description for image available

there is no "The Answer"

start with a method, but expect degradation

 

no description for image available

you'll tire out

 

no description for image available

with degradation, change

 

no description for image available

 

There is hope: "we can understand the universe, we just can't beat it"

 

no description for image available