Pregunta: "Whiches son los blockers más críticos?"

AI Response:
🚨 Critical Blockers Analysis:

High Priority Blockers (3):
├── PLAT-234: API integration failing (blocks 5 other tickets)
├── PLAT-189: Database migration pending (affects entire sprint)
└── PLAT-156: Design approval needed (blocking frontend work)

Impact Analysis:
• 12 tickets waiting on these 3 blockers
• Estimated 2-day delay if not resolved by tomorrow
• Ana and Carlos most affected (60% of their sprint work blocked)

Recommended Actions:
1. Escalate PLAT-234 to DevOps team immediately
2. Schedule emergency design review for PLAT-156
3. Consider parallel work streams for PLAT-189 dependencies

Pregunta: "¿Vamos a completar el sprint a tiempo?"

AI Response:
📊 Sprint 24 Completion Forecast:

Current Status (Day 8 of 10):
├── Completed: 23 SP (68% of 34 SP commitment)
├── In Progress: 8 SP (Ana: 5 SP, Carlos: 3 SP)
├── Remaining: 3 SP (2 small bugs, 1 documentation task)

Completion Probability: 89%
├── Historical pattern: Team completes 92% when at 68% by day 8
├── Remaining work: Low complexity, no dependencies
├── Team capacity: No planned time off, normal velocity
└── Risk factors: None identified

Recommendation: On track for successful completion
Next check-in: Tomorrow at 2pm to confirm final push

Pregunta: "How está el workload del team?"

AI Response:
👥 Team Workload Analysis - Frontend Team:

Current Assignments:
├── Ana: 13 SP (110% capacity) ⚠️ Overloaded
├── Carlos: 8 SP (80% capacity) ✅ Optimal
├── Maria: 5 SP (50% capacity) 📈 Can take more
└── Tom: 10 SP (100% capacity) ✅ Fully utilized

Workload Trends:
• Ana consistently over-capacity last 3 sprints
• Maria ramping up well, ready for more complex work
• Team total: 36 SP vs 40 SP capacity (90% utilization)

Recommendations:
1. Redistribute 3 SP from Ana to Maria
2. Consider Ana for architecture/mentoring focus
3. Team well-balanced overall, minor adjustment needed

Settings > Integrations > Jira > Custom Fields

Commonly mapped fields:
├── Story Points → Effort estimation
├── Business Value → ROI analysis  
├── Customer Impact → Priority scoring
├── Technical Risk → Risk assessment
└── Target Release → Roadmap planning

Pregunta: "What features tienen mayor business value?"

AI Response:
💰 Business Value Analysis (Last Quarter):

High Value Features Delivered:
├── User Dashboard Redesign: 9/10 business value, 34 SP effort
├── Mobile App Performance: 8/10 business value, 21 SP effort  
├── API Rate Limiting: 7/10 business value, 13 SP effort

Value vs Effort Efficiency:
• API Rate Limiting: Best ROI (7 value / 13 effort = 0.54)
• Dashboard Redesign: Good ROI (9 value / 34 effort = 0.26)
• Mobile Performance: Moderate ROI (8 value / 21 effort = 0.38)

Recommendation: Focus on similar high-value, low-effort features
Next candidates: Security improvements, Search optimizestion

Pregunta: "Why se retrasó el project MOBILE?"

AI Response:
🔍 MOBILE Project Delay Analysis:

Timeline Reconstruction:
Week 1-2: Normal progress (32 SP completed)
Week 3: Slowdown began (18 SP completed)
Week 4-5: Major delays (12 SP completed total)

Root Cause Analysis from Comments:
├── Week 3: "API integration more complex than expected" (Ana, PLAT-145)
├── Week 3: "Need design clarification before proceeding" (Carlos, PLAT-167)  
├── Week 4: "Blocked waiting for backend team" (Maria, PLAT-178)
└── Week 5: "Scope creep - 3 new requirements added" (Tom, PLAT-189)

Key Decision Points:
• Day 15: Decision to rebuild API integration (added 1 week)
• Day 18: Scope expansion approved by stakeholders (added 5 SP)
• Day 22: Backend dependency identified (external team delay)

Lessons Learned:
1. API complexity assessment needs improvement
2. Cross-team dependencies should be identified earlier  
3. Scope change process needs tighter control
4. Design review should happen before development starts

Settings > Integrations > Jira > Field Mapping

Common mappings:
├── Story Points → Effort (auto-detected)
├── Business Value → ROI Analysis
├── Customer Impact → Priority Scoring  
├── Technical Risk → Risk Assessment
├── Target Release → Roadmap Planning
└── QA Status → Quality Tracking

Si tienes Jira admin access:
1. Impulsum configura webhooks automáticamente
2. Covers all important events (issue updates, comments, etc.)
3. Includes security validation (HMAC signatures)
4. Self-healing si webhooks fail

Jira Admin > System > WebHooks > Create WebHook

Webhook URL: [Provided by Impulsum]
Events to track:
├── Issue Created, Updated, Deleted
├── Issue Commented  
├── Issue Transitioned
├── Sprint Started, Completed
└── Project Updated

Security: Enable HMAC SHA256 validation

Problem: Project missing from Impulsum
Cause: No Browse Projects permission
Solution: Contact Jira admin para project access

Problem: Some issues missing o incomplete
Cause: Issue-level security restrictions
Solution: Verify View Issues permission para specific issue types

Problem: Bi-directional sync not working
Cause: Missing Create Issues permission  
Solution: Request Create permission o disable bi-directional features

Settings > Integrations > Jira > Project Selection

Recommended approach:
├── ✅ Active projects only
├── ✅ Projects you manage directly  
├── ✅ Projects your team contributes to
├── ❌ Archived o completed projects
└── ❌ Projects you only observe

Advanced Settings > Issue Filters

Common filters:
├── Exclude: Resolved issues older than 6 months
├── Include: Only specific issue types (Story, Bug, Task)
├── Exclude: Issues with security level restrictions
├── Include: Issues assigned to your teams only
└── Exclude: Spam o test issues

Settings > Data Management > Retention Policies

Recommended settings:
├── Active issues: Keep indefinitely
├── Resolved issues: 12 months
├── Comments: 6 months  
├── History: 3 months detailed, 12 months summary
└── Attachments: Metadata only, 30 days

Problem: Using Jira Server URL instead of Cloud
✅ Correct: yourcompany.atlassian.net
❌ Wrong: jira.yourcompany.com
❌ Wrong: yourcompany.com/jira

Solution: Use your Atlassian Cloud URL

Problem: Corporate firewall blocking connection
Symptoms: Connection timeout, "Cannot reach Jira"
Solution: 
1. Contact IT to whitelist api.impulsum.com
2. Ensure OAuth redirects are allowed
3. Test from personal device/network

Problem: OAuth app not configured properly
Symptoms: "OAuth error" o "Invalid client"
Solution:
1. Try disconnecting y reconnecting
2. Clear browser cache y cookies
3. Use incognito/private browsing
4. Contact support if persists

Problem: Multiple Atlassian accounts
Symptoms: "Wrong account connected"
Solution:
1. Log out of all Atlassian accounts
2. Log into correct account first
3. Then connect from Impulsum
4. Verify correct site selected

1. Log into Jira directly
2. Can you see the projects you want to sync?
3. Can you view issues in those projects?
4. Can you see user information?

If NO to any: Contact Jira admin for permissions

Problem: Can't see specific projects
Cause: Not added to project o project is private
Solution: Jira admin adds you to project team

Problem: Some issues missing from sync
Cause: Issue security levels above your access
Solution: Request higher security clearance o accept partial sync

Problem: Team information not syncing
Cause: No "Browse Users" global permission
Solution: Jira admin grants Browse Users permission

Problem: Made changes in Jira 30 minutes ago, not in Impulsum
Diagnosis:
1. Check webhook status: Settings > Integrations > Jira > Webhook Status
2. Manual sync: Click "Sync Now" button
3. Check for errors: Look for red indicators o error messages

Solutions:
├── If webhooks failing: Re-configure webhooks
├── If manual sync works: Webhook issue, contact support  
├── If manual sync fails: Permission o connection issue
└── If partial sync: Data filtering o permission restrictions

Problem: Updates taking too long to appear
Expected: <5 seconds with webhooks, <15 minutes without
Troubleshooting:
1. Verify webhook configuration
2. Check Jira webhook delivery logs
3. Test with simple issue update
4. Monitor sync status dashboard

Problem: Initial sync taking hours
Normal for: 1000+ issues = 10-30 minutes
Concerning if: >1 hour for any size
Solutions:
1. Check network connectivity
2. Verify no rate limiting
3. Consider syncing fewer projects initially
4. Contact support for large datasets (>5000 issues)

Problem: Only some projects o issues syncing
Causes:
├── Project selection settings too restrictive
├── Permission differences between projects
├── Custom filters excluding data
├── Issue security levels
└── Archived o deleted projects

Solution: Review Settings > Integrations > Jira > Sync Configuration

Problem: Project shows wrong status o metrics
Diagnosis:
1. Compare with Jira directly
2. Check last sync time
3. Verify custom field mappings
4. Look for data transformation issues

Common causes:
├── Custom fields not mapped correctly
├── Workflow states not recognized  
├── Time zone differences affecting dates
├── Archived issues included in calculations
└── Permission restrictions affecting data completeness

Problem: Team members not showing o incomplete profiles
Causes:
├── No "Browse Users" permission
├── Users not assigned to synced projects
├── Inactive o deactivated user accounts
├── Privacy settings hiding user information
└── Cross-organization user access issues

Solutions:
1. Verify user permissions in Jira
2. Check project team assignments
3. Confirm users are active
4. Review privacy settings

Problem: Velocity, burndown, o other metrics don't match Jira
Troubleshooting:
1. Check calculation timeframes (sprint dates, etc.)
2. Verify story point field mapping
3. Compare issue inclusion criteria
4. Check for timezone differences
5. Validate custom field data types

Common fixes:
├── Remap story points field correctly
├── Adjust sprint date calculations
├── Exclude archived o invalid issues
├── Standardize estimation practices
└── Update field type mappings

Problem: Some data current, other data stale
Investigation:
1. Check which data types are affected
2. Review sync logs for specific errors
3. Test manual sync for affected areas
4. Verify webhook events are configured correctly

Resolution approach:
├── Identify pattern in stale data (projects, issue types, etc.)
├── Check permissions for affected data
├── Review webhook configuration for those events
├── Manual sync to verify data availability
└── Contact support with specific data examples

Project naming:
✅ Good: PLATFORM-v2, MOBILE-app, API-gateway
❌ Bad: Project1, New thing, Mike's project

Issue naming:
✅ Good: "Implement user authentication API"
❌ Bad: "Fix stuff", "Update thing", "Bug"

Component naming:
✅ Good: Frontend-Dashboard, Backend-API, Mobile-iOS
❌ Bad: FE, BE, App

Recommended workflow states:
├── To Do → Ready for development
├── In Progress → Actively being worked
├── Code Review → Technical validation
├── Testing → QA validation  
├── Done → Completed y deployed

Benefits for AI:
• Better progress tracking
• Accurate bottleneck identification
• Improved velocity calculations
• Clearer team workload analysis

Story Points: Use consistent scale (Fibonacci: 1,2,3,5,8,13)
Business Value: 1-10 scale, documented criteria
Priority: Use Jira defaults, avoid custom priority schemes
Labels: Standardized taxonomy (frontend, backend, bug, enhancement)
Components: Align with team structure y codebase organization

Week 1: PM + 1 senior developer
├── Set up integration
├── Test basic functionality  
├── Identify any issues
└── Document initial learnings

Week 2-3: Add rest of core team
├── Train on basic AI interactions
├── Establish daily usage patterns
├── Collect feedback y iterate
└── Build confidence in insights

Week 4+: Full team adoption
├── Advanced features training
├── Custom dashboard setup
├── Automated reporting
└── Integration with team processes

Essential skills for all team members:
├── How to ask effective questions
├── Understanding AI response context
├── Basic troubleshooting (sync issues, permissions)
├── Data quality best practices
└── Privacy y security awareness

Advanced skills for PMs:
├── Custom field mapping
├── Integration optimizestion
├── Advanced analytics interpretation
├── Cross-tool correlation analysis
└── Team performance coaching using insights

Common objections y responses:

"Another tool to learn":
→ Show how it reduces time in other tools

"AI might replace us":  
→ Demonstrate how it enhances human decision-making

"Data privacy concerns":
→ Explain security measures y data handling policies

"Don't trust AI accuracy":
→ Start with low-stakes questions, build confidence gradually

"Too busy to adopt":
→ Focus on immediate time-saving benefits

Optimal configuration:
├── Real-time webhooks for active projects
├── Daily sync for archived projects
├── Selective field syncing (only what you use)
├── Reasonable historical data limits (6-12 months)
└── Project filtering (exclude irrelevant projects)

Performance monitoring:
├── Sync duration tracking
├── API rate limit monitoring  
├── Error rate analysis
├── Data volume optimizestion
└── User experience metrics

Efficient AI questions:
✅ "How is sprint 24 progressing?" (specific scope)
✅ "What are this week's blockers?" (time-bounded)
✅ "Show me Ana's workload" (person-specific)

Inefficient questions:
❌ "Tell me everything about all projects" (too broad)
❌ "Analyze all historical data" (too much processing)
❌ "What should I do?" (too vague)

Team size impact:
├── <10 people: Standard configuration works well
├── 10-25 people: Consider project-based filtering
├── 25-50 people: Implement role-based data access
├── 50+ people: Enterprise configuration with custom optimizestion
└── Multiple teams: Separate integrations per team/department

Principle of least privilege:
├── Only sync projects team members need access to
├── Use service accounts for organization-wide integrations
├── Regular access reviews (quarterly)
├── Immediate access revocation for departing team members
└── Audit trail monitoring for sensitive projects

Sensitive data handling:
├── Exclude confidential projects from sync
├── Use Jira security levels for sensitive issues
├── Configure data retention policies appropriately
├── Monitor data export y sharing activities
└── Implement data classification standards

Privacy considerations:
├── Team member consent for performance analytics
├── Anonymization of individual metrics when sharing
├── Clear communication about data usage
├── Opt-out mechanisms for personal data
└── Compliance with local privacy regulations (GDPR, etc.)

SOC 2 compliance:
├── Access logging y monitoring
├── Data encryption in transit y at rest
├── Regular security assessments
├── Incident response procedures
└── Vendor security validation

GDPR compliance:
├── Data processing consent management
├── Right to be forgotten implementation
├── Data portability capabilities
├── Privacy impact assessments
└── Data protection officer coordination

Industry-specific:
├── HIPAA (Healthcare): PHI handling procedures
├── SOX (Financial): Audit trail requirements
├── ISO 27001: Information security management
└── Custom compliance: Organization-specific requirements