Tech lead tips

of 43 /43
Tech Lead Tips Rouan Wilsenach @rouanw

Embed Size (px)

Transcript of Tech lead tips

  • Tech Lead TipsRouan [email protected]

  • 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

  • Being the person who cares

  • Caring

    Back to first principles

  • Helping the flow of work

  • Flow

    1 dev, 1 customer

  • Flow

    Technical advisor

  • Flow

    Planning

  • Flow

    Looking ahead

  • Flow

    Splitting stories

  • Flow

    Technical Spikes

  • Flow

    Look for patterns and bottlenecks

  • Flow

    Cross-role involvement

  • Ready for change

  • Change

    Last responsible moment

  • Change

    Automated tests

  • Change

    Make coding easier

  • Change

    Emergent design and refactoring practices

  • Change

    Simplicity

  • Technical Debt

    http://martinfowler.com/bliki/TechnicalDebtQuadrant.html

    http://martinfowler.com/bliki/TechnicalDebtQuadrant.htmlhttp://martinfowler.com/bliki/TechnicalDebtQuadrant.html

  • Change

    Code review

  • 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

    http://user.it.uu.se/~carle/softcraft/notes/PromiscuousPairing.pdfhttp://user.it.uu.se/~carle/softcraft/notes/PromiscuousPairing.pdfhttp://user.it.uu.se/~carle/softcraft/notes/PromiscuousPairing.pdfhttp://user.it.uu.se/~carle/softcraft/notes/PromiscuousPairing.pdf

  • Change

    Clear the road to production

  • Change

    Using data to know what to change

  • Being a leader

  • Leading

    Autonomous team with shared principles

  • Leading

    Strong opinions, loosely held

  • Leading

    Dealing with ambiguity

  • Leading

    Aim to be redundant

  • Leading

    Knowing your team

  • Leading

    Have the tough conversations

  • Leading

    Managing disagreement

  • Leading

    Fun team

  • The 80 / 20 rule

  • roughly 80% of the effects come from 20% of the

    causes

    - Pareto principle

    https://en.wikipedia.org/wiki/Pareto_principle

  • 80 / 20

    Uphold & extend

  • 80 / 20

    Delegation vs building individuals

  • Being a little meta

  • Being meta

    Bigger picture

  • Being meta

    Plug into the tech community

  • Being meta

    Observant

  • Being meta

    Guide your team

  • Being meta

    Eavesdrop