Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
JWORKSPowered By Ordina
Everything you want(ed) to know on your
first day as a Technical Lead and that you
can use every d...
ORDINAJWORKS
Bart Blommaerts
Application Architect
Ordina Belgium
@DaggieBe
JWorks
Technical Leadership
What?
@DaggieBe
Technical Leadership
What?
Technical Guidance
@DaggieBe
Technical Leadership
What?
Risks & RequirementsTechnical Guidance
@DaggieBe
Technical Leadership
What?
CoachingRisks & RequirementsTechnical Guidance
@DaggieBe
Technical Leadership
What?
CommunicationCoachingRisks & RequirementsTechnical Guidance
@DaggieBe
Technical Leadership
Do we really need one?
Technical Leadership
Do we really need one?
Everything is awesome !
Technical Leadership
Do we really need one?
Really well-functioning teams
where people share responsibilities
2 sides to a story
Technical responsibilities vs. Leadership activities
Technical Leadership
50 %
@DaggieBe
Technical
1. Advocate for Change
ORIENT
ACT
OBSERVE
DECIDE
Advocate for Change
@DaggieBe
Experience the same pain as
everybody else on the team
@DaggieBe
JWORKSPowered By Ordina
Everything you want(ed) to know on your
first day as a Technical Lead and that you
can use every d...
2. Work through Failure and Success
Things will fail
Prepare for failure
Don’t finger-point
Take responsibility

Learn from failure
@DaggieBe
Celebrate success
Sprint celebrations
Feature complete
Congratulate the team
Congratulate individuals
3. Stay Technical
Stay Technical
Write code
Review code
Technical vision
Evolution of code
@DaggieBe
Networking

Security

Deployment
Consistency
Stay Technical
@DaggieBe
4. Always Available
Technical Design Business Project
Management
Code
Time Management
35% 25% 15% 25%
@DaggieBe
Be realistic
@DaggieBe
5. Be a mentor for your team
Mentor
Mediator
@DaggieBe
Mentor
Mediator
@DaggieBe
Mentor Match goals
Optimise for
the group
Effective
delegation
Mediator
@DaggieBe
Mentor Match goals
Optimise for
the group
Effective
delegation
Mediator
@DaggieBe
Mentor Match goals
Optimise for
the group
Effective
delegation
Mediator
@DaggieBe
Know when to give input
Know when to make decisions
Know when to step back
@DaggieBe
6. Surround yourself with other Tech Leads
Personal Level
@DaggieBe
Objectives

Architecture

Interoperability
Dependencies
Organisational level
@DaggieBe
You are not alone
@DaggieBe
7. Think Big, Bias for Action.
Think big
Create bold direction
Inspire results
Think differently
Focus on opportunities
@DaggieBe
Bias for Action
Many actions are reversible
Extensive study not always needed
Speed matters
Put flywheel in motion
Leadership
8. Interviewing potential new team members
www.websitename.com 44
Know your goal
Prepare
Usefulness of resumes
Don’t focus on tooling
Mindset of a Developer
Eagernes...
Do not use stackoverflow 

to find questions
@DaggieBe
1. Comfort
2. Offer options
3. Build on responses
4. Show interest
5. Bonus question
@DaggieBe
9. Embrace Cultural differences
Embrace Cultural
Differences
Diversity is invaluable
Opinions matter
Shared end goal
Surround yourself
@DaggieBe
Time
Communication
Prepare work
Everybody is part of the
team
Offshore?
@DaggieBe
10. Estimating is hard
Hofstadter’s Law: It always takes
longer than you expect, even when you
take into account Hofstadter’s Law.
Douglas Hofsta...
Quickly repurpose top innovation
before global communities.
Planning poker
Define a sequence
Set a baseline
Allow reasonin...
(O + 4BG + P) ÷ 6
Unknown unknowns
Add 20% for
- test
- debug
- polish
- documentation
- wtf moments
Solutioning
@DaggieBe
Any estimate is better than no estimate
Don’t forget the bigger picture

Share estimates
Review estimates
@DaggieBe
11. Interfacing with the outside world
MIZABusiness Company
Communication with
non-technical people
Go-to-Guy / Go-to-Girl
for management, the customer and other stakeholders
@DaggieBe
No
@DaggieBe
12. Facilitate (agile) team work
Facilitate agile
Backlog
Prioritised backlog
Sprint Planning
Burn down charts
Retrospectives
…
@DaggieBe
Your team’s
strength
is not a function of the talent of
individual members. It’s a function
of their
collaboration, tenaci...
Facilitate an awesome team
@DaggieBe
Thank You
@DaggieBe
JavaDay 2017: 10 tips to become an awesome technical lead (v4)
JavaDay 2017: 10 tips to become an awesome technical lead (v4)
Upcoming SlideShare
Loading in …5
×

JavaDay 2017: 10 tips to become an awesome technical lead (v4)

1,233 views

Published on

Updated slidedeck for JavaDay, currently with 12 tips.

As you grow in your career, chances are that one day you will end up as the Technical Lead of 1 or more projects. Often not by choice. The role of Technical Lead is quite different from the role of (senior) Software Developer and this talk will bring you answers on questions like:

* How do I do technical interviews?
* How do I lead a team? How do I lead multiple teams?
* How do I cope with my new responsibilities?
* How do I cope with success / failure?
* How do I prevent losing focus on the technical challenges?
* …

In summary, everything you want(ed) to know on your first day as a Technical Lead and that you can use every day from that point onwards.

Published in: Leadership & Management
  • Be the first to comment

JavaDay 2017: 10 tips to become an awesome technical lead (v4)

  1. 1. JWORKSPowered By Ordina Everything you want(ed) to know on your first day as a Technical Lead and that you can use every day from this point onwards. 10 tips to become an awesome Technical Lead Bart Blommaerts @DaggieBe
  2. 2. ORDINAJWORKS Bart Blommaerts Application Architect Ordina Belgium @DaggieBe JWorks
  3. 3. Technical Leadership What? @DaggieBe
  4. 4. Technical Leadership What? Technical Guidance @DaggieBe
  5. 5. Technical Leadership What? Risks & RequirementsTechnical Guidance @DaggieBe
  6. 6. Technical Leadership What? CoachingRisks & RequirementsTechnical Guidance @DaggieBe
  7. 7. Technical Leadership What? CommunicationCoachingRisks & RequirementsTechnical Guidance @DaggieBe
  8. 8. Technical Leadership Do we really need one?
  9. 9. Technical Leadership Do we really need one? Everything is awesome !
  10. 10. Technical Leadership Do we really need one? Really well-functioning teams where people share responsibilities
  11. 11. 2 sides to a story Technical responsibilities vs. Leadership activities Technical Leadership 50 % @DaggieBe
  12. 12. Technical
  13. 13. 1. Advocate for Change
  14. 14. ORIENT ACT OBSERVE DECIDE Advocate for Change @DaggieBe
  15. 15. Experience the same pain as everybody else on the team @DaggieBe
  16. 16. JWORKSPowered By Ordina Everything you want(ed) to know on your first day as a Technical Lead and that you can use every day from this point onwards. tips to become an awesome Technical Lead Bart Blommaerts 12
  17. 17. 2. Work through Failure and Success
  18. 18. Things will fail Prepare for failure Don’t finger-point Take responsibility
 Learn from failure @DaggieBe
  19. 19. Celebrate success Sprint celebrations Feature complete Congratulate the team Congratulate individuals
  20. 20. 3. Stay Technical
  21. 21. Stay Technical Write code Review code Technical vision Evolution of code @DaggieBe
  22. 22. Networking
 Security
 Deployment Consistency Stay Technical @DaggieBe
  23. 23. 4. Always Available
  24. 24. Technical Design Business Project Management Code Time Management 35% 25% 15% 25% @DaggieBe
  25. 25. Be realistic @DaggieBe
  26. 26. 5. Be a mentor for your team
  27. 27. Mentor Mediator @DaggieBe
  28. 28. Mentor Mediator @DaggieBe
  29. 29. Mentor Match goals Optimise for the group Effective delegation Mediator @DaggieBe
  30. 30. Mentor Match goals Optimise for the group Effective delegation Mediator @DaggieBe
  31. 31. Mentor Match goals Optimise for the group Effective delegation Mediator @DaggieBe
  32. 32. Know when to give input Know when to make decisions Know when to step back @DaggieBe
  33. 33. 6. Surround yourself with other Tech Leads
  34. 34. Personal Level @DaggieBe
  35. 35. Objectives
 Architecture
 Interoperability Dependencies Organisational level @DaggieBe
  36. 36. You are not alone @DaggieBe
  37. 37. 7. Think Big, Bias for Action.
  38. 38. Think big Create bold direction Inspire results Think differently Focus on opportunities @DaggieBe
  39. 39. Bias for Action Many actions are reversible Extensive study not always needed Speed matters Put flywheel in motion
  40. 40. Leadership
  41. 41. 8. Interviewing potential new team members
  42. 42. www.websitename.com 44 Know your goal Prepare Usefulness of resumes Don’t focus on tooling Mindset of a Developer Eagerness to learn
  43. 43. Do not use stackoverflow 
 to find questions @DaggieBe
  44. 44. 1. Comfort 2. Offer options 3. Build on responses 4. Show interest 5. Bonus question @DaggieBe
  45. 45. 9. Embrace Cultural differences
  46. 46. Embrace Cultural Differences Diversity is invaluable Opinions matter Shared end goal Surround yourself @DaggieBe
  47. 47. Time Communication Prepare work Everybody is part of the team Offshore? @DaggieBe
  48. 48. 10. Estimating is hard
  49. 49. Hofstadter’s Law: It always takes longer than you expect, even when you take into account Hofstadter’s Law. Douglas Hofstadter
  50. 50. Quickly repurpose top innovation before global communities. Planning poker Define a sequence Set a baseline Allow reasoning Uncertainty is normal @DaggieBe
  51. 51. (O + 4BG + P) ÷ 6 Unknown unknowns Add 20% for - test - debug - polish - documentation - wtf moments Solutioning @DaggieBe
  52. 52. Any estimate is better than no estimate Don’t forget the bigger picture
 Share estimates Review estimates @DaggieBe
  53. 53. 11. Interfacing with the outside world
  54. 54. MIZABusiness Company Communication with non-technical people
  55. 55. Go-to-Guy / Go-to-Girl for management, the customer and other stakeholders @DaggieBe
  56. 56. No @DaggieBe
  57. 57. 12. Facilitate (agile) team work
  58. 58. Facilitate agile Backlog Prioritised backlog Sprint Planning Burn down charts Retrospectives … @DaggieBe
  59. 59. Your team’s strength is not a function of the talent of individual members. It’s a function of their collaboration, tenacity, and mutual respect. @DaggieBe
  60. 60. Facilitate an awesome team @DaggieBe
  61. 61. Thank You @DaggieBe

×