Knowledge Creation - Lightning Talk
•Télécharger en tant que KEY, PDF•
4 j'aime•1,030 vues
12 min lightning talk version of my talk on knowledge creation as the key to effective software development.
Recommandé
Recommandé
Contenu connexe
Similaire à Knowledge Creation - Lightning Talk
Similaire à Knowledge Creation - Lightning Talk (20)
Dernier
Dernier (20)
Knowledge Creation - Lightning Talk
- 1. Knowledge Creation The key to effective software development Chris Hedgate @chrishedgate chris@hedgate.net http://www.hedgate.net/
- 2. Q: What if I train staff and they leave? A: What if you don’t, and they stay? Twitter (attribution unknown)
- 3. Write code
- 4. “Fake” example Google it Copy-paste Try yourself similar Ask an expert What code? Get time Write code from expert... New technology?
- 5. Policies? Avoid performance issues “Fake” example Follow policies Write Google it “correct code” Copy-paste Try yourself similar Which solution? Ask an expert What code? Get time Write code from expert... New technology?
- 6. Ask the architect Read docs Policies? Understand design Avoid performance issues “Fake” example Follow policies Find the right place Understand existing code Write Google it “correct code” Where in code base? Copy-paste Try yourself similar Which solution? Ask an expert What code? Get time Write code from expert... New technology?
- 7. Ask the architect Read docs Policies? Understand design Avoid performance issues “Fake” example Follow policies Find the right place Understand Am I allowed? existing code Write Do I have Google it “correct code” necessary rights? Where in code base? Modify Copy-paste Try yourself existing code similar Which solution? Ask an expert What code? Get time Write code from expert... New technology?
- 8. Ask the architect Read docs Policies? Understand design Avoid performance issues “Fake” example Follow policies Find the right place Understand Am I allowed? existing code Write Do I have Google it “correct code” necessary rights? Where in code base? Modify Copy-paste Try yourself existing code Talk to similar Which solution? customer Which customer? Ask an expert What code? Which problem? Get time Write code Specs? from expert... New Understand specs technology?
- 9. Integrate?!?
- 10. | Learning is the #1 constraint in software development
- 11. | Most efforts focus on sharing explicit knowledge Photo from margolove’s Flickr stream http://www.flickr.com/photos/margolove/1252522330/
- 12. | Knowledge-as-objects is a codifying perspective
- 13. | Knowledge-as-relations is a personalizing perspective
- 14. | Effective knowledge creation requires people and
- 15. | Effective knowledge creation requires people and A Value of sender’s knowledge base
- 16. | Effective knowledge creation requires people and Motivation of sender to share A B Value of sender’s knowledge base
- 17. | Effective knowledge creation requires people and Motivation of sender to share A B C Value of sender’s Availability of knowledge base transmission channels
- 18. | Effective knowledge creation requires people and Motivation of Motivation of sender to share receiver to receive A B C D Value of sender’s Availability of knowledge base transmission channels
- 19. | Effective knowledge creation requires people and Motivation of Motivation of sender to share receiver to receive A B C D E Value of sender’s Availability of Absorbation capacity knowledge base transmission channels at receiver
- 20. V (D) = LIS(D)
- 21. | Value people, roles and activities that builds knowledge
- 22. | Create an environment for knowledge creation
- 23. The SECI model of knowledge creation
- 24. Socialization I I
- 25. Socialization Externalization I I I I I G I I I
- 26. Socialization Externalization I I I I I G I I I Combination G G O G G
- 27. Socialization Externalization I I I I I G I I I Internalization Combination G O G G O G I G
- 28. | The ba - a physical, virtual and cultural place
- 29. Socialization Conversation Pairing Morning meetings Water cooler Sit together Music
- 30. Codification Retrospectives Externalization Code reviews Whiteboards Information radiators Documentation Presentations Brownbag lunches Code labs
- 31. Reuse Scrum-of-scrums Wikis Coding guidelines Planning meetings Demos and reviews Patterns Combination
- 32. Learning Mentorship Pairing Information radiators Study groups Internalization
- 33. | Make knowledge creation your main focus
Notes de l'éditeur
- \n
- \n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- How can anybody claim that building software is about writing code?\n
- (Shared) knowledge prevents bugs, removes bottlenecks, improves effectiveness\n
- Budgets only focus on sharing explicit knowledge. We forget the continuous sharing of tacit knowledge.\n
- We value databases of information. Make it searchable, findable, attainable. Have policies about codifying knowledge, and sharing it.\n
- Work with the people, as bearers of knowledge. Focus on personal relations, networks and meeting places for tacit knowledge to manifest.\nBoth perspectives are important, but it is easy to focus only on codifying knowledge with movement of employees etc. This is a fallacy though, lots of knowledge does not lend itself to codifying.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- Masters essay in informatics, Maria Håkansson and Frida Wedefelt, Göteborgs Universitet, 2003\nA: Easy, competence efforts.\nB: Medium, though most people like to share. Work continuously.\nC: Easy, focused efforts.\nD: Very difficult. People must want to learn. Cultural. Work continuously.\nE: Easy if you want it. Give space & time.\n
- \n
- \n
- You cannot control knowledge creation, especially the tacit knowledge. Incentives only hurt. Create an environment where knowledge creation can thrive, and it will.\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- The Japanese word ba, meaning “place”, is used when talking about the environment work happens in. It has physical, virtual and cultural aspects. Work on all!\n
- \n
- \n
- \n
- \n
- \n