How should AI-generated project tasks be reviewed and tracked?

1 hour 41 minutes ago
Avatar

One thing I'm curious about with AI-assisted project management is what happens after the AI generates the initial work items.

For example, an AI could take a requirement and generate:

  • User stories
  • Development tasks
  • Test cases
  • Risks
  • BDD scenarios

But generating these artifacts is only the first step. The more difficult part is keeping them connected and making sure the team can see what was generated, what was modified by a human, and what has actually been completed.

I'd be interested in a workflow where AI handles the initial decomposition, while the team validates the output and maintains traceability throughout development and testing.

This is also why I'm interested in platforms like Sharkly, where AI agents can participate in project workflows alongside human teammates rather than operating separately.

https://sharkly.ai/

For those using SpiraTeam, how are you currently reviewing and tracking AI-generated tasks or requirements?

Do you prefer AI to generate the initial work items only, or would you trust it to keep them updated throughout the project?

1 Replies
37 minutes ago
Avatar
re: Lucdev01234 1 hour 41 minutes ago

Hello,

The trust model I'd recommend: AI generates, humans promote. An AI-created item stays in a "draft" or "pending review" status until a human explicitly approves it.

Updates proposed by AI go back into draft. That way the team always owns what's in the active workflow.

 

 

Regards,
Victoria -

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: 1 hour 41 minutes ago
  • Last Reply: 37 minutes ago
  • Replies: 1
  • Views: 9