/ webinar /
How to Improve Code Quality: Your Jira Tickets Are Killing It
How to catch and fix bad requirements before they become expensive rework — with Allstacks' Jeff Keyes and Jim Grundner on why requirements are the real bottleneck in AI-assisted development.
Thank you!
About the author
Jeff Keyes is Field CTO and Product Leader at Allstacks, reshaping product management for the agentic era with 30+ years of building at companies like Microsoft, Atlassian, and Kaseya.
The biggest frustration of software engineers is now the most critical bottleneck in AI-assisted and agentic development. AI coding tools build directly from bad requirements — ambiguity and all — and the result is more rework.
Jeff Keyes, Field CTO and Product Leader, and Jim Grundner, Head of Engineering at Allstacks, share personal examples of the impact of AI coding, bad requirements, and what you can do to fix it.
What you'll learn
- Why bad requirements are the biggest bottleneck in development, and how to improve them
- What a new quality lens for requirements looks like as AI codes and humans shift to design and validation
- How early-adopting engineering teams are structuring their approach to requirements quality
- What an automated requirements evaluation on real Jira data looks like, from scoring to gap detection to ready-to-push fixes