Our team is moving toward more detailed user stories in Jira. I've had a few colleagues ask why is my human-written content flagged as AI when they run my descriptions through checkers. I am writing these manually during grooming! Is there a way to write Agile docs that don't look like a bot made them?
3 answers
The "As a [user], I want [goal], so that [benefit]" format is highly predictable. Since AI creates content based on probability, it loves this structure. To differentiate your work, focus on the "Acceptance Criteria." Make them very specific to your unique software environment. Use your team's internal shorthand or specific technical debt references. This breaks the pattern of "perfect" English that AI detectors are calibrated to find. It’s ironic that being a disciplined Scrum Master can actually make you look like an AI to these imperfect tools.
Are you using any AI-based grammar checkers to polish the user stories before you finalize them in your project management software?
Try adding more context about the 'why' behind the feature. Deeply logical, multi-step reasoning is often a hallmark of human thought that detectors can sometimes distinguish.
Exactly! Deep context is key. If you link the story to a specific customer feedback session, the nuance usually helps bypass those false AI flags effectively.
I do use a basic browser-based grammar corrector to ensure there are no typos before the sprint planning starts. I didn't think that would be enough to change the signature of my writing, but perhaps it is smoothing out my natural "human" errors too much for the detector's liking.