Confluence

Confluence is a very famous product for project management.

Comments: If you're new to it, you need to adapt. You also have a reluctance to tools that you haven't used before. But for effective projects and business management, you now have to use collaborative tools. You can get a better work environment by adapting quickly to the initial inconvenience.

Pros:

Project management, output, work-specific human resources management, sharing and collaboration with all participants are important, and Confluence solves all these things at once. There are many services and solutions for efficient project management, but we always use Confluence.

Cons:

Perhaps because it is mainly used for necessary functions, there are no disadvantages yet.

Robust Content Management Tool with lots of potential

Comments: Overall, it is a great tool with really great features and different capabilities that have allowed my team to really lean into content management. Would recommend this to other companies!

Pros:

Confluence is our go-to content management and knowledge based tool. The ability to create spaces by team or departments is really useful and my favorite feature is the ability to give permission by page instead of just by space. We have a main team focused on maintaining our knowledge base, but it's helpful that we can also assign unique individuals who are subject matter experts to also help that team update the content.

Cons:

At times it feels like Confluence may be a bit too robust. It's a great content management system, but can sometimes over complicate a search for a particular page. It can take some time to locate the page you are looking because so many results pop up. You have to weed through the results to find the one you're seeking.

Confluence for documentation

Comments: We use both Jira and confluence on our projects. Confluence was initially started on the project to replace word documents for programming specs and request. It was a mixed uptake due to higher learning curve over just word.

Pros:

A adequate documentation system that can integrate with Jira issue/ticket system.

Cons:

Not the best collaboration without adding in third party addins.

Knowledge Base as root

Comments: It has a learning curve at the beginning. Still, later on, and not so long after, you will find yourself putting everything on confluence because it is easy, well-managed, and perfect for a platform where people can find documentation and information in a well-presented format.

Pros:

Confluence is part of an already well-positioned and easy-to-implement ecosystem where multiple tools perform a specific job in a workflow. This makes it easy and friendly to set up and run; using information from other platforms like JIRA and Bitbucket, everything comes together in an excellent and organized way without much effort.

Cons:

It might be overwhelming at first; there are plenty of options and personalization elements you can include, so you might think, "It is too much for me." But by watching a couple of YouTube videos, you will see how you can customize it to suit your needs and start using its powerful features.

Alternatives Considered: Slack

Reasons for Choosing Confluence: We used to have documentation inside our bitbucket repositories, but we required a well-defined and easy-to-access platform where the team could both collaborate and access the information for a particular part of the application without needing to go through the code to find it

Switched From: Bitbucket

Reasons for Switching to Confluence: We found that Confluence integrated naturally with JIRA and our Bitbucket repositories, giving us an organic way to set up all our workflows in a single platform. While we could use Slack or any other messaging platform to communicate, Confluence worked perfectly for our documentation needs.

One of the best

Pros:

The ease of use makes it one of the best team work management platforms out there. We are a development team that uses Jira and the integration with Confluence makes our work seamless.

Cons:

As of now, nothing really. We still don't use the Database functionality as it is in alpha.