Page 1
Tech Lead TipsRouan Wilsenach@rouanw
Page 2
Tech lead tips
● Being the person who cares● Helping the flow of work● Ready for change● Being a leader● The 80/20 rule● Being a little meta
Page 3
Being the person who cares
Page 4
Caring
Back to first principles
Page 5
Helping the flow of work
Page 6
Flow
1 dev, 1 customer
Page 7
Flow
Technical advisor
Page 9
Flow
Looking ahead
Page 10
Flow
Splitting stories
Page 11
Flow
Technical Spikes
Page 12
Flow
Look for patterns and bottlenecks
Page 13
Flow
Cross-role involvement
Page 15
Change
Last responsible moment
Page 16
Change
Automated tests
Page 17
Change
Make coding easier
Page 18
Change
Emergent design and refactoring practices
Page 19
Change
Simplicity
Page 20
Technical Debt
http://martinfowler.com/bliki/TechnicalDebtQuadrant.html
Page 21
Change
Code review
Page 22
Change
Knowledge sharing
“data showed an overall increase in velocity when tasks were consistently assigned to the least qualified person”
http://user.it.uu.se/~carle/softcraft/notes/PromiscuousPairing.pdf
Page 23
Change
Clear the road to production
Page 24
Change
Using data to know what to change
Page 26
Leading
Autonomous team with shared principles
Page 27
Leading
Strong opinions, loosely held
Page 28
Leading
Dealing with ambiguity
Page 29
Leading
Aim to be redundant
Page 30
Leading
Knowing your team
Page 31
Leading
Have the tough conversations
Page 32
Leading
Managing disagreement
Page 35
“roughly 80% of the effects come from 20% of the
causes”
- Pareto principle
Page 36
80 / 20
Uphold & extend
Page 37
80 / 20
Delegation vs building individuals
Page 38
Being a little meta
Page 39
Being meta
Bigger picture
Page 40
Being meta
Plug into the tech community
Page 41
Being meta
Observant
Page 42
Being meta
Guide your team
Page 43
Being meta
Eavesdrop