Building a Confluence team

We need teams that will prepare, develop, and update our collaboration environment where we can collect and organize our knowledge.

Although we can provide most of this platform’s maintenance and development work with automation or Confluence’s features, it is people who will do the actual work.

Checking out team building tips

You can benefit from the following tips when building a team that will help you throughout your Confluence journey:

• Every company is unique, whether it’s a start-up with 10 people, a small business, or an enterprise with 5,000 people. They all have their own authentic contexts, problems, and needs.
• It may be necessary to set up different teams for different parts of the process (planning, initial setup, and maintenance).
• To keep such a platform alive, we must identify the jobs that need to be done and distribute them to the relevant roles and people.
• We can talk about the fundamental roles in almost every company: site, product, space, and content managers.
• In addition, roles may differ according to the diverse needs of other teams.
• You can build the team iteratively.
• The responsibilities of everyone who will use Confluence must be determined. Everyone should have some duties, but some should have more responsibilities.
• You can make a systematic stakeholder identification.

Identifying roles using RASCI within your team

We recommend that you identify your Confluence team’s roles and responsibilities to ensure everything is clear. That’s where RASCI comes into play.

RASCI (responsible, accountable, supporter, consultant, informed) is used to identify all the roles and responsibilities within a project. We recommend that you use this technique while adopting Confluence within your company, as it will help clarify the responsibilities of each project team member.

A detailed explanation of RASCI is provided as follows:

• Responsible (R): The person responsible for completing the work. This is an execution role.
• Accountable (A): The person accountable for the work’s outcome. This is a management role.
• Supporter (S): People who help those responsible to finish the work.
• Consultant (C): People from whom we’ll get help when we’re stuck or confused.
• Informed (I): People whom we keep informed throughout the work.

The following is an example of a RASCI table that you can use as a starting point when identifying the roles and responsibilities within your Confluence team:

Table 1.5: Sample RASCI table

Maintaining your Confluence team

You should maintain your Confluence team and keep it healthy. The following are some tips that can help you when maintaining your team:

• Continuous education on Confluence and content management is a must.
• The use of Confluence can feed the performance evaluation criteria.
• Support from the management and the support team is crucial.
• Tracking, monitoring, and reporting on Confluence teams’ performance is vital.
• You must clearly define roles and responsibilities to plan, realize, and maintain a healthy Confluence environment. You can use the previous table as a starting point when determining the roles and responsibilities for this project.

Atlassian University offers numerous, high-quality courses related to Confluence. Some of these courses are free, while others are paid. By studying these courses, you can keep yourself up to date with Confluence. Additionally, you can earn badges and certificates from this platform. We recommend exploring Atlassian University and taking advantage of the valuable resources available there. You can access the Confluence courses on Atlassian University at the following link: https://university.atlassian.com/student/catalog/list?search=confluence.