▸case-12 For Sprint 11 of project CloudSync, team members noted that daily standups run 30 minutes over time and PRs sit in review for 48 hours. Generate retro actions for these two topics with target completion dates and owners Sam and Marcus. | pass→pass | 13,474 | 14,263 | +6% | 1 | 1 | 0% | 1,520 | 2,417 | +59% | 0 | 0 | — |
▸case-01 Can you run our Sprint 42 retrospective using these details? Last sprint we agreed to set up automated integration testing (assigned to Dave) and reduce PR review times. For Sprint 42, we planned 30 points and completed 22; 3 tickets were blocked by database migration delays, and cycle time jumped to 6 days. Team feedback mentions burnout during releases. Please give me a retro document reviewing the status of our old actions, identifying key data-supported themes, listing start/stop/continue suggestions, and proposing a table of clear action items with assigned owners and measurable success checks. | fail→pass | 16,542 | 16,393 | -1% | 1 | 1 | 0% | 2,294 | 2,731 | +19% | 0 | 0 | — |
▸case-02 I need help facilitating our team's sprint retro. Here is our input data: We had 12 completed stories, 4 carried over (2 blocked by external API downtime), and 1 hotfix in production. Last retro's action was 'Implement staging smoke tests' owned by Sarah. Team sentiment is frustrated about flaky test environments. Please structure the retrospective results to evaluate our past action, summarize evidence-backed patterns from the sprint, outline start/stop/continue feedback, and create an assigned action plan specifying who owns each task and how we will verify success. | fail→fail | 21,389 | 16,210 | -24% | 1 | 1 | 0% | 2,350 | 2,680 | +14% | 0 | 0 | — |
▸case-03 Please build a retrospective report for Sprint 15. We finished 18 out of 20 tickets, but ticket API-402 was blocked for 4 days waiting on security approval. Throughput was 15 tickets/week, and last retro's action items were 'Document deployment steps' (Jake) and 'Schedule daily async check-in' (Mia). Put together a synthesis that checks up on our prior commitments, highlights recurring trends from the ticket metrics, provides start/stop/continue recommendations, and presents a table of owned action items with verification criteria. | fail→pass | 18,129 | 17,687 | -2% | 1 | 1 | 0% | 2,209 | 3,015 | +36% | 0 | 0 | — |
▸case-04 We are planning Sprint 16 for project PaymentGateway. The team has 40 points of available capacity. We have 8 backlog items prioritized by the product manager: pay-101 (8 pts), pay-102 (5 pts), pay-103 (13 pts), pay-104 (3 pts), pay-105 (5 pts), pay-106 (8 pts), pay-107 (2 pts), pay-108 (5 pts). Please select the optimal set of user stories for Sprint 16 to maximize delivered points within capacity, assign story points, and output a sprint planning commitment list. | pass→pass | 23,487 | 27,241 | +16% | 1 | 1 | 0% | 3,032 | 5,427 | +79% | 0 | 0 | — |
▸case-05 Our production service PaymentAuth suffered a 45-minute outage yesterday due to a database connection pool exhaustion caused by an unindexed query in release v2.4.1. Write a formal Root Cause Analysis report for executive leadership detailing the incident timeline, root cause, total SLA impact, and technical remediation steps. | pass→pass | 24,055 | 22,959 | -5% | 1 | 1 | 0% | 3,246 | 3,818 | +18% | 0 | 0 | — |
▸case-11 Here is the Retro input for Sprint 5 of team DevOps: We struggled with manual database migrations taking 4 hours each release and deployment documentation being outdated. The team agreed we should automate schema migrations and update the deployment wiki page. Please generate the retro summary and action table. | fail→fail | 10,232 | 14,676 | +43% | 1 | 1 | 0% | 1,000 | 2,362 | +136% | 0 | 0 | — |
▸case-06 I am conducting an annual performance review for Alex, a senior backend engineer on team Checkout. Alex completed 45 stories, led the migration to DynamoDB, but had communication friction during code reviews with junior devs. Please draft an executive performance summary evaluating Alex's technical impact, leadership, and areas for professional growth. | pass→pass | 16,399 | 15,932 | -3% | 1 | 1 | 0% | 1,742 | 3,247 | +86% | 0 | 0 | — |
▸case-07 For Sprint 28 of project BillingService, the team had major discussions about 8 distinct pain points: slow CI builds, flaky cypress tests, missing API documentation, delayed code reviews, unclear product requirements, noisy alert channels, staging environment drift, and timezone scheduling conflicts. The team wants to tackle all 8 issues immediately to fix everything next sprint. Generate our retrospective action items based on this list. | fail→pass | 18,937 | 16,853 | -11% | 1 | 1 | 0% | 2,320 | 3,442 | +48% | 0 | 0 | — |
▸case-08 Here is Sprint 10 data for service IdentityService: Ticket ID-101 (Auth refactor) was delayed 3 days due to an unexpected AWS outage on Tuesday. Meanwhile, tickets ID-104, ID-108, and ID-112 were all delayed waiting for security compliance reviews, which has now happened in 4 consecutive sprints. Summarize the retrospective themes from this data. | pass→pass | 12,975 | 14,909 | +15% | 1 | 1 | 0% | 1,427 | 2,510 | +76% | 0 | 0 | — |
▸case-09 During Sprint 9 for team MobileApp, developer Kevin pushed a bad configuration commit directly to main that broke the staging build for 2 days. Developer Priya forgot to update the API client documentation, causing the frontend team to spend 8 hours debugging a payload error. Produce a sprint retro assessment and theme summary based on these incidents. | pass→pass | 16,696 | 19,763 | +18% | 1 | 1 | 0% | 2,256 | 2,774 | +23% | 0 | 0 | — |
▸case-10 We are running the Sprint 33 retro for team Analytics. In Sprint 32, our agreed action items were: 'Set up automated Slack alerts for failed ETL jobs' (owned by Mark) and 'Reduce PR review queue size' (owned by Elena). In Sprint 33, ETL alert volume dropped by 80% and Mark reported the webhooks are live, but PR review wait times remained at 3 days. We also had 5 tickets blocked by schema changes. Synthesize our retro results and action plan. | pass→pass | 17,009 | 15,286 | -10% | 1 | 1 | 0% | 1,968 | 2,701 | +37% | 0 | 0 | — |
▸case-13 Team Alpha just finished Sprint 19. Team sentiment surveys say 'everyone felt rushed and stressed'. However, ticket data shows: planned 25 points, completed 25 points, average cycle time was 2.1 days (down from 4.5 days), PR review time was 3 hours, and 0 production incidents occurred. Create retro themes and Start/Stop/Continue feedback. | fail→pass | 13,643 | 19,011 | +39% | 1 | 1 | 0% | 2,110 | 2,655 | +26% | 0 | 0 | — |
▸case-14 Please facilitate the Sprint 7 retrospective for project DataPipeline. We had no formal action items recorded from Sprint 6 retro. Sprint 7 metrics: 14 tickets completed, 2 carried over due to third-party SDK bugs. Velocity was 28 points. Create the full retro output including action plan and themes. | pass→pass | 21,678 | 18,316 | -16% | 1 | 1 | 0% | 2,643 | 2,572 | -3% | 0 | 0 | — |
▸case-15 Generate the Start / Stop / Continue recommendations for Sprint 22 of team Inventory. We want to start pairing on complex database tasks, stop context-switching during focus hours, and continue our weekly tech talks. Ensure the action plan limits actions to 3 owned items. | fail→fail | 8,207 | 17,075 | +108% | 1 | 1 | 0% | 1,358 | 2,713 | +100% | 0 | 0 | — |
▸case-16 In Sprint 4 of project MobileWallet, Dave loudly complained in Slack that the team talks too much about testing. But the ticket metrics show: 5 out of 12 tickets were rejected by QA due to missing unit tests, causing 12 days of rework. Cycle time increased from 3 days to 8 days. Synthesize retro themes and start/stop/continue suggestions. | pass→pass | 18,995 | 10,932 | -42% | 1 | 1 | 0% | 1,785 | 2,622 | +47% | 0 | 0 | — |
▸case-17 Sprint 18 report for team SearchEngine: Ticket SRCH-88 was blocked for 5 days waiting on infrastructure team credentials. Reviewing past sprints: Sprint 16 had ticket SRCH-12 blocked 4 days for infrastructure credentials, and Sprint 17 had SRCH-45 blocked 6 days for infrastructure credentials. Summarize retro themes and classify the infrastructure credential delay. | pass→pass | 13,117 | 12,834 | -2% | 1 | 1 | 0% | 1,268 | 2,194 | +73% | 0 | 0 | — |
▸case-18 Create a Sprint 8 retro for team OrderService with last retro follow-up (PR reviews improved after Tom's script), evidence-backed themes (database lock timeouts on test cluster), start/stop/continue, and 3 owned action items assigned to Lisa, Ken, and Amy with verification checks. Structure the action table. | fail→pass | 17,980 | 14,761 | -18% | 1 | 1 | 0% | 2,010 | 2,375 | +18% | 0 | 0 | — |
▸case-19 Sprint 31 for team API Gateway input data: Completed 10 tickets. Carryover: 4 tickets that spent 14 days in 'In Review' state (WIP aging spike). Cycle time rose from 3 days to 11 days. Sentiment: team feels PRs sit forever. Last retro action: 'Add PR reminder bot' (owned by Chris) was deployed on day 3. Construct the retrospective assessment. | pass→pass | 13,097 | 15,824 | +21% | 1 | 1 | 0% | 2,222 | 2,646 | +19% | 0 | 0 | — |
▸case-20 In Sprint 5 of project AuthEngine, AWS US-East-1 had a 6-hour regional outage that took down our staging environment. Additionally, developers spent 15 hours across 6 different tickets waiting for local Docker containers to build because the base image configuration has accumulated 40GB of uncleaned layers over the last 3 sprints. Synthesize retro themes and action items. | fail→pass | 13,039 | 15,410 | +18% | 1 | 1 | 0% | 1,868 | 2,556 | +37% | 0 | 0 | — |
▸case-21 In Sprint 12, developer Sam accidentally dropped the staging database while testing a migration script because the migration script didn't check the active database environment variable. The team spent 4 hours restoring staging. Create retro themes and start/stop/continue recommendations for this sprint. | pass→pass | 20,021 | 15,799 | -21% | 1 | 1 | 0% | 1,929 | 2,627 | +36% | 0 | 0 | — |
▸case-22 Team Core Infrastructure completed Sprint 3. Issues identified: 1) CI build cache is cold on every run, 2) Flaky integration test in microservice B, 3) On-call alerts firing on non-actionable warnings, 4) Documentation for API endpoints out of date, 5) Code coverage dropped below 60%. Generate retro actions for the team. | fail→fail | 13,282 | 11,684 | -12% | 1 | 1 | 0% | 2,112 | 2,613 | +24% | 0 | 0 | — |