O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Winning technical strategy for your teams and products

513 visualizações

Publicada em

A few tips for CTOs, Technical Directors, Technical Leads and Architects on how to define and execute a winning strategy for their teams and products.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

Winning technical strategy for your teams and products

  1. 1. Winning A talk by Alexandru Bolboaca @alexboly alex.bolboaca@mozaicworks.com Technical Strategy
  2. 2. I was once named architect... but what was I supposed to do? Technical Lead? CTO?
  3. 3. Purpose of the Talk ● Useful technical leadership practices ● A bit about how to learn them ● A bit about how to apply them
  4. 4. As a technical lead... You are responsible for keeping, protecting and growing your teams
  5. 5. Technical Leadership Practices 1. Align with Business 2.Assess the situation 3. Build a roadmap 4. Encourage learning 5. Set boundaries 6. Execute the roadmap 7. Create opportunities + Influence Company Culture
  6. 6. I'm guilty for this talk! Alexandru Bolboacă Trainer, coach, polyglot programmer with international experience alex.bolboaca@mozaicworks.com @alexboly
  7. 7. 1. Align with Business ● What does the business want the most in the next 6 months? – Improved customer happiness? – Improved productivity? – Expand to new lines of business? ● How can the technical practices help these objectives?
  8. 8. 2. Assess the Situation ● '121' chats with everyone involved ● Code, design, architecture review ● Key Metrics eg. cyclomatic complexity,– no. of bugs, files with most changes ● Documentation review ● Process review => weak and strong points
  9. 9. 3. Build a Roadmap Vision: Improve customer happiness Objective: Customers to like the release 9/10 times Goals 0 blocking / major bugs per release Underpromise, overdeliver 0 misunderstandings on features Nice visual, interaction design Practices Demo 2 x week Code review Unit test critical areas ATDD or BDD Continuous improvement Visual Management First demo the design Top-down dev. How we'll learn Coaching / Mentoring Workshop + coaching Doing Book + Practice Book + Practice Doing Better code design Workshop + coaching
  10. 10. 4. Encourage learning ● Low investment + low speed: – Internal Communities of Practice – Encourage community participation – Book clubs ● Average investment + average speed: – Attend conferences – Workshops (see roadmap) ● High investment + high speed: – Coaching – Mentorship
  11. 11. 5. Set Boundaries Because of business need X we need to do / never do practice Y Eg: because we need to demo flawlessly twice a week, we need high coverage for automated tests and we don't estimate (unless explicitly requested)
  12. 12. 6. Execute the Roadmap ● Change is part of the roadmap ● Remember about change: – Repeat the goals over and over again – Explain, explain and explain again why they're important – Start with the most likely team(s) to succeed – Market successes, learn from failures – Get outside help
  13. 13. 7. Create Opportunities ● Each developer should have a growth objective ● Have '121's every two weeks to review status and define next actions
  14. 14. Company Culture is Crucial! ● Culture = what you do every day ● Eg, Mozaic Works: – Trust, transparency, communication, autonomy, results-orientation ● Eg, Spotify: – High autonomy, high alignment, responsibility – http://labs.spotify.com/2014/03/27/spotify-engin eering-culture-part-1/ for details
  15. 15. You Influence Company Culture! ● What kind of personalities do you want in the team? – collaborative OR combative – help grow others OR eliminate them ● What are the team values? – eg. trust, transparency, communication, autonomy, results
  16. 16. Technical Leadership Practices 1. Align with Business 2.Assess the situation 3. Build a roadmap 4. Encourage learning 5. Set boundaries 6. Execute the roadmap 7. Create opportunities + Influence Company Culture
  17. 17. Your Questions? “The important thing is not to stop questioning”
  18. 18. I'm guilty for this talk! Alexandru Bolboaca alex.bolboaca@mozaicworks.com @alexboly http://alexbolboaca.ro
  19. 19. Learn More http://itakeunconf.com/ Bucharest, 29-30 May 2014 Assessments We provide assessments for technical and organizational purposes I T.A.K.E. Unconference Blog mozaicworks.com/category/blog 11 Workshops SOLID Principles Design Patterns Unit Testing TDD etc. Agile Works Community where we talk about various development practices
  20. 20. Photo Attribution http://life.halcode.com/archives/2008/04/13/the-7-attributes-of-leadership/ http://3.bp.blogspot.com/-Cqdg1WeNuA8/TjZ8iloJEpI/AAAAAAAAAGY/bGX693pKEPU/s1600/super_architect.jpe g http://commons.wikimedia.org/wiki/File:US_Navy_110312-N-OA833-005_The_U.S._Naval_Academy_womens_bas ketball_team_hoists_the_Patriot_League_Tournament_championship_trophy_after_winning_the.jpg