I note that AI products require additional clarity around: expected behavior, data needs, quality evaluation, hallucination handling, and safety considerations.
A Jira ticket can be marked “Ready” and still not be ready for development.
I noticed that Jira tickets marked “Ready” often still lack the shared understanding needed for developers to start work, especially when requirements flow quickly from Slack to Jira to Sprint.
- I split responsibility for ticket readiness:
- I adopted a “Ready for Development” checklist that must be satisfied before a ticket is considered Ready:
✅ Clear user story – I always make sure the story is explicitly written and validated before the sprint starts.
- Clear user story
- Acceptance criteria defined
- Designs/API requirements available
- Dependencies identified
- Edge cases discussed
- QA expectations clear
- Story small enough for the sprint
- Team understands what “Done” means
- PM defines problem, user, success criteria, acceptance criteria, dependencies, and edge cases.
- Scrum Master ensures team alignment, visibility of blockers, proper refinement discussion, story sizing, and protects the team from scope creep.