Summary of "JIRA Tutorial for Business Analysts & Product Owners Part 2 - Managing Requirements with Confluence"

High-level summary

Purpose: Show how a Business Analyst (BA) can use Confluence to manage requirements and BA deliverables so teams have clarity, reduce risk, and work more productively.
BA mission: create clarity around six core responsibilities — stakeholders, context, need, solution, change, and value. (Team-specific but broadly applicable.)
When Confluence adds the most value in Scrum:
- During sprint planning: define, refine, and estimate user stories; capture stakeholders, context, dependencies, technical implications, and value.
- After a sprint: document how production/behavior changed so future planning and onboarding have an authoritative source.
Audience/use cases: most valuable in medium/large organizations or products that are part of a larger system; may be unnecessary for very small, simple products.

Concrete how-to items and best practices

Create a Confluence space (team-level container)
- Decide the appropriate level: product, release train/value stream, or team depending on collaboration boundaries.
- Use a template if you know the structure you want; otherwise start with a blank space.
- Note: spaces are for the whole team (BAs, devs, POs, QA, etc.). Someone else (scrum master, dev lead, admin) may create the space.
Create and place pages correctly
- Prefer creating a page from the Pages section to see and control the hierarchy rather than using the quick “Create” button, which can place the page where you don’t intend.
- Use the Rich Text Editor to add headings, bold text, lists, tables, code snippets, etc.
- Browse available page templates for useful shortcuts.
Build basic BA deliverables in Confluence
- Glossary
  - Use a table with a header row (the header stays visible while scrolling).
  - Add columns/rows from the UI and allow sorting by column to help readers find terms.
  - Good first deliverable: low effort, high value for onboarding and shared language.
- Models and diagrams
  - Document process models, context diagrams, process flows, data flow diagrams, ERDs, etc.
  - Use diagramming plugins (draw.io, Lucidchart, Visio integrations) or built-in widgets.
  - Embed existing diagrams or create new ones inline; add explanatory text on the same page to describe diagram elements.
- Code snippets (optional)
  - Insert code snippets when sharing small examples or API call samples with developers.
Use plugins and admin support
- Many useful Confluence extensions (draw.io, mind map widgets, etc.) are available; adding them typically requires admin permission.
- If a feature is missing, request the plugin from Confluence administrators.
Link and cross-reference content
- Link pages so readers can jump directly to relevant details (for example, link an attendee-management page to the Google API doc).
- Link content at the user-story level so developers/QAs can quickly access context, API docs, diagrams, and acceptance criteria.
- Insert or embed external docs or spreadsheets when necessary.
Organize your space in a way that fits the team
- Common patterns:
  - Functional decomposition: top-down by feature/function (good for discoverability by domain).
  - Deliverable-type organization: group by process docs, ERDs, requirements, etc.
  - Technical vs. business subspaces/pages: separate or nested depending on team needs.
- Choose an organization that reflects how people search for information (process-heavy vs data-heavy vs function-heavy systems).
Integrate Confluence with Jira
- Link Confluence pages to Jira issues (user stories) so the dev/QA team can access requirements, diagrams, API docs, and acceptance criteria directly from the Jira story.
- Link an entire Confluence space to a Jira project so you can browse Confluence content from within Jira.
- Use Confluence pages to support Definition of Ready (dependencies tracked, story estimated, technical implications understood, etc.).

Practical tips and recommended habits

Start small: create a glossary and a few key process or feature pages.
Maintain headers and a consistent structure so pages are readable and scannable.
Use sorting, filtering, and table features to keep reference material usable.
Prefer embedding diagrams rather than linking separately when context is needed beside the diagram.
Keep Confluence a collaborative space — authorship and editing are for the whole team, not just the BA.
If uncertain how to structure the space, iterate and adapt to the team’s behavior.

Tools mentioned

Confluence (core)
Jira (integration with Confluence)
draw.io (diagramming plugin)
Mind map widget (plugin)
Other diagram tools referenced: Visio, Lucidchart

Example used in the video

“Travel Buddy” fictional app / Travel Buddy Confluence space and Jira project demonstrate the workflow: glossary, attendee management page, Google API doc, diagrams, and links between Confluence and Jira.