This can act as the knowledge repository which people can search. They also provide a web front-end to search the logs. There are a few IRC Loggers available which can log the conversations. There could be questions flying back and forth in real time.Īs these conversations go on, we can have a bot recording all the conversations. Whoever has the knowledge and is available can respond back. When somebody has a question they can shoot it on the chat room. When the team members get into office, they can logon to the chat server, just like they logon to IM.
#BEST IRC CHAT ROOMS 2016 OFFLINE#
To solve the issues listed above, I was thinking of installing an IRC chat server and use chat rooms as an offline discussion forum. We are looking at this system to be in development for 3–4 years and then 20–25 years in production. I also think this is not a very sustainable model for managing knowledge within a team over its lifecycle. IMs are little more convenient but they are essentially one-to-one conversations and hence we could see the same issues discussed over and over again. In addition to this, we also use Instant Messengers. when you don‘t know whom to ask or when the so-called expert is not available. While I value face-to-face communication, some times it is not very effective. Work Around: Mostly people walk across team rooms and ask the so-called experts about the issue they are currently facing. The whole Wiki is such a mess there is no easy way to refactor it to find information more intuitively. But the real problem is finding things easily on the Wiki.
#BEST IRC CHAT ROOMS 2016 HOW TO#
Right from how to get started as a new team member to configuration issues to architectural guidelines, everything seems to be captured on the Wiki. We have tried to used a Wiki to capture/document different things that we feel should be shared between the teams. We still seem to be facing issues with the items listed above. Both in terms of Architecture and product vision Managing process and technology related knowledge between the teams, so that each team does not reinvent the wheel.Having good collaboration between teams.We also had a few exchange of team members between the teams. We have gradually grown over time by adding 2–3 new team members to the existing teams and talking the same number of older members and forming new teams. We started of with one team of 8 people about a year ago. We also have couple of Product owners and Project Managers. It includes a QA, a Scrum Master, a Subject mater expert and the rest are developers. Each team has about 8–15 members on the team. All the teams are located in the same building. I‘m currently working on a product which has 8 development teams. In other words, using IRC Chat Rooms as a form of intra-team communication and as a knowledge repository
0 kommentar(er)
