Sprint planning usually assumes that developers are the ones doing the work.
But what happens when your team starts using AI coding agents?
A sprint could have:
A developer working on architecture
An AI agent implementing a feature
Another agent writing tests
A human reviewing and merging the results
Suddenly, planning isn't just about who has time. It's also about deciding which tasks can be delegated to agents and how humans should review their work.
I've been exploring Sharkly.ai for this kind of workflow. Its Plan feature helps organize project work, while Sprints provide a way to structure that work into focused cycles.
Plan: https://sharkly.ai/features/plan/
Sprints: https://help.sharkly.ai/docs/space/sprints
I think the interesting challenge isn't simply adding AI to sprint planning.
It's figuring out how to plan a sprint when both humans and AI agents are contributors.
Would you assign AI agents specific tasks and deadlines as part of your normal sprint?
Top comments (0)