Conference50min
We created our own AI orchestrator and it became so much more!
We built an agent orchestration tool using Embabel Agent, Skills, and Spec files to coordinate AI-driven software work. It provides a visual dashboard for active agents, tasks, and next steps, reshaping team roles: developers review AI output, analysts define requirements, and product owners manage faster sprint queues.
talk.summaryAiDisclaimer
Ricky van RijnMetaFactory
talkDetail.whenAndWhere
Friday, October 9, 11:50-12:40
TBA 5
talks.roomOccupancytalks.noOccupancyInfo
Agentic AI is something everyone wants to use or sell. We wanted an overview of the work and active agents and therefore we created an orchestration tool. Using the Agent, Skills and Spec files from default locations so its interchangeable with other tools. And it really started to change the way we worked on software projects.
As a Java software Engineer it could be seen as a automation of tasks, as an Scrum Master/Product Owner a way to coordinate and for the business analyst a way to store functional requirements. We've used Embabel Agent as the fundamental layer. On top of that we've created a visual representation so we can have a website open in our office which shows which agent is active, what it's doing and what's the next task.
For Software Development teams this will be the biggest change, developers are more reviewing and delivering feedback to the AI while business analysts had a field day of delivering the requirements for the spec files which were reviewed by an AI agent before they could be assigned to an AI-agent. The product owner is in control of the queue where sprints are no longer weeks but days.
I want to share how we created this orchestrator and explain on which impact each technical step had on the way-of-work in our team. It wasn't just about creating an application anymore, everything had impact on how we work.
As a Java software Engineer it could be seen as a automation of tasks, as an Scrum Master/Product Owner a way to coordinate and for the business analyst a way to store functional requirements. We've used Embabel Agent as the fundamental layer. On top of that we've created a visual representation so we can have a website open in our office which shows which agent is active, what it's doing and what's the next task.
For Software Development teams this will be the biggest change, developers are more reviewing and delivering feedback to the AI while business analysts had a field day of delivering the requirements for the spec files which were reviewed by an AI agent before they could be assigned to an AI-agent. The product owner is in control of the queue where sprints are no longer weeks but days.
I want to share how we created this orchestrator and explain on which impact each technical step had on the way-of-work in our team. It wasn't just about creating an application anymore, everything had impact on how we work.
Ricky van Rijn
CTO and Software Architect with over 10 years of hands-on java development experience. He is passionate about Software Development, Artificial Intelligence (AI), Robotics, IoT, Cybersecurity, Open Source Software and loves tech gadgets. Ricky is a speaker on conferences like Code&Comedy, DevSecCon, JFall, Devoxx UK and has a background as a lecturer on an University of Applied sciences. Besides all that Ricky is a Fitness and Martial Arts instructor and enthusiast. Current focus is forming and testing new AI best practices.