#planning-poker
Microsoft Build 2026 Shows Why AI Agents Need Better Sprint Planning
Sun May 31 2026
Microsoft Build 2026 is putting agentic AI, GitHub Copilot, MCP, and safety tooling at the center of developer work. Here is how agile teams should estimate agent work before it reaches production.
AI Coding Dependence Is Now an Estimation Risk
Sat May 30 2026
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.
Agentic Infrastructure Changes Sprint Estimation
Sat May 30 2026
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.
AI Coding Agents Are Changing Sprint Planning in 2026
Fri May 29 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.
Spec-Driven Development Makes Planning Poker More Important
Fri May 29 2026
AWS Kiro and the wider spec-driven development trend show why better requirements, clearer estimates, and human review matter when AI agents build software.
Jira Story Points: A Practical Guide to Better Agile Estimation
Thu May 21 2026
How to use Jira story points, planning poker, and velocity reports without turning estimation into a pressure metric for product teams.
Planning Poker in 2026: A Practical Guide for AI-Assisted Agile Teams
Mon May 18 2026
How remote product teams can use planning poker, Jira, and AI suggestions without losing the conversation that makes estimates useful.
Scrum Today: What Still Works, What Needs to Change
Mon Apr 21 2025
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.
AI Estimation: A Practical Way to Use AI Without Losing Team Judgement
Mon Apr 21 2025
AI can make agile estimation faster by preparing context and surfacing risks, but the final estimate still needs the team conversation.