A bot that turns Teams meetings into reviewed DevOps backlogs
This AI project management bot case study covers an IT and software delivery organisation that runs sprint-based projects on Microsoft Teams and Azure DevOps. Meeting notes, task allocation and sprint tracking were manual, which caused delays and inconsistencies. We built a bot that joins Teams meetings, an AI agent that extracts tasks from the transcript, and a manager review step before anything reaches Azure DevOps. The MVP is delivered and Phase 1 is implemented.
| Before | With the agent | |
|---|---|---|
| Meeting notes | Captured by hand, which caused delays and inconsistencies | A bot joins the Teams meeting and captures the recording and transcript |
| Task extraction | Someone read the notes and wrote up the tasks | An AI agent pulls objectives and tasks from the transcript |
| Backlog creation | Epics, stories and tasks entered manually | Draft Epics, User Stories and Tasks are generated for Azure DevOps |
| Task assignment | Allocated by hand | Tasks go to the right team and developers, using story points and sprint capacity |
| Sprint visibility | Managers lacked real-time visibility into velocity and pending tasks | Power BI dashboards show velocity, progress trends and pending tasks |
| Control | Manager did everything | Manager reviews, edits or deletes tasks before approval |
The agent drafts. The manager decides. Nothing lands in Azure DevOps until the manager approves it.
Epics, User Stories and Tasks are drafted from the meeting transcript and placed in the nearest sprint once approved. Only tasks from that meeting are added.
Tasks are matched to the right team and assigned using Fibonacci story points and available sprint capacity.
Power BI dashboards cover velocity, progress trends and pending tasks, and email reminders go out for incomplete tasks.
Tasks can be reviewed, edited or deleted in the Manager Review Portal. Azure DevOps only gets approved work.
An Azure AD app with an Application Access Policy and the Microsoft Graph API control access to Teams data.
Teams, Azure DevOps, Azure AI and Power BI are connected, so the team keeps its existing way of working.
No. The status is MVP completed, with Phase 1 implemented.
No. Generated tasks are emailed to the manager with a portal link. The manager reviews, edits or deletes them, and approved tasks are then created in Azure DevOps.
A bot joins the Teams meeting through a dedicated service account. Recordings and transcripts are captured with Power Automate and the Fireflies.ai API and stored in a SQL database.
Tasks are matched to the right team (Backend, Frontend, QA, Designer, Project Manager). Developers are then chosen using Fibonacci story points and available sprint capacity. The sprint rule, Sprint 1 as day 1-15 and Sprint 2 as day 16 to month end, is specific to this setup.
Tell us how your team plans sprints today. We'll show you where an agent can draft the work and your manager still approves it.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
Talk to a QServices solutions architect about your ERP. You'll leave with two or three automation ideas you can act on, even if you never work with us.