AI in Agile Delivery: Sprints, Retrospectives, and Velocity

Help me prepare for sprint planning for Sprint 4 of the
AP automation project.

Context:
- Sprint 1-3 velocity: 34, 31, 37 story points (avg: 34)
- Team capacity this sprint: 90% (one developer has 1 day off)
- Expected available capacity: ~30 points
- Sprint goal: Complete all invoice matching backend logic and
  begin approval workflow UI

Backlog items available (with point estimates): [paste backlog]

Help me:
1. Select the stories that best fit the sprint goal
   within the 30-point capacity constraint
2. Identify any dependencies between selected stories
3. Identify any stories that are too large for one sprint
   (should be split before being taken in)
4. Draft the sprint goal statement (1-2 sentences)
5. Flag stories with unclear acceptance criteria that
   should be refined before sprint start

Generate a retrospective facilitation guide for Sprint 4 of
the AP automation project.

Context: [paste sprint 4 events — what happened, what went well, issues]

Format: Start-Stop-Continue retrospective

Include:
1. A 5-minute warm-up activity to get the team talking honestly
2. Guided questions for each category (Start/Stop/Continue)
   tailored to the sprint events you know about
3. A prioritization exercise to identify the top 2 action items
4. A format for capturing action items (owner, what, by when)

After the retrospective, given these notes: [paste retro notes]
Convert to:
- Summary of items in each category
- Top 3 insights from the discussion
- Action items with owners and due dates
- One-paragraph team morale read (based on what the team said)

Here is our sprint velocity data for the last 8 sprints:
[paste: sprint number, capacity, planned points, delivered points]

Analyze:
1. Average and trend in velocity (improving, declining, stable)
2. Planned vs. delivered ratio — are we consistently over- or under-committing?
3. Sprints with significant variance — what factors contributed?
4. Realistic velocity forecast for the next 4 sprints
5. Based on remaining backlog estimate ([X] points) and current velocity,
   what is the projected delivery date?
6. What changes to our planning process would improve predictability?

Here are the user stories in our backlog for refinement: [paste]

For each story:
1. Clarity: Is the story clear enough for a developer to estimate?
   Flag any stories that need more detail.
2. Size: Are any stories too large to complete in one sprint?
   Suggest splits for stories over 8 points.
3. Dependencies: Do any stories have unresolved dependencies
   that must be addressed before they can be started?
4. Acceptance criteria completeness: Are the criteria specific
   and testable? Flag any that need improvement.
5. Priority ordering: Given the sprint goal of [goal], rank
   the top 5 stories that should be prioritized.

Convert these sprint 4 technical completion notes into a
stakeholder-facing sprint review summary:

Technical notes: [paste — stories completed, bugs fixed, technical decisions]

Audience: Business stakeholders (CFO's office, Finance Director's team)
who don't understand technical details but care about progress.

Format:
- What can users do now that they couldn't before?
- What business problem does the work completed this sprint address?
- What is being demonstrated at the sprint review?
- What is planned for the next sprint and how does it advance
  the overall project goal?

No technical terminology. Business outcomes only.

Here are the currently blocked items in our sprint: [paste]

For each blocked item:
1. Root cause of the block (what must happen to unblock)
2. Who has the ability to unblock this item
3. What the PM should do to accelerate resolution
4. What the cost of waiting another week is
   (in schedule impact and team productivity)
5. Decision: escalate to steering committee / resolve at PM level /
   accept and re-plan around

Prioritize by schedule impact.