Build it team knowledge base with blog and Wiki

Recently, my team has been discussing the impact of web on the upgrade and transformation of enterprise networks. More people are talking about the personalized experience that web brings to users, reflecting "my homepage as my master ". However, I would like to add that Web2.0 not only brings about the improvement of user experience, but also makes the Internet decentralized. Everyone can be the source of information, it is very easy for anyone to express their opinions ".

The idea of Web2.0 can also be applied to the internal construction of IT teams, especially the construction of team knowledge bases. Every member is the source of knowledge and will consciously maintain the correctness of knowledge. Based on this idea of team collaboration, wiki is indeed a very good knowledge base building platform, refer to [using flexwiki to build the knowledge base of the project team]. But how can we ensure the Creative Enthusiasm of team members? I went on to think about blog, which depends on my personal performance to stimulate creative enthusiasm.

Main content:
1. Current Situation of my team's knowledge accumulation
2. Significance of Knowledge Accumulation
2. Why not a forum?
3. Why choose Wiki and blog?
5. Scope of Wiki inclusion
6. Knowledge management references
7. behaviors to be avoided

Current Situation of Knowledge Accumulation

To put it simply, the current situation of my IT team (myteam for short)'s knowledge accumulation is not general. It is for your reference. Basically, there is no accumulation of knowledge in myteam. If a person leaves the company, the development experience and technology of the project will be lost. If the project owner wants to learn this knowledge, he can only read the code, read the requirements and design documents, or consult other Members who have been involved in the project. However, this process is very time-consuming: Because we advocate a clear division of labor among members, other members may not be familiar with the work done by the departing members, even if they know what it is, this is one of them. Second, the huge demands and design documents are difficult to pass on experience and technology. Thirdly, reading code is a very time-consuming and inefficient task, especially when the claimed member is scheduled to modify the bug in the original code, the original code has a disturbing effect.

To solve this problem, I would like to have two ideas: the first method to adopt XP encouragement is that every member has a deep understanding of the work done by other Members, but it is too difficult for myteam, when every member can't finish his/her work, how can he learn about the work of other members? The second approach is to accumulate the experience and problem solutions of each member in the project development process through the knowledge base as learning materials for new members, or a reference for other members to solve similar problems.

Significance of Knowledge Accumulation
The importance of knowledge accumulation is self-evident. First, knowledge accumulation can reduce the cost of knowledge and reduce the knowledge loss caused by the frequent turnover of IT teams. Secondly, the process of knowledge accumulation is a steady incremental growth. The collection of personal knowledge into the team's knowledge makes the team's knowledge system more perfect and can also become a reference for new member training.

Why not a forum?
So why not choose a forum? As far as I know, many IT teams have internal discussion forums, but I understand that the Forum is like a square. It is a place for discussion at a gathering, not suitable for knowledge accumulation, what's more, for the team, we recommend face to face conversations and discussions.
The Forum mode is summarized as follows:
1) the landlord posted a post
2) enthusiastic discussions (replies)
3) the viewer reads the post, filters the discussion content, and summarizes the final answer.
For wiki, the answer and method that the team members think is the best. New members can adopt the solution directly, or you can modify it directly when you have better opinions.

Why?WikiAndBlog
For individuals, blog provides a simple way for users to express their opinions. It is also a good platform for personal knowledge accumulation and self-presentation. For the team, the blog also provides a good way to understand other members. by reading his blog, you can understand what he thinks, thinks, and learns, so that the knowledge can be spread in a timely manner.

If you accidentally know the blog address of a colleague, will you go up and check it out?

I think most people will go up and look at it. People will consciously care about things around their lives, not to mention working with colleagues every day. Therefore, the Team's blog is very easy to form a virtuous circle of "writing blogs"-> "reading and commenting frequently"-> "writing more blogs, it constantly inspires team members to post their latest thoughts and lessons on their blogs.

For the team, the blog also has its shortcomings: the blog is suitable for individuals to express their opinions, but it is not suitable for the team's knowledge accumulation. What the team needs is a continuous and stable accumulation of knowledge. Wiki can well make up for this shortcoming of the blog. By constantly incorporating personal opinions into the team's knowledge system, it forms an increasingly sophisticated knowledge base. Some people say that "Wiki is used for the popularization of old knowledge, while blog is used for the innovation of new knowledge. Is it not a foreseeable revolution of knowledge that heroes charge in front and people supply in the back ?".

WikiRange
As a team's knowledge base, wiki is not suitable for collecting highly controversial and subjective content. Content such as "team development should change or revolution" and "my views on team development" is not suitable for wiki. The content included in the Wiki should be as satisfying as possible: skillful, empirical, objective, and knowledge can be used to achieve the goal of "no more mistakes I 've taken" or "Understanding the latest knowledge. Therefore, for the team wiki, it is suitable to include a summary of the Members' work experience, solutions to technical difficulties, or introduce some new knowledge.

Knowledge management references
Of course, building a wiki and blog is very easy for the IT team, but how can we make everyone actively blog and Wiki and give full play to the role of the knowledge base, I still need to do a lot of work, so I will try again. I have recently read some documents for your reference:

· Wiki, blog, and project knowledge management #

· The ins and outs of Wiki and enterprise applications #

· E-works-> library-> Enterprise Management-> knowledge management-> Performance Management for knowledge workers #

· E-works-> library-> Enterprise Management-> knowledge management-> creating a knowledge culture #

· Responsible for knowledge management #

· How far is your enterprise from knowledge management? #

· Comment: knowledge management, the next gold mine of Informatization? -Csdn news #

· Progress and research direction of knowledge management-the world of inheritance #

Behavior to be avoided
Finally, we will illustrate some actions that we usually need to avoid that are not conducive to the accumulation of team knowledge:
1. Avoid P2P technology sharing as much as possible: new technologies and good ideas should be shared as teams
2. Reject meaningless knowledge accumulation: for example, for some large projects, there are usually dozens or even hundreds of documents, however, it is a pity that these documents are generally saved in a simple form and are hard to be reused.