B Com Exam > B Com Videos > Contemporary Management > Knowledge Management Tools & Concepts, Contemporary Management
Knowledge Management Tools & Concepts, Contemporary Management Video Lecture | Contemporary Management - B Com
|
52 videos|42 docs|12 tests
|
FAQs on Knowledge Management Tools & Concepts, Contemporary Management Video Lecture - Contemporary Management - B Com
| 1. What are some popular knowledge management tools used in contemporary management? |  |
Ans. Some popular knowledge management tools used in contemporary management include:
- Content management systems (CMS): These tools help in organizing and managing digital content such as documents, files, and media.
- Collaboration platforms: These tools facilitate the sharing and collaboration of knowledge among team members, such as project management software or communication tools.
- Data analytics tools: These tools help in analyzing and interpreting data to extract valuable insights and knowledge.
- Knowledge bases: These tools provide a centralized repository of information and knowledge that can be easily accessed and shared within an organization.
- Learning management systems (LMS): These tools enable the creation, delivery, and tracking of training and learning materials for employees.
| 2. What is the concept of knowledge management in contemporary management? | |
Ans. Knowledge management is the process of capturing, organizing, and utilizing an organization's knowledge assets to enhance productivity, innovation, and decision-making. It involves identifying, creating, and sharing knowledge within an organization to facilitate learning and improve performance. The concept of knowledge management recognizes that knowledge is a valuable resource that needs to be effectively managed to gain a competitive advantage. It encompasses various strategies, tools, and techniques to capture, store, retrieve, and disseminate knowledge to the right people at the right time.
| 3. How can knowledge management tools benefit organizations in contemporary management? | |
Ans. Knowledge management tools can benefit organizations in contemporary management in several ways:
- Improved decision-making: Knowledge management tools provide access to relevant and up-to-date information, enabling managers to make informed decisions based on accurate data and insights.
- Enhanced collaboration and innovation: These tools facilitate knowledge sharing and collaboration among employees, leading to increased innovation and creativity within the organization.
- Increased efficiency and productivity: By providing a centralized repository of knowledge and information, these tools help employees find the information they need quickly, reducing time wastage and improving overall productivity.
- Retention of organizational knowledge: Knowledge management tools help capture and preserve valuable knowledge within the organization, preventing the loss of critical information when employees leave or retire.
- Continuous learning and development: These tools support the creation and delivery of training materials, enabling employees to acquire new knowledge and skills, fostering continuous learning and development.
| 4. How can organizations effectively implement knowledge management tools? | |
Ans. To effectively implement knowledge management tools, organizations can follow these steps:
- Identify organizational goals and objectives: Understand the specific knowledge needs and objectives of the organization and align them with the selection and implementation of appropriate knowledge management tools.
- Assess existing knowledge and information assets: Identify and evaluate the existing knowledge and information resources within the organization, determining what needs to be captured, organized, and shared.
- Select appropriate knowledge management tools: Choose tools that align with the organization's goals and requirements. Consider factors such as ease of use, scalability, integration capabilities, and user adoption.
- Create a knowledge management strategy: Develop a comprehensive plan that outlines the approach, processes, and responsibilities for managing knowledge within the organization. Define roles and responsibilities for knowledge management activities.
- Train employees: Provide training and support to employees on how to effectively use the knowledge management tools. Encourage a culture of knowledge sharing and collaboration.
- Monitor and evaluate: Continuously monitor and evaluate the effectiveness of the knowledge management tools and processes. Make necessary adjustments and improvements based on feedback and performance metrics.
| 5. Are there any challenges or risks associated with implementing knowledge management tools in contemporary management? | |
Ans. Yes, there can be challenges and risks associated with implementing knowledge management tools in contemporary management. Some of these include:
- Resistance to change: Employees may resist adopting new tools and processes, especially if they perceive them as an additional burden or disruption to their existing work routines. Proper change management and communication are essential to address this challenge.
- Lack of user adoption: If employees do not see the value or benefits of the knowledge management tools, they may not actively use them, leading to limited knowledge sharing and collaboration. User training, clear communication, and showcasing the benefits of the tools are crucial to drive adoption.
- Information overload: If knowledge management tools are not properly organized and structured, they can result in information overload, making it difficult for employees to find relevant and useful information. Effective categorization, search functionalities, and information architecture are important to mitigate this risk.
- Security and privacy concerns: Knowledge management tools involve storing and sharing sensitive information. Organizations need to ensure proper security measures are in place to protect against data breaches and unauthorized access. Compliance with privacy regulations is also crucial.
- Technology limitations: The effectiveness of knowledge management tools can be limited by the capabilities and limitations of the technology itself. It is important to choose tools that are scalable, user-friendly, and capable of integrating with existing systems. Regular updates and maintenance are also necessary to address any technical issues.
Text Transcript from Video
hey my name is David Wiggins and my
presentation is survey of knowledge
management tools and concepts that will
help facilitate the transfer of small
projects between teams I want to start
off with a couple of of the base
concepts of knowledge management
basically if you're on a team where
you're just starting the project or
you're working on and you want to
document all of your information you're
doing a push strategy a push strategy is
where you're actively managing and not
the knowledge pushing it into a
repository so that it can be easily
searched and managed in the future by
future teams clients repositories
what-have-you that the opposite of that
is a pull strategy it's kind of that
that you're doing an ad hoc knowledge
seeking say you just joined a team and
you don't know anything about the
project or the domain you're going to be
looking in existing documentation maybe
that may or may not be part of the
team's documentation maybe you're just
looking online or going to the experts
asking questions this is a pull strategy
and I'll be referring to these terms
throughout the presentation this is an
eye chart and it's meant to be an eye
chart this is copy and paste off of
which PDA just the knowledge management
section the reason I throw this in here
is to explain that knowledge management
is actually a whole area of study and
there are a whole bunch of strategies a
whole bunch of tools a whole bunch of
little sub areas of study in this under
under the subject and today I'm just
going to give a brief overview of a
couple of things but there's a ton that
can be read about this topics if you so
desire so how does a CS 577 do it right
now we've got a repository being our
team website we have a standardized
format for Docs being the what that ms
word templates that we use or graded on
these so we're incentivized to actually
do a good job on the documentation and
then furthermore we've got review boards
with our stakeholders and our teammates
in order to make sure that they're good
quality
and also to make sure that there's no
holes why have I been thinking about
this personally I started up a prototype
project at work a couple of months ago
and an interesting thing happened there
we're working on the prototype and it
and it was a limited scope but at one
point management came back and said
we're gonna have a lull where
everybody's going to leave and go work
on other efforts and then probably we're
going to come back and do this for real
like on contract and large scale and so
we need to be able to take all that
we've learned during the prototype and
document it and be able to eat it maybe
it'll be yourselves coming back or other
team other people other developers but
we need to make sure that we don't let
all this knowledge go to waste
so we started thinking about it then
then started on 577 a and I was on Team
seven we were working on a project that
was meant to go for two semesters it
didn't because everybody else went got
internships over a summer but we spent a
lot of time thinking about how can we
push our information into these
documents in 577 B I guess ed my old
team didn't continue but I got put on
another team and and all of a sudden I'm
on this team of seven people and most of
us have weren't on this team before so
we're all kind of a lot of us are on the
dark starting from scratch don't know
what we're doing don't understand the
client don't understand the vision of
the project and we spend a lot of time
doing a lot of pulling of information
talking to the clients talking to the
people that were on the project
previously so at work when I started on
this project I figured well I'll just
send out an email and find out what my
co-workers know about it and I got some
great responses so this is a quote that
I got out of one of the emails that came
back to me that I thought was great he
says I think the key to transferring a
project from one team to another is
documentation requirements design
decisions and rationale designed adopt
documents meeting notes commented code
etc as much as processes of pain that's
one of the reasons we have it and he's
one of our senior developers on
to come around right now but immediately
after I got that email from across the
hall a buddy of mine says no you're not
supposed to document your so you can't
share all your information with other
people you got to be indispensable its
job security look out for yourself if
you're the only one that knows how to do
something on a project and they can't
get rid of you so immediately we have
this classroom with management we have
our customer saying we want this project
to continue but at the same time people
want to keep their jobs so you got to
manage your culture another concept is
whether or not or how do you make
incentivize or make it mandatory or
whatever you do you've got to get people
to put their information into your
system or strategy or however you've
decided to manage your knowledge I
personally like the reward system and
one great example that I found back over
flow comm that they have rankings and
sort of achievements and the idea is
that the more you put into the system
the higher rank and you get and then as
public and so you have bragging rights
is there any monetary reward no are they
paying more no all they did is just give
you something that said you know as a
gold star but it makes people feel good
and incentivizes them to do more to put
more information into the system here
real quick things to document is just a
few suggestions it will vary from
project project by requirements designs
decisions meeting notes commented code
mock-ups think about anything that you
would need if you are coming back
completely from scratch and joining the
project what would that person need in
order to pick up and start working so I
want to go through a couple of tools
that you might use and this is not
certainly not a comprehensive list but
the idea is that here's a few examples
that you can start with you can compare
these with other tools that you've used
or might consider using and also
consider kind of the level of how much
you want to invest into this tool this
first one is Atlassian they have a whole
suite of tools for collaboration project
tracking bug tracking the whole deal but
it's not free you do get technical
support and it's got a ton of
functionality but
want to go to that level there Atlassian
calm another option might be to have a
wiki somewhere wikispaces calm is a
product that my team this semester has
been using it's nice to get rich content
unity it's a wiki so you can put up your
documents and information all in one
place just a simple repository but it's
also free lastly and these are two two
products that I've used to take
screencasts of my code or processes
things that I've done at work camstudio
is an open source product that's what
I'm using right now it's free it's easy
fairly easy to use easy to learn doesn't
give you a lot of editing capability on
the Left I've got Camtasia Studio which
is the COTS off-the-shelf product it's
got all the effects and cool features
that you'd ever want you get your tech
support etc the drawbacks to doing this
I already talked about some of the good
things that come from it but the
drawbacks are that it takes time to do
these videos memory usage because video
is large and also requires a webcam or a
mic so you've got to equip everybody
that's doing these videos with that
hardware here are my references in
closing I just want to say that most of
these references are just to the
products but if you look at these
products and and then look at other
products that you find through googling
or just searching or asking around and
you can look and see there are pros and
cons to each of these and some of these
products might suit you prop your
project better than others be it's your
budget that's limiting you or maybe the
learning curve also consider the
concepts that I've gone over push and
pull strategies incentivizing and and
getting people to buy off on your
strategy is really important otherwise
you can put all this time and effort
into learning or implementing a
repository for your information but it
will never get used so that said I want
to leave you with the disclosing
statement that the knowledge management
is really important
and sometimes simply just you know a
word doc just doesn't cover it you got
there's a lot of things that can that
you can do to do better thank you for
your time
presentation is survey of knowledge
management tools and concepts that will
help facilitate the transfer of small
projects between teams I want to start
off with a couple of of the base
concepts of knowledge management
basically if you're on a team where
you're just starting the project or
you're working on and you want to
document all of your information you're
doing a push strategy a push strategy is
where you're actively managing and not
the knowledge pushing it into a
repository so that it can be easily
searched and managed in the future by
future teams clients repositories
what-have-you that the opposite of that
is a pull strategy it's kind of that
that you're doing an ad hoc knowledge
seeking say you just joined a team and
you don't know anything about the
project or the domain you're going to be
looking in existing documentation maybe
that may or may not be part of the
team's documentation maybe you're just
looking online or going to the experts
asking questions this is a pull strategy
and I'll be referring to these terms
throughout the presentation this is an
eye chart and it's meant to be an eye
chart this is copy and paste off of
which PDA just the knowledge management
section the reason I throw this in here
is to explain that knowledge management
is actually a whole area of study and
there are a whole bunch of strategies a
whole bunch of tools a whole bunch of
little sub areas of study in this under
under the subject and today I'm just
going to give a brief overview of a
couple of things but there's a ton that
can be read about this topics if you so
desire so how does a CS 577 do it right
now we've got a repository being our
team website we have a standardized
format for Docs being the what that ms
word templates that we use or graded on
these so we're incentivized to actually
do a good job on the documentation and
then furthermore we've got review boards
with our stakeholders and our teammates
in order to make sure that they're good
quality
and also to make sure that there's no
holes why have I been thinking about
this personally I started up a prototype
project at work a couple of months ago
and an interesting thing happened there
we're working on the prototype and it
and it was a limited scope but at one
point management came back and said
we're gonna have a lull where
everybody's going to leave and go work
on other efforts and then probably we're
going to come back and do this for real
like on contract and large scale and so
we need to be able to take all that
we've learned during the prototype and
document it and be able to eat it maybe
it'll be yourselves coming back or other
team other people other developers but
we need to make sure that we don't let
all this knowledge go to waste
so we started thinking about it then
then started on 577 a and I was on Team
seven we were working on a project that
was meant to go for two semesters it
didn't because everybody else went got
internships over a summer but we spent a
lot of time thinking about how can we
push our information into these
documents in 577 B I guess ed my old
team didn't continue but I got put on
another team and and all of a sudden I'm
on this team of seven people and most of
us have weren't on this team before so
we're all kind of a lot of us are on the
dark starting from scratch don't know
what we're doing don't understand the
client don't understand the vision of
the project and we spend a lot of time
doing a lot of pulling of information
talking to the clients talking to the
people that were on the project
previously so at work when I started on
this project I figured well I'll just
send out an email and find out what my
co-workers know about it and I got some
great responses so this is a quote that
I got out of one of the emails that came
back to me that I thought was great he
says I think the key to transferring a
project from one team to another is
documentation requirements design
decisions and rationale designed adopt
documents meeting notes commented code
etc as much as processes of pain that's
one of the reasons we have it and he's
one of our senior developers on
to come around right now but immediately
after I got that email from across the
hall a buddy of mine says no you're not
supposed to document your so you can't
share all your information with other
people you got to be indispensable its
job security look out for yourself if
you're the only one that knows how to do
something on a project and they can't
get rid of you so immediately we have
this classroom with management we have
our customer saying we want this project
to continue but at the same time people
want to keep their jobs so you got to
manage your culture another concept is
whether or not or how do you make
incentivize or make it mandatory or
whatever you do you've got to get people
to put their information into your
system or strategy or however you've
decided to manage your knowledge I
personally like the reward system and
one great example that I found back over
flow comm that they have rankings and
sort of achievements and the idea is
that the more you put into the system
the higher rank and you get and then as
public and so you have bragging rights
is there any monetary reward no are they
paying more no all they did is just give
you something that said you know as a
gold star but it makes people feel good
and incentivizes them to do more to put
more information into the system here
real quick things to document is just a
few suggestions it will vary from
project project by requirements designs
decisions meeting notes commented code
mock-ups think about anything that you
would need if you are coming back
completely from scratch and joining the
project what would that person need in
order to pick up and start working so I
want to go through a couple of tools
that you might use and this is not
certainly not a comprehensive list but
the idea is that here's a few examples
that you can start with you can compare
these with other tools that you've used
or might consider using and also
consider kind of the level of how much
you want to invest into this tool this
first one is Atlassian they have a whole
suite of tools for collaboration project
tracking bug tracking the whole deal but
it's not free you do get technical
support and it's got a ton of
functionality but
want to go to that level there Atlassian
calm another option might be to have a
wiki somewhere wikispaces calm is a
product that my team this semester has
been using it's nice to get rich content
unity it's a wiki so you can put up your
documents and information all in one
place just a simple repository but it's
also free lastly and these are two two
products that I've used to take
screencasts of my code or processes
things that I've done at work camstudio
is an open source product that's what
I'm using right now it's free it's easy
fairly easy to use easy to learn doesn't
give you a lot of editing capability on
the Left I've got Camtasia Studio which
is the COTS off-the-shelf product it's
got all the effects and cool features
that you'd ever want you get your tech
support etc the drawbacks to doing this
I already talked about some of the good
things that come from it but the
drawbacks are that it takes time to do
these videos memory usage because video
is large and also requires a webcam or a
mic so you've got to equip everybody
that's doing these videos with that
hardware here are my references in
closing I just want to say that most of
these references are just to the
products but if you look at these
products and and then look at other
products that you find through googling
or just searching or asking around and
you can look and see there are pros and
cons to each of these and some of these
products might suit you prop your
project better than others be it's your
budget that's limiting you or maybe the
learning curve also consider the
concepts that I've gone over push and
pull strategies incentivizing and and
getting people to buy off on your
strategy is really important otherwise
you can put all this time and effort
into learning or implementing a
repository for your information but it
will never get used so that said I want
to leave you with the disclosing
statement that the knowledge management
is really important
and sometimes simply just you know a
word doc just doesn't cover it you got
there's a lot of things that can that
you can do to do better thank you for
your time
Related Exams
About this Video
|
4.76/5 Rating |
|
Oct 25, 2024 Last updated |
Video Description: Knowledge Management Tools & Concepts, Contemporary Management for B Com 2024 is part of Contemporary Management preparation.
The notes and questions for Knowledge Management Tools & Concepts, Contemporary Management have been prepared according to the B Com exam syllabus.
Information about Knowledge Management Tools & Concepts, Contemporary Management covers all important topics for B Com 2024 Exam.
Find important definitions, questions, notes, meanings, examples, exercises and tests below for Knowledge Management Tools & Concepts, Contemporary Management.
Introduction of Knowledge Management Tools & Concepts, Contemporary Management in English is available as part of our Contemporary Management for B Com & Knowledge Management Tools & Concepts, Contemporary Management in
Hindi for Contemporary Management course. Download more important topics related with notes, lectures and mock test series for
B Com Exam by signing up for free.
Description
Video Lecture & Questions for Knowledge Management Tools & Concepts, Contemporary Management Video Lecture | Contemporary Management - B Com - B Com full syllabus preparation | Free video for B Com exam to prepare for Contemporary Management.
Information about Knowledge Management Tools & Concepts, Contemporary Management
Here you can find the meaning of Knowledge Management Tools & Concepts, Contemporary Management defined & explained in the simplest way possible.
Besides explaining types of Knowledge Management Tools & Concepts, Contemporary Management theory, EduRev gives you an ample number of questions to practice Knowledge Management Tools & Concepts, Contemporary Management tests,
examples and also practice B Com tests.
|
52 videos|42 docs|12 tests
|
|
Explore Courses for B Com exam
|
|
Signup for Free!
Signup to see your scores go up within 7 days! Learn & Practice with 1000+ FREE Notes, Videos & Tests.
Related Searches
shortcuts and tricks
,Previous Year Questions with Solutions
,Summary
,Knowledge Management Tools & Concepts
,Knowledge Management Tools & Concepts
,Contemporary Management Video Lecture | Contemporary Management - B Com
,past year papers
,Exam
,Contemporary Management Video Lecture | Contemporary Management - B Com
,video lectures
,study material
,ppt
,Sample Paper
,Free
,Semester Notes
,Important questions
,Viva Questions
,Extra Questions
,Knowledge Management Tools & Concepts
,Contemporary Management Video Lecture | Contemporary Management - B Com
,practice quizzes
,mock tests for examination
,Objective type Questions
,MCQs
;
Study Knowledge Management Tools & Concepts, Contemporary Management on the App
Students of B Com can study Knowledge Management Tools & Concepts, Contemporary Management alongwith tests & analysis from the EduRev app,
which will help them while preparing for their exam. Apart from the Knowledge Management Tools & Concepts, Contemporary Management,
students can also utilize the EduRev App for other study materials such as previous year question papers, syllabus, important questions, etc.
The EduRev App will make your learning easier as you can access it from anywhere you want.
The content of Knowledge Management Tools & Concepts, Contemporary Management is prepared as per the latest B Com syllabus.
|
© EduRev
|
Education Revolution
|
Follow Us
|
Signup to see your scores
go up
within 7 days!
within 7 days!
Takes less than 10 seconds to signup