Ana içeriğe geç
Versiyon: 1.0.2

PBI Generation Wizard

The Generation Wizard guides you through the process of creating Product Backlog Items using AI.

Step 1: File Selection​

Document Upload​

Upload requirement documents:

  • Supported Formats: PDF, DOCX, DOC, TXT, RTF
  • File Size: Up to 10MB per file
  • Multiple Files: Upload several documents at once

How to upload:

  1. Click the upload area or drag and drop files
  2. Wait for processing confirmation
  3. Files appear in the selected list

Text Input​

Paste requirements directly:

  1. Click the Text tab
  2. Paste your content in the text area
  3. Supports rich text and formatting

Image Input​

Add visual references:

  • Screenshots - Application mockups
  • Wireframes - Design documents
  • Diagrams - Flow charts, architecture

Supported formats: PNG, JPG, JPEG, GIF, WebP

SmartRequest Source​

Use approved SmartRequest data:

  1. Click the SmartRequest tab
  2. Select from available requests
  3. Choose data fields to include:

Core Content (Default):

  • ☑️ Summary
  • ☑️ Description
  • ☑️ Acceptance Criteria
  • ☑️ Custom Field Answers

Additional Context (Optional):

  • ☐ Recommended Actions
  • ☐ Original Description
  • ☐ Evaluation Q&A
  • ☐ Attached Documents
  • ☐ Priority Context

Step 2: Configuration​

AI Model Selection​

Choose the AI model for generation:

  • Default company model
  • Custom configured models
  • Different models for different use cases

Language Settings​

Select output language:

  • Turkish - PBIs in Turkish
  • English - PBIs in English

Platform Selection​

Choose target platform(s):

  • ☑️ Web Application
  • ☑️ Mobile Application
  • ☑️ API / Backend
  • ☑️ Desktop Application

PBI Types​

Select which types to generate:

  • ☑️ Epic - High-level objectives
  • ☑️ Feature - Distinct functionalities
  • ☑️ User Story - Specific requirements
  • ☑️ Acceptance Criteria - Completion conditions

Quantity Settings​

Specify PBI counts:

  • Auto - AI determines appropriate quantity
  • Manual - Set specific numbers per type

Quality Level​

LevelProcessing TimeOutput Detail
Speed~30 secondsBasic PBIs
Balanced~1 minuteStandard detail
Quality~2 minutesComprehensive

Step 3: Analysis​

During this step, the AI processes your inputs:

Processing Stages​

  1. Document Parsing - Extracting text and structure
  2. Content Analysis - Understanding requirements
  3. PBI Generation - Creating backlog items
  4. Hierarchy Building - Organizing structure

Progress Indicators​

  • Real-time progress bar
  • Current processing stage
  • Estimated time remaining

What the AI Analyzes​

  • Business objectives and goals
  • User needs and pain points
  • Technical requirements
  • Acceptance criteria patterns
  • Dependencies and relationships

Step 4: Results​

Viewing Generated PBIs​

List View​

All PBIs in a flat list:

  • Filter by type (Epic, Feature, Story, AC)
  • Search within results
  • Sort by various criteria

Hierarchical View​

Nested structure showing relationships:

📁 Epic: User Authentication
📂 Feature: Login System
📄 Story: As a user, I want to login...
✓ AC: System accepts valid credentials
✓ AC: Error shown for invalid credentials
📄 Story: As a user, I want to reset password...
📂 Feature: Registration
📄 Story: As a new user, I want to register...

Editing PBIs​

Click any PBI to edit:

  • Title - Update the PBI name
  • Description - Modify content
  • Type - Change PBI type
  • Acceptance Criteria - Add/edit/remove

Filtering Results​

FilterDescription
TypeShow specific PBI types
SearchFind by keyword
StatusFilter by completion

Exporting Results​

Export to Excel​

  1. Click Export button
  2. Select Excel format
  3. Choose columns to include
  4. Download the file

Export to PDF​

  1. Click Export button
  2. Select PDF format
  3. Include/exclude sections
  4. Generate document

Export to Integration​

When integrations are configured:

  1. Click Export to Jira/Azure DevOps
  2. Map fields if needed
  3. Confirm creation

Tips for Better Results​

Input Quality​

✅ Do:

  • Provide clear, specific requirements
  • Include user context and personas
  • Mention technical constraints
  • Add acceptance criteria examples

❌ Don't:

  • Use vague or ambiguous language
  • Skip business context
  • Provide incomplete information

Configuration Tips​

  • Start with Balanced quality for most use cases
  • Use Speed for initial brainstorming
  • Use Quality for final documentation
  • Enable all relevant platforms

Review Process​

  1. Always review generated content
  2. Verify acceptance criteria completeness
  3. Check hierarchy organization
  4. Refine story point estimates