Better Requirements. Better AI.

Think of this book as a farmer's almanac for working Scrum teams-a practical guide you can return to when the work gets messy.

I've been the business analyst, Scrum Master, project manager, manager, and executive. I've planted the seeds and dug up the potatoes. This book brings together what I've learned along the way.

Inside, I show how to:

• Develop clear stories and acceptance criteria through conversation with an AI assistant.
• Bring meeting records and supporting information into the requirements process before moving work into Jira.
• Give developers requirements and supporting material they can use with their chosen tools.
• Refine the backlog, plan realistic Sprints, and manage dependencies and unplanned work.
• Use estimates and reporting to explain what the team delivered, what changed, and what still needs attention.

A worked Account Access example connects the guidance to stories, wireframes, acceptance criteria, and the team's Definition of Done. Recommendations that go beyond the Scrum Guide are identified as Field Insights.

Written for business analysts, Product Owners, Scrum Masters, and the teams they support, Better Requirements. Better AI. explains what I recommend, why it matters, and how to apply it.

The goal is straightforward: help your team understand the work, plan it realistically, and deliver what customers are counting on.