Project blogs are the easiest way to share information within a company.

A well-known fact and a typical problem - in a software company, people from different projects know little about what their colleagues do. No matter how well-placed informal communication, still a lot of useful information is not disclosed in everyday conversations.

And it would seem such a simple tool as project blogs - and is really capable of great help in the transfer of important information between project teams:

• new components that can be used in neighboring projects
• integration code with third-party systems
• found problems with workbacks
• important documents, regulations
• and many other things that can be useful and save the neighboring team a lot of time, and, accordingly, money in general for the company.

Blogging itself is now very common, so many in the team will participate in the development of the project blog - leaving their posts and participating in discussions, thereby “heating up” the communication channel between the project teams.
Imagine how important this is in a large project, several teams working on different parts of it.

And of course, as with the introduction of any new tool, it is important not to forget that project blogs should be easily accessible to all interested, and ideally they should be integrated into the project environment - the tool you work with every day.