the geek's guide to leading teams

47
The Geek’s Guide to Leading Teams @patkua Patrick Kua

Upload: patrick-kua

Post on 14-Jul-2015

9.919 views

Category:

Leadership & Management


1 download

TRANSCRIPT

Page 1: The Geek's Guide to Leading Teams

The Geek’s Guide to Leading Teams

@patkuaPatrick Kua

Page 2: The Geek's Guide to Leading Teams

Available on leanpub (http://tiny.cc/twtl)

Page 3: The Geek's Guide to Leading Teams

Why do we need a Tech Lead?

Page 4: The Geek's Guide to Leading Teams

Why do we need a Tech Lead?

Page 5: The Geek's Guide to Leading Teams
Page 6: The Geek's Guide to Leading Teams
Page 7: The Geek's Guide to Leading Teams

?

Page 8: The Geek's Guide to Leading Teams

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

@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

@julianboot

Page 9: The Geek's Guide to Leading Teams

A simple test for an effective Tech Lead...

Page 10: The Geek's Guide to Leading Teams

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

Yes

No

Page 11: The Geek's Guide to Leading Teams

What do effective Tech Leads focus on?

Page 12: The Geek's Guide to Leading Teams

Tech People

Business You

Page 13: The Geek's Guide to Leading Teams

The “Tech” in Tech Lead

Page 14: The Geek's Guide to Leading Teams

TECH

Do effective Technical Leaders need to code?

Definitely!

At least 30% of the time with the team

Page 15: The Geek's Guide to Leading Teams

http://bit.ly/15Rm4z

Page 16: The Geek's Guide to Leading Teams

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

http://bit.ly/15Rm4z

Page 17: The Geek's Guide to Leading Teams

http://bit.ly/15Rm4z

““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...””

Page 18: The Geek's Guide to Leading Teams

Consistency over Cleverness

Page 19: The Geek's Guide to Leading Teams

http://www.emacswiki.org/emacs/TabsSpacesBoth

Page 20: The Geek's Guide to Leading Teams

Tabs OR Spaces

2 Spaces OR 4 Spaces

CamelCase OR Underscore

Curly brace end of line OR next line

Brackets OR not

Page 21: The Geek's Guide to Leading Teams

Team Culture

Page 22: The Geek's Guide to Leading Teams

How 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?

Team Culture

Page 23: The Geek's Guide to Leading Teams

Vision

Page 24: The Geek's Guide to Leading Teams

Vision

Yes

No

Can everyone draw the same architecture diagram?

Page 25: The Geek's Guide to Leading Teams

Free download: http://bit.ly/1Esrn7f

Page 26: The Geek's Guide to Leading Teams

Riding Paradox

Page 27: The Geek's Guide to Leading Teams

Riding Paradox

“Paradox” by Michael Berg

Consistency vs Improvement

Delivering vs Learning

Technical vs Business

Page 28: The Geek's Guide to Leading Teams

People

Page 29: The Geek's Guide to Leading Teams

Analytical

Activator

Intellection

Achiever

Strategic

Input

Woo

Page 30: The Geek's Guide to Leading Teams

Collective Accuracy = Average Accuracy

+ Diversity*

* Requires ability to integrate

Page 31: The Geek's Guide to Leading Teams

Trust isn’t built in one day

Page 32: The Geek's Guide to Leading Teams

Growing People

Page 33: The Geek's Guide to Leading Teams

Skill/Ability

Cha

lleng

eH

IGH

LOW

LOW HIGH

Page 34: The Geek's Guide to Leading Teams

Skill/Ability

Cha

lleng

eH

IGH

LOW

LOW HIGH

Anxiety

Page 35: The Geek's Guide to Leading Teams

Skill/Ability

Cha

lleng

eH

IGH

LOW

LOW HIGH

Boredom

Page 36: The Geek's Guide to Leading Teams

Skill/Ability

Cha

lleng

eH

IGH

LOW

LOW HIGH

FlowAnxiety

Boredom

Page 37: The Geek's Guide to Leading Teams

Learning Activities

Brown Bag sessions

Spike Showcases

Team code reviews

Technical Retrospectives

Pair Programming

Video/Book Club

Page 38: The Geek's Guide to Leading Teams

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

Beware the bad apple

Page 39: The Geek's Guide to Leading Teams

Bridging the Business

Page 40: The Geek's Guide to Leading Teams

Technical Business

Translating between realms

Page 41: The Geek's Guide to Leading Teams

Business Opportunities

Page 42: The Geek's Guide to Leading Teams

You

Page 43: The Geek's Guide to Leading Teams
Page 44: The Geek's Guide to Leading Teams
Page 45: The Geek's Guide to Leading Teams

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 46: The Geek's Guide to Leading Teams

People The Tech of a Tech Lead

Bridging the Business You

Page 47: The Geek's Guide to Leading Teams

Questions?

@patkuaPatrick Kua