Confluence for Business Analysts: A Quick Tour (Spaces, Pages, Templates)
A quick tour of Confluence for business analysts: the project space, its home page, the page tree, finding a page, and the templates you start new pages from.
Step by step
Spaces
- Confluence tour. Confluence is where a project's documents live: requirements, meeting notes and decisions. If you are a new business analyst, these are the parts you will use every day.
- A space. Everything starts with a space. Most teams make one space per project, like the Online Shop Project space here. Each space has a home page. This one says what the project is and where to start reading.
Pages
- The page tree. On the left is the page tree. Every document in the space is a page, like the project overview.
- Find a page. If you can't find something, type in the box above the page tree. It finds pages by their title, so typing Glossary brings up the Glossary page. Click the page in the results to open it.
- A page. A page holds text, lists and tables. The Glossary page is a table of the words the project uses, so everyone means the same thing. To change a page, click Edit. Everyone works on the same page, so there is only one version, not 10 copies in email.
Templates
- Templates. New pages often start from a template. Open the space's templates and Confluence shows ready-made pages for requirements, meeting notes, retrospectives and more. Click a template to look inside it. Here it's the retrospective. Its preview opens on the right. The headings and tables are already there, so you only fill them in.
- Create. For a blank page, use the Create button at the top. It's there at any time.
Recap
- Space, pages, templates. To sum up: one space per project, with a home page. Every document is a page in the tree. Find pages by title, and start new ones from a template.
Common mistakes
- Sending copies of a document by email. The copies drift apart and nobody knows which one is current. Share the link to the page and edit the page itself, so there is only one version.
- Vague page titles. The box above the page tree finds pages by title, so a page called Notes 2 is hard to find. Give each page a clear title, like Glossary.
- Starting every page from a blank page. For requirements, meeting notes or retrospectives, start from a template. The headings and tables are already in place, so pages across the project look the same.
- Spreading one project across several spaces. Keep one space per project, with a home page that says where to start reading. Then the whole page tree for the project is in one place.
When a business analyst uses this
In a requirements workshop, stakeholders use "order" and "purchase" to mean different things. The business analyst adds both words to the project's Glossary page in Confluence with one agreed meaning each. Then everyone, including the developers, works from the same definitions instead of a copy in someone's inbox.
Questions people ask
What is Confluence in business analysis?
Confluence is a shared space where a project's documents live, such as requirements, meeting notes and decisions. Business analysts write and keep these documents there as pages the whole team can read and edit.
How do business analysts use Confluence?
They keep one space per project and write requirements, glossaries and meeting notes as pages, often starting from a template. Everyone edits the same page, so there is one version instead of copies in email.
