130
The Geek’s Guide to Leading Teams @patkua ThoughtWorks

The Geek’s Guide to Leading Teams

Embed Size (px)

DESCRIPTION

Presentation given at GotoAarhus 2012 on the Humans At Work track

Citation preview

Page 1: The Geek’s Guide to Leading Teams

The Geek’s Guide to Leading Teams

@patkuaThoughtWorks

Page 2: The Geek’s Guide to Leading Teams

The Geek’s Guide to Leading Teams

@patkua@patkuaThoughtWorks

Page 3: The Geek’s Guide to Leading Teams
Page 4: The Geek’s Guide to Leading Teams
Page 5: The Geek’s Guide to Leading Teams
Page 6: The Geek’s Guide to Leading Teams

Who am I?

Page 7: The Geek’s Guide to Leading Teams

Who am I?

Page 8: The Geek’s Guide to Leading Teams

Who am I?

Programmer

Tech Lead Agile Coach

Me!

Page 9: The Geek’s Guide to Leading Teams

Who am I?

Programmer

Tech Lead Agile Coach

Me!

Author

http://tiny.cc/retrobook

Page 10: The Geek’s Guide to Leading Teams
Page 11: The Geek’s Guide to Leading Teams

Why do we need a Tech Lead?

Page 12: The Geek’s Guide to Leading Teams
Page 13: The Geek’s Guide to Leading Teams
Page 14: The Geek’s Guide to Leading Teams
Page 15: The Geek’s Guide to Leading Teams
Page 16: The Geek’s Guide to Leading Teams
Page 17: The Geek’s Guide to Leading Teams
Page 18: The Geek’s Guide to Leading Teams
Page 19: The Geek’s Guide to Leading Teams
Page 20: The Geek’s Guide to Leading Teams
Page 21: The Geek’s Guide to Leading Teams

?

Page 22: The Geek’s Guide to Leading Teams
Page 23: The Geek’s Guide to Leading Teams
Page 24: The Geek’s Guide to Leading Teams

Think this doesn’t happen in the real world?

Page 25: The Geek’s Guide to Leading Teams

@julianboot

Page 26: The Geek’s Guide to Leading Teams

Source: http://twitter.com/julianboot/status/232830267822309376

@julianboot

@thejayfields: I had ten guys on my last project, all of them had opinions and all

of them were expressed in the code base #speakerconf

Page 27: The Geek’s Guide to Leading Teams
Page 28: The Geek’s Guide to Leading Teams

A simple test for an effective Tech Lead...

Page 29: The Geek’s Guide to Leading Teams

Does the codebase look like it was written by a single person?

Yes

No

Page 30: The Geek’s Guide to Leading Teams
Page 31: The Geek’s Guide to Leading Teams

What does a good Tech Lead focus on?

Page 32: The Geek’s Guide to Leading Teams

P

P

P

Page 33: The Geek’s Guide to Leading Teams

Programming

P

P

Page 34: The Geek’s Guide to Leading Teams

Programming

People

P

Page 35: The Geek’s Guide to Leading Teams

Programming

People

Process

Page 36: The Geek’s Guide to Leading Teams

Programming

Page 37: The Geek’s Guide to Leading Teams

Programming

Do effective Technical Leaders need to code?

Page 38: The Geek’s Guide to Leading Teams

Programming

Do effective Technical Leaders need to code?

Definite

ly!

Page 39: The Geek’s Guide to Leading Teams

Programming

Do effective Technical Leaders need to code?

Definite

ly!

Page 40: The Geek’s Guide to Leading Teams

Programming

Do effective Technical Leaders need to code?

Definite

ly!

At least 30% of the time with the team

Page 41: The Geek’s Guide to Leading Teams

Programming http://bit.ly/15Rm4z

Page 42: The Geek’s Guide to Leading Teams

Programming

“...respect is the currency of the realm”

http://bit.ly/15Rm4z

Page 43: The Geek’s Guide to Leading Teams

Programming

““The amount of respect an IT pro pays someone is a measure of how tolerable that person is when it comes to getting things done...””

http://bit.ly/15Rm4z

Page 44: The Geek’s Guide to Leading Teams

Programming

Consistency over Cleverness

Page 45: The Geek’s Guide to Leading Teams

Programming

Page 46: The Geek’s Guide to Leading Teams

Programming

Tabs OR Spaces

2 Spaces OR 4 Spaces

CamelCase OR Underscore

Curly brace end of line OR next line

Brackets OR not

Page 47: The Geek’s Guide to Leading Teams

Programming

Tabs OR Spaces

2 Spaces OR 4 Spaces

CamelCase OR Underscore

Curly brace end of line OR next line

Brackets OR not

Page 48: The Geek’s Guide to Leading Teams

Programming

Tabs OR Spaces

2 Spaces OR 4 Spaces

CamelCase OR Underscore

Curly brace end of line OR next line

Brackets OR not

There are more important topics to spend time on...

Page 49: The Geek’s Guide to Leading Teams

Programming

Team Culture

Page 50: The Geek’s Guide to Leading Teams

Programming

Team Culture

Page 51: The Geek’s Guide to Leading Teams

Programming

Team CultureHow long does the build

stay broken?

Page 52: The Geek’s Guide to Leading Teams

Programming

Team CultureHow long does the build

stay broken?Do people avoid conflict?

Page 53: The Geek’s Guide to Leading Teams

Programming

Team CultureHow long does the build

stay broken?Do people avoid conflict?

Do people offer new ideas?

Page 54: The Geek’s Guide to Leading Teams

Programming

Team CultureHow long does the build

stay broken?Do people avoid conflict?

Do people offer new ideas?Do people flag when they

need help?

Page 55: The Geek’s Guide to Leading Teams

Programming

Team CultureHow long does the build

stay broken?Do people avoid conflict?

Do people offer new ideas?Do people flag when they

need help?Do people feel okay to admit being wrong?

Page 56: The Geek’s Guide to Leading Teams

Programming

Vision

Page 57: The Geek’s Guide to Leading Teams

People

Page 58: The Geek’s Guide to Leading Teams

People

Strength in Diversity

Page 59: The Geek’s Guide to Leading Teams

People

Page 60: The Geek’s Guide to Leading Teams

People

Analytical

Activator

Intellection

Achiever

Strategic

Input

Woo

Page 61: The Geek’s Guide to Leading Teams

People Source: Catalyst (2007) http://bit.ly/nEEfGX

Fortune 500 companies with 3 or more women on the Board gain a significant performance

advantage over those with the fewest

Page 62: The Geek’s Guide to Leading Teams

People Source: Catalyst (2007) http://bit.ly/nEEfGX

Fortune 500 companies with 3 or more women on the Board gain a significant performance

advantage over those with the fewest

Return on Sales

73% 83% 112%

Return on Equity Return on Invested Capital

Page 63: The Geek’s Guide to Leading Teams

People Source: Credit Suisse Research Institute (August 2012) http://bit.ly/Oozuvl

“...over the past six years, companies with at least some female board

representation outperformed those with no women on the board in terms of share price performance.”

Page 64: The Geek’s Guide to Leading Teams

People Source: Credit Suisse Research Institute (August 2012) http://bit.ly/Oozuvl

“...over the past six years, companies with at least some female board

representation outperformed those with no women on the board in terms of share price performance.”

Return on Equity

12%

Page 65: The Geek’s Guide to Leading Teams

People Source: Credit Suisse Research Institute (August 2012) http://bit.ly/Oozuvl

“...over the past six years, companies with at least some female board

representation outperformed those with no women on the board in terms of share price performance.”

16%

Return on EquityReturn on Equity

12%

Page 66: The Geek’s Guide to Leading Teams

People

Page 67: The Geek’s Guide to Leading Teams

People

Collective Accuracy = Average Accuracy +

Diversity*

Page 68: The Geek’s Guide to Leading Teams

People

Collective Accuracy = Average Accuracy +

Diversity*

* Requires ability to integrate

Page 69: The Geek’s Guide to Leading Teams

People

Trust isn’t built in one day

Page 70: The Geek’s Guide to Leading Teams

People

Growing People

Page 71: The Geek’s Guide to Leading Teams

People

Skill/Ability

Cha

lleng

eH

IGH

LOW

LOW HIGH

Source: Csikszentmihalyi, Flow (1990)

Page 72: The Geek’s Guide to Leading Teams

People

Skill/Ability

Cha

lleng

eH

IGH

LOW

LOW HIGH

Anxiety

Source: Csikszentmihalyi, Flow (1990)

Page 73: The Geek’s Guide to Leading Teams

People

Skill/Ability

Cha

lleng

eH

IGH

LOW

LOW HIGH

Anxiety

Boredom

Source: Csikszentmihalyi, Flow (1990)

Page 82: The Geek’s Guide to Leading Teams

People

Maximising Potential

Page 83: The Geek’s Guide to Leading Teams

People

Page 84: The Geek’s Guide to Leading Teams

People

Skills

Page 85: The Geek’s Guide to Leading Teams

People

Skills

Strengths

Page 86: The Geek’s Guide to Leading Teams

People

Skills

StrengthsGoals

Page 87: The Geek’s Guide to Leading Teams

People

Skills

StrengthsGoals

Interests

Page 88: The Geek’s Guide to Leading Teams

People

Skills

StrengthsGoals

Interests

Sweet Spot

Page 89: The Geek’s Guide to Leading Teams

People

Skills

StrengthsGoals

Interests

Page 90: The Geek’s Guide to Leading Teams

People

Skills

StrengthsGoals

Interests

Page 91: The Geek’s Guide to Leading Teams

People

Skills

StrengthsGoals

Interests

Page 92: The Geek’s Guide to Leading Teams

People

Skills

StrengthsGoals

Interests

Page 93: The Geek’s Guide to Leading Teams

People

Learning Activities

Page 94: The Geek’s Guide to Leading Teams

People

Learning Activities

Brown Bag sessions

Spike Showcases

Team code reviews

TechnicalRetrospectives

Pair Programming

Video/Book Club

Page 95: The Geek’s Guide to Leading Teams

People

Page 96: The Geek’s Guide to Leading Teams

People

Beware the bad apple

“Bad Is Stronger Than Good” (2001) Baumeister et al

Page 97: The Geek’s Guide to Leading Teams

Process

Page 98: The Geek’s Guide to Leading Teams

Process

Page 99: The Geek’s Guide to Leading Teams

Process

Is it okay to tell people what to do?

Situational Leadership Model

Page 100: The Geek’s Guide to Leading Teams

Process

Is it okay to tell people what to do?

Yes

(but only

sometim

es)

Situational Leadership Model

Page 101: The Geek’s Guide to Leading Teams

Process

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Situational Leadership Model

Page 102: The Geek’s Guide to Leading Teams

Process

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Situational Leadership Model

Page 103: The Geek’s Guide to Leading Teams

Process

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Directing

Situational Leadership Model

Page 104: The Geek’s Guide to Leading Teams

Process

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Coaching

Directing

Situational Leadership Model

Page 105: The Geek’s Guide to Leading Teams

Process

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Supp

ortin

g Coaching

Directing

Situational Leadership Model

Page 106: The Geek’s Guide to Leading Teams

Process

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Supp

ortin

g Coaching

DirectingDelegat

ing

Situational Leadership Model

Page 107: The Geek’s Guide to Leading Teams

Process Situational Leadership Model

Page 108: The Geek’s Guide to Leading Teams

Process Situational Leadership Model

Page 109: The Geek’s Guide to Leading Teams

Process

Development level of an individual

Situational Leadership Model

Page 110: The Geek’s Guide to Leading Teams

Process

Dev

elop

ing

Development level of an individual

Dev

elop

ed

Situational Leadership Model

Page 111: The Geek’s Guide to Leading Teams

Process

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Situational Leadership Model

Page 112: The Geek’s Guide to Leading Teams

Process

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Low-some competence

Low commitment

Situational Leadership Model

Page 113: The Geek’s Guide to Leading Teams

Process

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Low-some competence

Low commitmentVariable commitment

Moderate-high competence

Situational Leadership Model

Page 114: The Geek’s Guide to Leading Teams

Process

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Low-some competence

Low commitmentVariable commitment

Moderate-high competence

High commitment

High competence

Situational Leadership Model

Page 115: The Geek’s Guide to Leading Teams

Process

Tuckman’s Model

Page 116: The Geek’s Guide to Leading Teams

Process Tuckman’s Stages of Group Development

Page 117: The Geek’s Guide to Leading Teams

Process

Forming

Tuckman’s Stages of Group Development

Page 118: The Geek’s Guide to Leading Teams

Process

Forming Storming

Tuckman’s Stages of Group Development

Page 119: The Geek’s Guide to Leading Teams

Process

Forming Storming Norming

Tuckman’s Stages of Group Development

Page 120: The Geek’s Guide to Leading Teams

Process

Forming Storming Norming Performing

Tuckman’s Stages of Group Development

Page 121: The Geek’s Guide to Leading Teams

Process

Forming Storming Norming Performing Adjourning

Tuckman’s Stages of Group Development

Page 122: The Geek’s Guide to Leading Teams

Process

Forming Storming Norming Performing Adjourning

Tuckman’s Stages of Group Development

Page 123: The Geek’s Guide to Leading Teams

Process

“Essentially, all models are wrong, but some are useful.”

- George E. P. Box

Page 124: The Geek’s Guide to Leading Teams

Process

Make time for you

Page 125: The Geek’s Guide to Leading Teams

Process

Page 126: The Geek’s Guide to Leading Teams

Process

Page 127: The Geek’s Guide to Leading Teams

Process

9am

6pm

Monday Tuesday Wednesday Thursday Friday

Email Time Email Time

Planning Time

1:1s

Email Time

Planning Time

Email Time

Next week planning

Page 128: The Geek’s Guide to Leading Teams

ProcessProgramming People

Concluding Thoughts

Page 129: The Geek’s Guide to Leading Teams

Questions?

http://jobs.thoughtworks.com/

are hiring

@patkua