Our PMO office is evaluating Is AutoGen the future of enterprise AI agents? for managing Jira tickets and resource allocation. Can we have one agent acting as a Scrum Master and another as a Developer to estimate story points? I’m interested in whether the framework can handle the "human-in-the-loop" requirement for approving budget changes or timeline shifts during the agent conversation.
3 answers
Integrating AutoGen into Project Management is a massive trend for 2024. The "human-in-the-loop" feature is actually a first-class citizen in AutoGen through the human_input_mode setting. You can set it to "ALWAYS" so that before any agent makes a final decision—like moving a Jira ticket to 'Done' or reallocating a budget—it must wait for a human to type "Approved" in the chat. We used this for a marketing launch. The "Scrum Agent" would summarize the day's blockers, and the human PM would just give the thumbs up. it significantly reduces the administrative load on the PM.
Beverly, how do the agents handle conflicting priorities? If the "Developer" agent says a task takes 5 days but the "Scrum" agent says it must be done in 2, how do they resolve that?
We've started using it to automatically generate meeting minutes and update the project roadmap. It saves our PMs about 5 hours a week of pure documentation work.
Gloria, those 5 hours add up to a huge productivity boost across a whole department. For a fast-scaling startup, that's the difference between hitting a milestone and missing it.
Douglas, that’s where the "negotiation" logic comes in. In the system prompt, we give the Scrum agent the final authority on "Scope" and the Developer agent the authority on "Feasibility." They actually "argue" it out in the chat. Usually, they settle on a middle ground, like descoping a feature to meet the deadline. If they can't agree after 3 turns, the framework is set to automatically flag the human PM to intervene. It’s fascinating to watch because it mimics the exact conversations we have in real sprint planning meetings.