Patterns of Effective Teams • Dan North • GOTO 2017

This presentation was recorded at GOTO Chicago 2017. #GOTOcon #GOTOchgo
gotochgo.com
Dan North - Originator of Behavior Driven Development (BDD) & Principal Consultant @daniel-terhorst-north
ABSTRACT
Some teams are orders of magnitude more effective than others, turning around business solutions in days or even hours. Their secret is a combination of smart technology choices, great development habits and a powerful team dynamic. In this talk [...]
Download slides and read the full abstract here:
gotochgo.com/2017/sessions/62
/ gotocon
/ goto-
/ gotoconferences
#Agile #EffectiveTeams #BDD
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
Sign up for updates and specials at gotopia.tech/newsletter
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
kzbin.info...

[@bluesprodeep2079]

Dreyfus Squared is a mind-opener. Thanks alot.

[@ngfgrant]

00:00 - Background / Reason for Talk 02:57 - Effective vs Productive Teams 04:08 - Introduction to Effective Team Patterns 05:12 - Dreyfus Squared Pattern 17:10 - Shallow Silos Pattern 21:57 - Near and Far Pattern 27:03 - Warm Welcome Pattern 30:28 - Seize the Day Pattern (stand ups) 38:27 - Code Critique Pattern 46:19 - Hack Day Pattern 47:30 - Conclusion and Lean Pub Book

[@DavidHarris74]

Great presentation, Dan. I enjoyed not only the practical content but your humble and open presentation style.

[@NoLiesWereTold]

Best talk i've seen in a while

[@nisimjoseph]

AMAZING lecture! thank you!

[@toralfrichter2011]

Big grin: inverse truck factor; Really good practical stuff: shallow silos, the real purpose of the stand-up, near and far coaching, ... Thanks for this one!

[@BB1CC666]

A great talk means coming from the real world and being applicable to the real world in a tangible way....like this talk....

[@SpencerSkelly]

What a great talk

[@StephanOudmaijer]

Great speaker! Great talk!

[@LearnTwice]

This was great! We use code critique and it is wonderful. I wish to try coding in pairs but have not had a chance yet.

[@MatthewChaplain]

17:50 I had a mouthful of coffee, damnit!

[@JaysonSunshine]

Great chat!

[@EnhoKuo]

Good!

[@nelsonc5339]

03:39 _effective_ teams manage to solve gnarly problems with tiny bits of software. 03:51 I don't want "productive" teams, I want people who are really good at understanding the *heart* of the problem and just solving for that. 30:28 Standups!

[@alessandrob.g.4524]

Is this the lecture Jim Coupling was mentioning in the same GOTO Conference?

[@BryonLape]

I really want to work for a company as he describes.

[@logiciananimal]

You've discovered a legitimate use for a chain letter! That's nifty.

[@chocoicecreamisupportukrai8803]

Underated

[@archmad]

this is a slap to full stack devs

[@LoneWolf-wp9dn]

Its 2020 and the book is still at 7%

[@LagusAT1]

2022 7% And it is effective or productive? :D

[@iaintoft7003]

Cornwall is emmets, not Somerset!

[@NeilHighley]

Who is the programmer Dan mentions at the two minute mark

[@doneitel]

Kent Beck

[@vadergrd]

but but but ... you need to be on alert if someone new is coming or what if the last person arrived already left ... is the wiki only for a department?? is it a small company??

[@BestHKisDLM]

What we did is that we have started on a team level and iterated until it was sufficient enough to pass to whole department. Then we decided not to. Other teams may edit/copy parts of the shared sections, but you really do not want it to grow beyond certain point. When the warm welcome is beyond 3 standard pages, its way too much.

[@kobac8207]

"I hit the round thing with a stick thing"

[@soberhippie]

The ending sounds a bit like the "Life of Brian"

[@SKyrim190]

42:08 "These are both made up words" Every word is made up...