Build a great Technical Team

1,638 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,638
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Build a great Technical Team

  1. 1. Build A Great Technical Team V1.0, Because I Embrace Change Alexandru Bolboaca
  2. 2. How relevant are technical practices? How to learn them quickly? Questions I'm trying to answer
  3. 3. What to avoid? How to sell it? Questions I'm trying to answer
  4. 4. Personal Story
  5. 5. XP'ers Great care shown to code Still working on code Common Things
  6. 6. Deploy every 2 days Vs Commit every 2 days A Tale of Two Teams
  7. 7. Agile? Lean? Building Products! Mindset
  8. 8. #1 Software is Precise Encoded Knowledge My Principles
  9. 9. #2 Know WHERE you're going if you want to get there My Principles
  10. 10. #3 High Quality, Fast Feedback Ensures Quality and Reduces Risks My Principles
  11. 11. #4 Continuously improve Through Experiments My Principles
  12. 12. People Values Practices Environment Tools Axes
  13. 13. People Knowledge building Values Common vision Practices That Facilitate High quality feedback Environment Continuous improvement Tools Choose A New Manifesto?
  14. 14. In Code We Trust Consequence #1
  15. 15. Not Only Working Code But also (at least) Clear Consequence #2
  16. 16. Automated tests encode knowledge about the system Consequence #3
  17. 17. Knowledge can be expressed as simple or complex as we want. Consequence #4
  18. 18. Build a Great Technical Team How To...
  19. 20. Bad when you notice it Enables creativity Information Radiators Environment
  20. 21. Source Control IDE Continuous Integration Continuous Testing Tools
  21. 22. Practices
  22. 23. Realize Pain Act People
  23. 24. Collective Mind Build Knowledge?
  24. 25. 1. Pick people 2. Teach them 3. Tools from day 1 Start a Team DOs
  25. 26. 4. Involve team 5. Support them 6. Push if they settle Start a Team DOs
  26. 27. 7. Grow organic 8. Add organizational practices as required 9. Trust your team Start a Team DOs
  27. 28. DON'T start a large app DON'T settle DON'T stop experiments DON'T micromanage Start a Team DONTs
  28. 29. Shorten feedback cycles Improve your Team
  29. 30. <ul><li>“ Learning is the bottleneck”
  30. 31. Amr Elssamadisy
  31. 32. Agile Adoption Patterns </li></ul>
  32. 33. Invest Communities of Practice Outside help Measure the right things Adopt Technical Practices
  33. 34. <ul><li>Set a learning objective
  34. 35. Work on a problem
  35. 36. If you fail to do it properly, redo
  36. 37. Make a retrospective </li></ul>Deliberate Practice (for devs)
  37. 38. How relevant are technical practices? Feedback How to learn them quickly? Practice Questions I'm trying to answer
  38. 39. What to avoid? Breaking Principles How to sell it? Experiments Questions I'm trying to answer
  39. 40. Thank You! @alexboly alexboly@gmail.com alexbolboaca.ro tungle.me/alexandrubolboaca The important thing is not to stop questioning

×