The lust for knowledge and experience

2,440 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
2,440
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The lust for knowledge and experience

  1. 1. THE LUST FOR KNOWLEDGE AND EXPERIENCE MARCEL VAN BRAKEL 28 JAN. 2011
  2. 2. A LITTLE BIT ABOUT MYSELF Development  PHP  Open Source  Content Management  Custom applications Teams,processes, business Dog, movies, gaming, gadgets, musicals ∂ Developer since 2000
  3. 3. WHAT IS THIS TALK ABOUT ?Understanding the stuff that makes knowledge sohard to get and even harder to share, therefore makingexperience the main influential aspect in developmentteam evolution. ∂ NOT about recruitment
  4. 4. WHAT IS HAPPENING ?
  5. 5. WHAT IS HAPPENING? Widely accepted More large scale projects Rising aspiration∂ PHP Developer hunt is on
  6. 6. MORE AND BETTER WORK∂ NO MORE UNDERDOG!
  7. 7. DEMAND IS CHANGING … Apache Linux PHP HTML MySQL∂ … SO IS THE WAY WE WORK
  8. 8. DYNAMIC ENVIRONMENT ActiveMQ PHPUnit Hadoop GearmanMemcached Tika Zend Server SSL Azure Apache Linux nginx PHP Varnish Amazon S3OAuth CouchDB Zend Framework MySQL CakePHP Drupal Symfony MS SQL MongoDB WordPress API’s Solr MariaDBHTML NoSQL Oracle Typo3 Social media
  9. 9. THIS IS A LOT
  10. 10. THIS IS A LOTTEAMWORK !
  11. 11. WHAT IS KNOWLEDGE ANYWAY?
  12. 12. KNOWLEDGE, AS A FUNCTION K = ƒ( I.S.A ) Information , Skill, Attitude
  13. 13. EXPLICIT KNOWLEDGE “This talk is about knowledge”∂ Codified
  14. 14. IMPLICIT KNOWLEDGE “How do airplanes fly?”∂ Can be codified
  15. 15. TACIT KNOWLEDGE “How do you operate a complex machine efficiently”∂ Can NOT be codified
  16. 16. THE DEMAND
  17. 17. COMPANIES ARE LOOKING FOR: High knowledge level (sr.) Broad focused Specialist Several ( 3 – 6 ) years of experience∂ NOT REALLY REALISTIC
  18. 18. DEVELOPMENT TEAMS
  19. 19. GENERAL TEAM COMPOSITIONSenior developer Domain knowledge System architectureMedior developers Production, developmentJunior developers Production, implementation∂ “Knowledge equals Power”
  20. 20. APPLIED KNOWLEDGEHIERARCHY within the teamDECISIONS top – downCOMMANDS no collaborationLEARNING by doing∂ Efficient and effective for production only
  21. 21. THE DANGERSTERRITORIAL behaviorSHARING not implementedJUNIORS steep learning curveNO INSIGHT in knowledge
  22. 22. WHAT DO WE WANT ?More knowledge Explicit and implicitMore experience Preferably > 3 yrsSelf supporting team Sharing knowledge Better synergy
  23. 23. EFFICIËNT KNOWLEDGE SHARING
  24. 24. SHARING OPTIONS Sessions Knowledge base Yellow pages Master - apprentice – pupil
  25. 25. PERSONAL SHARING SESSIONS (1)By SENIORFor ALLTARGETMinimize interpretational differenceProviding information“Improve” attitude∂ Conference, presentation, meeting
  26. 26. PERSONAL SHARING SESSIONS (2)
  27. 27. PERSONAL SHARING SESSIONS (3) Motivate sharing  Certification  CFP’s Variants  Open Podia  Corporate blog  User group initiatives∂ Part of performance review
  28. 28. KNOWLEDGE BASE (1)By ALLFor ALLTARGETProvide data and explicit knowledge∂ Wiki, lotus notes, custom application
  29. 29. KNOWLEDGE BASE (2)∂ Inline documentation !?
  30. 30. KNOWLEDGE BASE (3) Transfer information  Explicit knowledge  Project facts Warnings  Time consuming  Strict formatting∂ Use for archive
  31. 31. YELLOW PAGES (1)By ALLFor ALLTARGETInsight in knowledge and skill locationsInsight in low density area’s∂ Wiki, intranet, custom
  32. 32. YELLOW PAGES (2)
  33. 33. YELLOW PAGES (3) Who knows what? What are we missing when someone is unavailable? Where can I go to? Who can teach me?
  34. 34. MASTER – APPRENTICE – PUPIL (1)By SENIOR / MEDIORFor MEDIOR / JUNIORTARGETActively engaging in teachingEasier tacit knowledge transferStructural team member growth
  35. 35. MASTER – APPRENTICE – PUPIL (2)∂ Teaching I will …
  36. 36. MASTER – APPRENTICE – PUPIL (3)1. Teach the teacher2. Master “teaches” pupil3. Pupil becomes apprentice4. Apprentice supports new pupils5. Apprentice becomes master∂ … share it you must
  37. 37. KNOWLEDGE MANAGEMENT IMPLEMENTATION / TOOLS
  38. 38. WHERE TO START Assign a coordinator Create team awareness Gather budget Analyze your needs Implement in phases
  39. 39. JUNIORS TAKE THE LEAD Absent knowledge Important topics Seeing the gap
  40. 40. PHASE 1SKILL MATRIXKNOWLEDGE MATRIX∂ YELLOW PAPERS ?
  41. 41. PHASE 2TACIT KNOWLEDGE SHARINGSessions, blogging, open podia∂ MOTIVATE !!
  42. 42. PHASE 2MASTER – APPRENTICE – PUPILPersonal attention∂ Self organized
  43. 43. PHASE 3, 4 , *KNOWLEDGE BASEDocumenting information
  44. 44. RECAP Self supporting teams Awareness Willingness Tools∂ Knowledge no longer equals power !!
  45. 45. THANKS !joind.in/4775 || www.slideshare.net/mvbrakel || @mvbrakel

×