sf-agent-framework/sf-core/utils/requirements-tracker.md

AI Agent Orchestration Framework for Salesforce Development - Two-phase architecture with 70% context reduction

# Requirements Tracker Utility - Agent Instructions

## Purpose

This utility provides instructions for AI agents to generate comprehensive
requirements tracking and management solutions for Salesforce implementations,
ensuring complete traceability from business needs to delivered functionality.

## Agent Instructions

### When to Generate Requirements Tracking

Generate requirements tracking components when:

- Project requirements need centralized management
- Traceability across lifecycle is required
- Progress tracking and reporting is needed
- Change impact analysis is necessary
- Compliance documentation is required
- Stakeholder alignment needs coordination
- Quality assurance requires verification

### Core Components to Generate

#### 1. Requirements Management System

Generate management components that:

- Capture and store requirements
- Track status and progress
- Manage dependencies
- Version control changes
- Facilitate approvals
- Enable collaboration

Key tracking elements:

- Functional requirements
- Non-functional requirements
- Technical requirements
- Business rules
- Compliance requirements
- Integration requirements

#### 2. Progress Tracking Engine

Create tracking components for:

- Status monitoring
- Progress reporting
- Milestone tracking
- Velocity calculations
- Burndown analytics
- Completion forecasting

#### 3. Traceability Matrix Generator

Implement traceability for:

- Requirements to design
- Design to implementation
- Implementation to testing
- Testing to deployment
- End-to-end visibility
- Impact analysis

### Configuration Requirements

#### Custom Objects

```yaml
Requirement__c:
  - Requirement_ID__c (Text - External ID)
  - Title__c (Text)
  - Description__c (Long Text Area)
  - Type__c (Picklist)
  - Priority__c (Picklist)
  - Status__c (Picklist)
  - Owner__c (Lookup - User)
  - Business_Owner__c (Lookup - User)
  - Source__c (Text)
  - Approval_Status__c (Picklist)
  - Target_Date__c (Date)
  - Story_Points__c (Number)
  - Dependencies__c (Text Area)

Requirement_Change__c:
  - Requirement__c (Master-Detail)
  - Change_Type__c (Picklist)
  - Previous_Value__c (Text Area)
  - New_Value__c (Text Area)
  - Change_Reason__c (Text Area)
  - Changed_By__c (Lookup - User)
  - Change_Date__c (DateTime)
  - Approval_Required__c (Checkbox)

Traceability_Link__c:
  - Source_Requirement__c (Lookup)
  - Target_Item__c (Text)
  - Link_Type__c (Picklist)
  - Relationship__c (Picklist)
  - Status__c (Picklist)
  - Verification_Status__c (Picklist)
```

### Requirement Lifecycle Management

#### Status Workflow

```
Draft → Under Review → Approved → In Development → Testing → Completed
  ↓         ↓              ↓            ↓               ↓        ↓
Rejected  On Hold      Cancelled   Blocked         Failed   Deployed
```

#### Status Transition Rules

- Draft → Under Review: Complete documentation
- Under Review → Approved: Stakeholder sign-off
- Approved → In Development: Sprint planning
- In Development → Testing: Code complete
- Testing → Completed: All tests pass
- Any → Blocked: Dependency issues
- Any → On Hold: Business decision

### Implementation Patterns

#### Requirements Collection Pattern

1. Stakeholder interviews
2. Document requirements
3. Categorize and prioritize
4. Validate with stakeholders
5. Obtain formal approval
6. Baseline for development

#### Change Management Pattern

1. Capture change request
2. Analyze impact
3. Assess dependencies
4. Estimate effort
5. Obtain approvals
6. Update baselines

#### Progress Tracking Pattern

1. Regular status updates
2. Automated notifications
3. Dashboard reporting
4. Stakeholder communication
5. Issue escalation
6. Milestone reviews

### Tracking Metrics to Generate

#### Progress Metrics

```
Requirements Progress = (Completed Requirements / Total Requirements) × 100
Story Points Progress = (Completed Points / Total Points) × 100
Velocity = Story Points Completed / Sprint Duration
Burndown Rate = Remaining Work / Time Remaining
```

#### Quality Metrics

```
Requirements Stability = 1 - (Changed Requirements / Total Requirements)
Traceability Coverage = (Traced Items / Total Items) × 100
Approval Rate = (Approved Requirements / Submitted Requirements) × 100
Defect Leakage = Defects Found Post-Implementation / Total Defects
```

#### Delivery Metrics

```
On-Time Delivery = Requirements Delivered On Schedule / Total Requirements
Scope Creep = New Requirements Added / Original Requirements
Rework Rate = Requirements Reworked / Total Requirements
Stakeholder Satisfaction = Average Rating from Feedback
```

### Dashboard Components to Generate

#### Executive Dashboard

Display:

- Overall progress percentage
- Requirements by status
- Milestone achievement
- Risk and issue summary
- Budget and timeline status
- Stakeholder satisfaction

#### Project Manager Dashboard

Show:

- Sprint progress
- Team velocity
- Blocked requirements
- Change requests
- Resource allocation
- Dependency tracking

#### Team Dashboard

Include:

- Assigned requirements
- Work in progress
- Testing status
- Documentation needs
- Collaboration items
- Next priorities

### Reporting Capabilities

#### Status Reports

Generate reports showing:

- Requirements completion status
- Progress against milestones
- Issues and blockers
- Change impact analysis
- Resource utilization
- Quality metrics

#### Traceability Reports

Create reports for:

- Requirements to test cases
- Requirements to user stories
- Design to implementation
- Code to requirements
- Defects to requirements
- Coverage analysis

#### Compliance Reports

Develop reports covering:

- Regulatory compliance
- Audit trail documentation
- Approval workflows
- Change control
- Quality assurance
- Risk management

### Best Practices to Implement

1. **Requirements Definition**
   - Clear and measurable
   - Testable criteria
   - Priority classification
   - Acceptance criteria
   - Owner assignment

2. **Change Control**
   - Formal change process
   - Impact assessment
   - Approval workflows
   - Version management
   - Communication plans

3. **Stakeholder Management**
   - Regular reviews
   - Clear communication
   - Expectation setting
   - Feedback loops
   - Decision tracking

4. **Quality Assurance**
   - Peer reviews
   - Validation checkpoints
   - Testing alignment
   - Documentation standards
   - Continuous improvement

### Advanced Features to Consider

1. **AI-Enhanced Analysis**
   - Requirement similarity detection
   - Auto-categorization
   - Impact prediction
   - Risk assessment
   - Smart recommendations

2. **Automated Workflows**
   - Status transitions
   - Notification triggers
   - Approval routing
   - Progress updates
   - Report generation

3. **Integration Capabilities**
   - ALM tools integration
   - Test management systems
   - Project management tools
   - Documentation platforms
   - Communication systems

### Error Handling Instructions

Handle these scenarios:

1. Missing requirement data
2. Circular dependencies
3. Conflicting priorities
4. Approval delays
5. Resource constraints

Recovery strategies:

- Data validation rules
- Dependency analysis
- Priority matrices
- Escalation procedures
- Alternative workflows

### Testing Requirements

Generate test classes for:

1. Requirements creation and updates
2. Status transition workflows
3. Dependency management
4. Traceability links
5. Report generation accuracy

### Success Metrics

Track and measure:

- Requirements completion rate
- On-time delivery percentage
- Change request volume
- Stakeholder satisfaction
- Quality metrics achievement
- Process efficiency improvements

```

```