PlannerPoker Blog

Practical agile planning for modern product teams

Guides on planning poker, Jira-connected estimation, remote refinement, and using AI without losing the team conversation.

A neural network diagram representing AI coding dependence in sprint planning
5/30/20267 min readFeatured

AI Coding Dependence Is Now an Estimation Risk

Developers are leaning hard on AI coding tools, but AI-generated code still needs review. Here is how sprint planning and planning poker should respond.

Latest posts

5/30/2026

Agentic Infrastructure Changes Sprint Estimation

AWS, Google, and cloud platforms are redesigning infrastructure for AI agent traffic. Product teams should estimate bursty workloads, permissions, memory, and cost before they ship agent features.

5/29/2026

AI Coding Agents Are Changing Sprint Planning in 2026

Enterprise coding agents are moving from autocomplete into real delivery workflows. Here is how agile teams should adjust estimation, planning poker, and Jira habits.

5/29/2026

Spec-Driven Development Makes Planning Poker More Important

AWS Kiro and the wider spec-driven development trend show why better requirements, clearer estimates, and human review matter when AI agents build software.

5/21/2026

Jira Story Points: A Practical Guide to Better Agile Estimation

How to use Jira story points, planning poker, and velocity reports without turning estimation into a pressure metric for product teams.

5/18/2026

Planning Poker in 2026: A Practical Guide for AI-Assisted Agile Teams

How remote product teams can use planning poker, Jira, and AI suggestions without losing the conversation that makes estimates useful.

4/21/2025

Scrum Today: What Still Works, What Needs to Change

Scrum still works when teams use it as a lightweight operating system for clarity, learning, and delivery, not as a calendar full of status meetings.

4/21/2025

AI Estimation: A Practical Way to Use AI Without Losing Team Judgement

AI can make agile estimation faster by preparing context and surfacing risks, but the final estimate still needs the team conversation.