🤖 AI + Agile: A Test Engineer's Take on AI in Quarterly Planning & Retros

[Anwesha Pan]

Hi everyone! 👋

I'm a Dev/Test Engineer on a Kanban team working on a large-scale insurance platform. Here's what I'm seeing AI do for our Agile ceremonies — from the quality trenches.

---

📋 Quarterly Planning

We run Kanban — no sprints, no velocity charts, no two-week commitments. Instead, we plan on a quarterly cadence, setting priorities, capacity expectations, and key deliverables for the next 12 weeks.

• Throughput forecasting — AI analyzes our historical cycle time and throughput to generate probabilistic forecasts ("85% chance you'll deliver 45–55 items this quarter") instead of gut-feel guesses.

• Risk flagging — AI scans upcoming epics and warns us: "This area historically produces 40% more hotfixes." As a tester, that's gold for planning test effort upfront.

• Bottleneck prediction — AI spots where work will pile up before it happens, helping us set smarter WIP limits.

The tester's pain point AI solves: Test complexity is finally visible in planning — not just dev effort.

---

🔄 Retrospectives

Kanban retros can feel vague without sprint boundaries. AI helps by:

• Correlating retro themes with flow data — "When the team flagged 'unclear requirements,' cycle time jumped 40% and escaped defects doubled." That's the evidence testers need to push for better refinement.

• Surfacing hidden blockers — "Items spend 4.2 days stuck in 'Waiting for Test Environment' — up 60% from last quarter." Turns vague complaints into actionable problems.

• Generating targeted prompts — Instead of "What went well?", AI asks: "7 items reopened last month — what's driving the rework?"

---

💬 Over to You!

• Are you using AI in your planning or retros? What's working?

• Kanban teams — has AI changed how you manage flow?

• What's one thing you'd never want AI to touch?

Let's hear it! 👇