Knowledge Mapping: An Overview Prof Elaine Ferneley

Slides:



Advertisements
Similar presentations
Stimulating Knowledge Creation Dr. Elaine Ferneley.
Advertisements

Knowledge Mapping: An Overview Prof Elaine Ferneley.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 15 Creating Collaborative Partnerships.
Knowledge Mapping KMForum lpc. 1 What is “knowledge mapping?” An ongoing joint quest to help discover the constraints, assumptions, location, ownership,
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
1 Knowledge Management. 2  Knowledge management (KM) is a process that helps organizations identify, select, organize, disseminate, and transfer important.
Creating Collaborative Partnerships
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Forethought Knowledge is our most important engine of production – Alfred Marshal Knowledge is the key resource of the 21st century Problem today is.
KNOWLEDGE MANAGEMENT TEAM. KM Skills in General 1. Time management → to acquire knowledge 2. Learning technique → to absorb knowledge 3. Networking skill.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Human Resource Management Lecture 27 MGT 350. Last Lecture What is change. why do we require change. You have to be comfortable with the change before.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements Engineering Requirements Elicitation Process Lecture-8.
BYST 1 Knowledge Management (KM): Experience in implementing KM at KMUTT Asst. Prof. Bundit Thipakorn Asst. Prof. Bundit Thipakorn Computer Engineering.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
C11- Managing Knowledge.
Knowledge Management …basic principles and practices.
Knowledge Mapping: An Overview Prof Elaine Ferneley.
Software Prototyping Rapid software development to validate requirements.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Knowledge Management in Theory and Practice
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 15 Creating Collaborative Partnerships.
Knowledge management By Dhanalakshmi. Contents  Knowledge & knowledge management  Knowledge creation process  Knowledge management system  Knowledge.
KNOWLEDGE MANAGEMENT (KM) Session # 15. Knowledge management is a method to simplify and improve the processes of creating, capturing, sharing, distributing,
1 2. Knowledge Management. 2  Structuring of knowledge enables effective and efficient problem solving dynamic learning strategic planning decision making.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini XVII. Verification and Validation.
This session commences the second part of the content.
Data Collection Techniques
Module 1: Overview of Information System in Organizations
Pepper modifying Sommerville's Book slides
Creating Collaborative Partnerships
Generating data with enacted methods
Requirements Engineering Processes
Prototyping in the software process
Software Prototyping.
Introduction to Employee Training and Development Chapter 1
Requirements Engineering Process
Content Management.
Knowledge Management in Theory and Practice
Building the foundations for innovation
Organization and Knowledge Management
Systems Analysis and Design
By Sikiru Abiodun Ganiyu
SNS College of Engineering Coimbatore
EKT 421 SOFTWARE ENGINEERING
ASSESSMENT OF STUDENT LEARNING
Program comprehension during Software maintenance and evolution Armeliese von Mayrhauser , A. Marie Vans Colorado State University Summary By- Fardina.
Chapter 1 The Systems Development Environment
Assist. Prof. Magy Mohamed Kandil
Taxonomies, Lexicons and Organizing Knowledge
Informatics 121 Software Design I
Informatics 121 Software Design I
Design Research Jon Kolko Director & Founder, Austin Center for Design.
Managing Organizational Knowledge
Chapter 6 Discuss the types of strategic research
Requirements Engineering Processes
User interface design.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
KNOWLEDGE MANAGEMENT (KM) Session # 40
Knowledge Management Trevor T Yardley General Manager
KNOWLEDGE MANAGEMENT (KM) Session # 37
COMP444 Human Computer Interaction Usability Engineering
Introduction to Employee Training and Development Chapter 1
Rapid software development
Presentation transcript:

Knowledge Mapping: An Overview Prof Elaine Ferneley

Revisiting the Definition of Knowledge Management (Skyrme’s) Don’t leave it to serendipity Surface assumptions, Codify what is known Knowledge Management is the explicit and Systematic management of vital knowledge - and its associated processes of creation, organisation, use & exploitation Focus, resources are limited KM has its own tools & techniques Prof Elaine Ferneley

Seven Strategic Levers [Skyrme, 2002] Customer Knowledge - the most vital knowledge in most organizations Knowledge in Processes - applying the best know-how while performing core tasks Knowledge in Products (and Services) - smarter solutions, customized to users' needs Knowledge in People - nurturing and harnessing brainpower, your most precious asset Organizational Memory - drawing on lessons from the past or elsewhere in the organization Knowledge in Relationships - deep personal knowledge that underpins successful collaboration Knowledge Assets - measuring and managing your intellectual capital. Prof Elaine Ferneley

Practices & Processes Our focus today Creating & Discovering creativity techniques data & text mining knowledge elicitation business simulation, content analysis Sharing & Learning communities of practice, learning networks share fairs, share best practice cross functional teams, action reviews Organizing & Managing knowledge centres, knowledge audits expertise profiling, knowledge mapping measurement of intellectual capital Prof Elaine Ferneley

What is Knowledge Mapping Ongoing quest in an organisation (includes supply & customer chain): Discover knowledge location and ownership; Identify value and use of knowledge artefacts; Learn roles & expertise of individuals; Identify constraints in flow of knowledge; Highlight opportunities to leverage existing knowledge. Knowledge mapping activities: Survey, audit and synthesis; Identify where knowledge is being acquired and lost; Personal and group competencies and proficiencies; Identify how knowledge flows through an organisation. Knowledge mapping helps organisations: Appreciate how loss of staff influences Intellectual Capital; Select teams Match technology to knowledge needs. Prof Elaine Ferneley

Key Principles of Knowledge Mapping Understand that knowledge is transient; Explain boundaries & respect personal disclosures; Recognise knowledge comes in a variety of forms: Tacit ‘v’ explicit; Codified ‘v’ personal; Short ‘v’ long lifecycle. Locate knowledge in processes, people, relationships, documents; suppliers, customers etc. Be aware of organisational hierarchies, cultural issues, reward mechanisms, sharing & value, legal processes & protections (patents, NDAs, MoUs etc.) Prof Elaine Ferneley

What is a Knowledge Map & Why Use One ? Navigation aid to explicit and tacit knowledge; Portrays sources, flows, constraints and sinks of knowledge within an organisation; Encourages re-use and prevents re-invention, saves search time; Highlights expertise, discover communities of practice, helps staff to find critical resources; Improves decision making, problem solving and customer response time by providing access to information; Provides an inventory of intellectual and intangible assets; The start of a corporate memory or collective mind. Prof Elaine Ferneley

How & Where Should I be Looking How & Where Should I be Looking? Active Knowledge Elicitation Techniques Formal and informal interviews: Interviewer asks the expert or end user questions relating to the specific topic Adv: well known, comfortable for interviewees DisAdv: time consuming, expensive, interviewer expertise required, interviewee cooperation required Verbal Protocol Analysis: Experts report thought processes involved in performing a task or solving a problem Adv: rigorous DisAdv: time consuming, hard to analyse Group Task Analysis: A group of experts describes and discusses processes pertaining to a specific topic Adv: multiple viewpoints, concensus building DisAdv: how to validate Narratives, Scenarios, Storytelling Expert or end user constructs stories to account for a set of observations Adv: rich insight, good for ill defined problems DisAdv: reliance on self reports Questionnaires: Users respond to specific questions Adv: usually quantitative, easy to code DisAdv: low return rate, responses are difficult to validate Prof Elaine Ferneley

How & Where Should I be Looking How & Where Should I be Looking? Active Knowledge Elicitation Techniques Focus Groups A group discusses different issues Adv: allows exchange of ideas, good for generating complete lists DisAdv: an individual may dominate, not good for discovering specific problems Wants & Needs Analysis: Users brainstorm about what they want/need from a system Adv: exchange of ideas, determines areas for focus, allows prioritisation DisAdv: wants and needs may not be realistic Observation: Observe users in their natural environment Adv: see it as it really is (but not ethnography) DisAdv: time, depends on observer note taking & observation skills Ethnographic Study: Users culture and work environment are studied via emersion Adv: see it as it really is over a long time period DisAdv: time consuming, hard to distance yourself from the domain User Diary Users record and evaluate their actions Adv: real time (almost) tracking DisAdv: invasive, possible delay in recording Concept Sorting Users determine relationships between concepts Adv: helps structure information DisAdv: grouping is user specified, structure may be too elaborate Prof Elaine Ferneley

How & Where Should I be Looking How & Where Should I be Looking? Passive Knowledge Elicitation Techniques News feeds: Discussion groups; Company magazines; Bulletins. Contact addresses Organisation charts; Home pages. Network transactions: Email tags; Semantic analysis. Helpdesks and CRM systems: Interaction logs; Process scripts. Asset and HR databases (company CVs); LAN directory structures: Who has access to what; Why do they have access. Library & record archives Process descriptions: QA documents; Procedure manuals. Meta-data directories: Standardisation documents; Meta-tags on electronic data sources. Prof Elaine Ferneley

What do I do with the information? Compile: Yellow pages/register of interests; Best practice/lessons learnt databases; Prototype ontology/taxonomy Identify: Knowledge stewards/gatekeepers; Isolated islands, narrow communication channels; Critical sequences/dependencies. Explore reuse opportunities: Attempting to create a knowledge network of people, processes and data. Prof Elaine Ferneley

We Will Now Look at Some Specific Examples Spreadsheets – great and simple to use, disseminate and for all to understand Cause and effect models The example we will use is from ISEEE Prof Elaine Ferneley

Explicit model of who has what knowledge Simple Spreadsheets Explicit model of who has what knowledge Value of various knowledge items can be weighted Allows transparency Encourages people to state their knowledge and expertise Cheap and one of the most effective tools I’ve seen, everyone understands a spreadsheet Prof Elaine Ferneley

SBS Staff Expertise – figures are fictional! Prof Elaine Ferneley

Useful as brainstorming tools Auditing Tools Tools that allow you to classify expertise, apply some sort of rating or ranking to knowledge domains; Useful as brainstorming tools Strongly encourage you to download Assistum: http://www.assistum.com/2002/products/examples/java/project.htm Prof Elaine Ferneley

Assistum Knowledge Editor - http://www. assistum Prof Elaine Ferneley

STELLA http://www. iseesystems Prof Elaine Ferneley

Examples Prof Elaine Ferneley

Examples Prof Elaine Ferneley

Mind Mapping – For Brainstorming, Knowledge Elicitation and Knowledge Mapping Mind Mapping is a technique developed by Tony Buzan to help individuals organise, generate and learn ideas and information Pictorial representation – detail and overview together Consider spatial relationships and anticipate consequences Supported by visual processing – improved recall, aids understanding Explicit representation acts as a creativity trigger Prof Elaine Ferneley

Hand Drawn Mind Map Prof Elaine Ferneley

MindJet Mindmap Prof Elaine Ferneley

Why Mind Map Software – the Pro’s and Con’s Supports continuous refinement Allows variable granularity Brings formality (validity?) to the process Integration with other tools Cross ref & re-assembly of elements of the knowledge base possible Slow Horde mentality (difficult to throw away early versions) Semantics – in large implementations is the same vocabulary being used Common understanding Maintenance – especially due to the transitory nature of the output Prof Elaine Ferneley

Consider further mechanisms to encourage: The Next Step Consider further mechanisms to encourage: Relinquishing of knowledge; Creation of new knowledge; Brainstorming tools; Capturing of the brainstorming activity. Representing knowledge in a highly structured database does not encourage this …. Prof Elaine Ferneley