Video: Patterns of Effective Teams - Dan North
Patterns of Effective Teams - Dan North |
Patterns of Effective Teams - Dan North
https://www.youtube.com/watch?v=lvs7VEsQzKY
8 years in thought works
bring agile in large companies
small team in trading firm
most performant team I've ever seen
have person X in our team
patterns
effective != productive
Patterns
not for beginners
best practices are for beginners
===
Dreyfus Squared
Dreyfus model
Novice: needs rules
nothing else
Advanced beginner: test rules
Competent: applies rules
has internalised
Proficient: falls back on rules
instinct, instinct, insight
don't trust it yet
Expert: transcends rules
no longer think in rules
'expert' chess grandmaster plays different
remember previous games
less effort
Dreyfus Squared
novice + expert = x-(
someone dies
advance + advanced
massive learning
don't put into prod
competent + novice = :-)
proficient + expert = :-D
===
Shallow Silos
people that are interested in a task, will do it better
relaxed about rotating teams
as long as 2 ppl know something
===
Near and Far
interaction between teams
ppl work in vertical
cross functional teams don't work
coaching model
near coach (in team)
far coach (out team)
ppl embedded in the team get together with the person out of team
person out of team must learn
core team, and go out and share
eg. DB, networking
===
Warm Welcome
really caring about someone joining team
laptop
password
1 mail
wiki
Welcome Name
you probably will want to meet these people today
...
...
...
find out the next person who will join, and change the name on top
leaves team
corresponding pattern
celebrate
===
Seize the Day
standups
steering
coordination exercise
cf american football
huddle for next
What's the best possible today we can have?
Status
Tea order + how is it going?
beginning of the standup
no more than 2 minutes
one person goes over the entire board
explains where we are
3 Questions
Kench Weiver is being misunderstood
What work items were moved yesterday
What work items should I see moving today
What work items are being blocked?
people are never blocked, work items can
===
Code Critique
cf movie critique
used to believe "if you do pairing, and do it well, you don't need code reviews"
what are the trade-offs?
idiom:
turn of phrase that happens to be there?
agreed upon
eg. process sequence of values
for
iterator
map-reduces
recursion
-> codebase with 4+ dev
-> multiple and combinations
pythonic
scala opiniated language
unusual stuff becomes signal
have junior ppl critique more experienced ppl code
"why did you do that"
purpose: explain to me why did you do that)
effect: Oh my goodness, that's a really good question
allows idioms to emerge in safe environment
you did this thing I did not think of
what other things did you discard on the way through that?
===
Hack Day
!= hackathon
day where we don't do regular day
day with a team
eg.
bug day
throughput day
===
leanpub
software faster
43 chapters
Patterns of Effective Teams - Dan North |
