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.

Knowledge Capture Process


Published on

Published in: Business, Education
  • Be the first to comment

Knowledge Capture Process

  1. 1. ITMGMT 560 Managing Technology Learning Instructor: Ryan Gun hold August 26, 2012 (by Anahita Zamani)
  2. 2. Agenda  Introduction  Background  Current State & Situation  Desired State  Proposal  Process Map  Collaboration & Communication Tools  Summary  Q & A
  3. 3. Introduction  Knowledge Capture Process  Identify  Create  Represent  Distribute  And enable adoption of insights and experiences. The intent of this presentation is to develop a process for capturing and re-using knowledge within the project team and learning from utside environment.
  4. 4. Background  OC Health system is the solution for Monitoring the health of OC product in online an don-prem world.  OC Health system is using a third party product .  Health is a growing feature and taking more attention from other feature teams.  OC Health team is changing and new resource are adding.  Many on the fly design changes is being introduced to the code.  No knowledge capture process is in place.
  5. 5. Current State & Situation  Design changes are not being captured and documented.  Existing documents and wiki page are not up-to-date.  Links to the documents has changed.  Resources are not addressing external teams questions.  Lessons are not being captured.  Knowledge transfer is a one-to-one process.  There is a lot of hidden knowledge floating around.  Team is lacking knowledge on partner’s products.
  6. 6. Desire State  To have a central repository for information, documents and tools.  To have all the documents and wiki page up-to-date.  To make sure all the links to the documents and resource are available and accessible,  To have needed information for the partners and external team available.  To capture the lesson learned after each project and major release.  To collect the hidden knowledge from the team members.  Team have enough knowledge and resources from outside.
  7. 7. Proposal  Create a semi-formal process to capture and re-use knowledge in the project team environment, by following the process map.  Create a Learning Organization.
  8. 8. Process Map
  9. 9. Collaboration & Communication Tools  Tools to be successful in collaboration with colleagues and externals include:  SharePoint and Websites  Microsoft Lync  Email  Weblogs
  10. 10. Summary  Reviewed the current state of the issues with team’s knowledge capture system and learning process.  Reviewed the desired state.  Reviewed the proposed knowledge transfer “Implicit” and “Explicit” practices.  Reviewed the tools for communication and collaboration.
  11. 11. Q & A
  12. 12. Knowledge Mapping  Identify sources, opportunities and constraints to knowledge creation and flows.  Re-use and prevent re-invention, saving search time and acquisition costs.  Highlight islands of expertise and suggest ways to build bridges to increase knowledge sharing and exchange.  to discover effective and emergent communities of practice where informal learning is happening  to reduce the burden on experts by helping staff to find critical solutions & information quickly  to improve customer response, decision making and problem solving by providing access to applicable information, internal and external experts
  13. 13. Reference  Knowledge Transfer. (June, 2008). Data retrieved August 26, 2012 from websites at iatives/KnowledgeTransfer/  Senge, P., Kleiner, A., & Roberts, C. (1999). The dance of change: The challenges of sustaining momentum in learning organizations. (1st ed.). New York: Doubleday/Currency. (ISBN: 9780385493222)  Weinberger, D. (2007). Everything is miscellaneous: The power of the new digital disorder. (1st ed.). New York: Times Books - Henry Holt & Co.. (ISBN: 9780805080438)