Smart PBI
Smart PBI turns requirements into a product backlog.
It reads documents, text, images, Confluence pages, Figma designs, existing backlog items, and SmartRequests, and generates epics, features and user stories with acceptance criteria. The generated items are then reviewed, edited, approved, and pushed into Jira, Azure DevOps, or a spreadsheet.
The pages
| Page | Route | What it is for |
|---|---|---|
| Dashboard | /smart-pbi/dashboard | Generation KPIs, backlog breakdown, recent sessions |
| PBI Board | /smart-pbi/pbi-board | Kanban workflow, approvals, Jira linkage |
| Smart PBI Generation | /smart-pbi/generation | The generation wizard |
| PBI Sessions | /smart-pbi/sessions | Past runs, their output, regeneration and export |
| File Management | /smart-pbi/files | Source documents — the shared Analyzer file store |
| Settings | /smart-pbi/settings | Defaults for model, language, quality, types, platforms |
How work moves through the module
- Generate. Pick sources, configure the run, and let the AI produce a backlog.
- Review. Edit, regenerate, add, duplicate, or delete items inside the session.
- Transfer. Move the items you want to keep onto the PBI Board.
- Work. Assign items, set priority and risk, and move them across the workflow columns.
- Approve. Submit an item for approval and let the configured approvers sign off.
- Deliver. Export to Jira, Azure DevOps, or Excel, or link items to Jira issues directly.
What gets generated
| Type | What it is |
|---|---|
| Epic | Large work that can be broken down into features |
| Feature | Functionality that provides business value |
| User Story | A small piece of functionality from the user's perspective |
| Acceptance Criteria | The conditions a user story must meet |
Epic, Feature and User Story are the three stored item types. Acceptance criteria hang off a user story rather than existing as items of their own.
You do not have to generate all three levels. Which levels you enable decides the shape of the result — see Hierarchy modes.
Generation quality
Three quality levels trade speed against thoroughness.
| Level | Use it for |
|---|---|
| Speed | Quick drafts and brainstorming |
| Balanced | The recommended default |
| Accuracy | Thorough analysis for work that matters |
Set the default in Settings and override it per run in the wizard.
Getting output out
| Target | Result |
|---|---|
| Excel | Downloads a spreadsheet of the selected items |
| Jira | Creates issues in a Jira project |
| Azure DevOps | Creates work items, preserving the hierarchy |
Individual board items can also be linked to an existing Jira issue, or turned into a new one, without a full export.
SmartRequest as a source
An approved SmartRequest can be handed straight to Smart PBI as generation input. Requests are consumable while they are evaluated, submitted, or approved.
Related modules
| Module | Relationship |
|---|---|
| Analyzer | Owns the document store and the settings screen Smart PBI reuses |
| SmartRequest | Feeds approved requests in as generation sources |
| CaseWriter | Takes generated backlog items and writes test cases from them |
Quick start
- Set your defaults in Settings — model, language, quality, which types to generate, and target platforms.
- Upload a requirements document from File Management, or bring one in from Confluence.
- Run the generation wizard and review the result.
- Transfer the items you want onto the PBI Board.
- Submit them for approval, then export or link them to Jira.
A clearly structured source document produces a better backlog. Sections, explicit business goals, and concrete requirements all give the AI something to anchor on.
