Many customers I have worked with face delivery challenges: delays, quality issues, or unmet expectations. These problems often appear during delivery but originate much earlier.
In my experience, business are quite reluctant to write lengthy documents and sometimes find it hard to ariculate what they actually need and why it matters. When discussing AI, we often focus on accelerating code generation or automating development and deployment. But what if we start by helping the business formulate goals and expected results so everybody understand the full picture?
To move beyond PowerPoint one-pagers or sketches on napkins, yet avoid massive templates with redundant or irrelevant headings, I decided to try to create a Rovo agent that guides the business to express what truly matters.
And here is how to create a "Initiative Readiness Checker":
To maintain consistency in Confluence, I created a template with specific headings. You can tailor this template to your business needs. This was basically the blank template business used to start with.
I gave the Rovo agent access to all Confluence spaces to be able to retrieve existing information. I also added a specific page with a “Definition of Ready” for Initiatives, specifying what to include under each heading and the DoD for each section.
These skills are needed to create and update pages in Confluence, there might be more but this is what is used rigth now.
Convert page format
Edit page (append content)
Create page
Create label
This describes the mode of the Agent. I am not really sure how it affect it’s performance
You are a benevolent agent who helps the Portfolio and Program Manager define and describe Initiatives so that they are easy to understand for the business and the technical resources that will implement the change.
These are the short suggestions you see when you choose the agent
Create an initiative from a template
Review this document to verify it meets our DoD for initiatives
Identify epics to create from this initiative
I initially only used one standard scenario focusing on high-level initiatives, but in the future I think I will adapt it to handle different scenarios depending on whether the user wants to create Initiatives, Epics, or Stories, as there are slight differences.
Here you create the prompt for the agent. Mine became quite long; below is only the beginning. You must iterate to tailor it to your needs but it is engaging, and you will soon understand how to guide the agent to handle information effectively
You assist users with the following tasks:
A. Create an Initiative.
B. Review an existing Initiative.
We will use "----" to delimit the instructions for each task. The goal of an Initiative document (INT) is to clearly describe the vision and objective of a change so that everyone has a shared understanding of what is to be achieved.
Here is a template for the structure:
👁️🗨️ Vision
🧑🤝🧑Target audience
💕 Needs
🏆Expected outcome
✈️ Strategic goals
🎯Business goals
💰Estimated scope (man-days)
📅Estimated lead time (man-days)
🙋 Epics
Title: INT: [Initiative Name]
I am not a skilled Rovo designer or developer, but after half a day I had created an Agent that works very well. It coaches, challenges, and can suggest improvements to the business owner whenever they get stuck. Either when creating a Initiative from scratch or improving an existing document.
Things that normally took days or weeks to describe and document (if they ever did get finished..) can now be done in a matter of hours with the assitance of the agent and with a much higer level of quality.
Feel free to reach out if you have additional questions, improvements or comments on this project.
Staffan Redelius
0 comments