# Elicitation Questionnaire - Business Analysis

> **Usage:** Structured questions for phase 2-discover
> **Standard:** BABOK v3 - Elicitation Techniques
> **Model:** OPUS with ULTRATHINK

---

## ULTRATHINK RULE

```
╔══════════════════════════════════════════════════════════════════════════════╗
║  ULTRATHINK: Deep thinking mode for exhaustive elicitation                   ║
╠══════════════════════════════════════════════════════════════════════════════╣
║                                                                              ║
║  During the discover phase, Claude MUST:                                     ║
║  • Consider ALL edge cases before formulating a question                      ║
║  • Challenge EVERY stakeholder assumption                                     ║
║  • Anticipate unexpressed needs                                              ║
║  • Validate completeness before moving to next question                      ║
║                                                                              ║
║  DO NOT:                                                                     ║
║  • Accept vague answers                                                      ║
║  • Skip question categories                                                  ║
║  • Assume stakeholder has thought of everything                              ║
║                                                                              ║
╚══════════════════════════════════════════════════════════════════════════════╝
```

---

## Category 1: Business Context

### 1.1 Fundamental Need

| # | Question | Answer Type |
|---|----------|-------------|
| Q1.1 | What business problem should this module/feature solve? | Free text |
| Q1.2 | What is the current situation (AS-IS)? | Description |
| Q1.3 | What is the target situation (TO-BE)? | Description |
| Q1.4 | What are the measurable success KPIs? | List + values |

### 1.2 Business Value

| # | Question | Answer Type |
|---|----------|-------------|
| Q1.5 | What ROI do you expect? (time, money, efficiency) | Quantitative |
| Q1.6 | What savings or gains will this module bring? | Estimation |
| Q1.7 | What happens if this module is NOT developed? | Impact |
| Q1.8 | What is the priority compared to other needs? | High/Medium/Low |

---

## Category 2: Stakeholders

### 2.1 Identification

| # | Question | Answer Type |
|---|----------|-------------|
| Q2.1 | Who are the direct end users? | List of roles |
| Q2.2 | Who are the indirect beneficiaries? | List |
| Q2.3 | Who is the sponsor/final decision maker? | Name + role |
| Q2.4 | Who can block the project? | List + reasons |

### 2.2 Needs by Role

| # | Question | Answer Type |
|---|----------|-------------|
| Q2.5 | For each role: What tasks should they accomplish? | Per role |
| Q2.6 | What frequency of use per role? | Daily/Weekly/Monthly |
| Q2.7 | What level of technical expertise per role? | Novice/Intermediate/Expert |
| Q2.8 | What current frustrations per role? | List of pain points |

---

## Category 3: Functional Scope

### 3.1 Functionality

| # | Question | Answer Type |
|---|----------|-------------|
| Q3.1 | List ESSENTIAL features (Must-Have) | List |
| Q3.2 | List DESIRED features (Should-Have) | List |
| Q3.3 | List OPTIONAL features (Could-Have) | List |
| Q3.4 | What is EXPLICITLY excluded? | List of exclusions |

### 3.2 Business Process

| # | Question | Answer Type |
|---|----------|-------------|
| Q3.5 | Describe the main user flow | Steps |
| Q3.6 | What are the decision points in the flow? | List |
| Q3.7 | What alternative flows exist? | Per condition |
| Q3.8 | What are the possible error cases? | List |

---

## Category 4: Data

### 4.1 Entities

| # | Question | Answer Type |
|---|----------|-------------|
| Q4.1 | What are the main entities handled? | List |
| Q4.2 | For each entity: important attributes? | Per entity |
| Q4.3 | What relationships exist between entities? | Text schema |
| Q4.4 | Expected data volume? | Estimation |

### 4.2 Data Rules

| # | Question | Answer Type |
|---|----------|-------------|
| Q4.5 | What validations on data? | List of rules |
| Q4.6 | Which fields are required vs optional? | Per field |
| Q4.7 | What specific formats/constraints? | List |
| Q4.8 | Sensitive data to protect? | List + level |

---

## Category 5: Integrations

### 5.1 Existing Systems

| # | Question | Answer Type |
|---|----------|-------------|
| Q5.1 | What internal systems should we integrate with? | List |
| Q5.2 | What external systems? | List |
| Q5.3 | Existing APIs to use? | Documentation |
| Q5.4 | Data to import from another system? | List + format |

### 5.2 Data Flows

| # | Question | Answer Type |
|---|----------|-------------|
| Q5.5 | Flow direction? (inbound/outbound/bidirectional) | Per system |
| Q5.6 | Synchronization frequency? | Real-time/Batch |
| Q5.7 | Data conflict management? | Strategy |
| Q5.8 | Fallback if external system unavailable? | Behavior |

---

## Category 6: Security & Permissions

### 6.1 Access

| # | Question | Answer Type |
|---|----------|-------------|
| Q6.1 | Who can VIEW data? | List of roles |
| Q6.2 | Who can CREATE entries? | List of roles |
| Q6.3 | Who can MODIFY? | List of roles |
| Q6.4 | Who can DELETE? | List of roles |

### 6.2 Restrictions

| # | Question | Answer Type |
|---|----------|-------------|
| Q6.5 | Geographic restrictions? | Countries/regions |
| Q6.6 | Time-based restrictions? (hours, periods) | Ranges |
| Q6.7 | Audit trail required? Which actions? | List |
| Q6.8 | Regulatory compliance? (GDPR, etc.) | List of standards |

---

## Category 7: User Interface

### 7.1 Experience

| # | Question | Answer Type |
|---|----------|-------------|
| Q7.1 | Target devices? (desktop, mobile, tablet) | List |
| Q7.2 | Browsers to support? | List + versions |
| Q7.3 | Accessibility required? (WCAG level) | A/AA/AAA |
| Q7.4 | Dark/light mode required? | Yes/No |

### 7.2 Screens

| # | Question | Answer Type |
|---|----------|-------------|
| Q7.5 | Main screens needed? | List |
| Q7.6 | Existing mockups/wireframes? | Documents |
| Q7.7 | Key information per screen? | Per screen |
| Q7.8 | Possible actions per screen? | Per screen |

---

## Category 8: Performance & Quality

### 8.1 Performance

| # | Question | Answer Type |
|---|----------|-------------|
| Q8.1 | Acceptable response time? | Milliseconds |
| Q8.2 | Number of concurrent users? | Estimation |
| Q8.3 | Expected load peaks? | When + volume |
| Q8.4 | Required availability? (SLA) | Percentage |

### 8.2 Quality

| # | Question | Answer Type |
|---|----------|-------------|
| Q8.5 | Acceptable error rate? | Percentage |
| Q8.6 | Specific tests required? | Types |
| Q8.7 | Available test environments? | List |
| Q8.8 | Overall acceptance criteria? | List |

---

## Category 9: Constraints

### 9.1 Technical

| # | Question | Answer Type |
|---|----------|-------------|
| Q9.1 | Mandated tech stack? | Technologies |
| Q9.2 | Infrastructure limitations? | Description |
| Q9.3 | Technology dependencies? | List |
| Q9.4 | Compatibility constraints? | List |

### 9.2 Organizational

| # | Question | Answer Type |
|---|----------|-------------|
| Q9.5 | Available budget? | Amount |
| Q9.6 | Fixed or flexible deadline? | Date + flexibility |
| Q9.7 | Available resources? | Team |
| Q9.8 | Approval process? | Steps |

---

## Category 10: Documentation & Support

### 10.1 Documentation

| # | Question | Answer Type |
|---|----------|-------------|
| Q10.1 | User documentation needed? | Yes/No + type |
| Q10.2 | Technical documentation needed? | Yes/No + type |
| Q10.3 | User training planned? | Plan |
| Q10.4 | Knowledge base to create? | Scope |

### 10.2 Support

| # | Question | Answer Type |
|---|----------|-------------|
| Q10.5 | Expected support level? | SLA |
| Q10.6 | Who provides level 1 support? | Team |
| Q10.7 | Escalation to level 2? | Process |
| Q10.8 | Monitoring and alerts required? | List |

---

## Questionnaire Usage

### Discovery Phase

1. **Start:** Begin with Category 1 (Business Context)
2. **Adapt:** Skip questions not relevant to the context
3. **Deepen:** Ask follow-up questions on vague answers
4. **Challenge:** Don't accept "we'll see later" on Must-Have

### Follow-up Questions

For each vague answer, use:
- "Can you give a concrete example?"
- "How do you measure that today?"
- "What happens if this rule is not respected?"
- "Who is impacted by this decision?"

### Documentation

Each answer should be documented with:
- Source (who answered)
- Date
- Confidence level (Confirmed/To validate/Hypothesis)
- Open follow-up questions

---

## Support

> **Questions about requirements elicitation?**
>
> 📧 **support@atlshub.ch**
