I want someone to help me in creating Rovo Agent for below
Sprint Velocity forecast
Sprint Retrospective
Daily scrum update team wise
Please help 🙏
@Anuj Batta I would encourage you to take a class from Atlassian Learning to understand more about Rovo. But to respond to your post:
You can do this with one agent that asks 2 questions first: “Which team?” and “Which meeting: Forecast / Retro / Daily?” Then it filters issues using your team signal (labels/components/team field) + current sprint. Forecast: summarize last 3 sprints’ completed story points + risks. Retro: wins, blockers, themes. Daily: today/next/blockers + stale issues. Here’s a clean starter set you can paste into Agent Instructions:
“Before running, always ask which team and which meeting type (Sprint Velocity Forecast, Sprint Retrospective, or Daily Scrum). Use team identifiers (labels, components, team field, or sprint name) to filter issues.
• Velocity Forecast: analyze last 2–3 completed sprints and forecast capacity and risks.
• Retrospective: summarize wins, blockers, patterns, and improvement areas from the last sprint.
• Daily Scrum: list today’s focus, blockers, carryover work, and stale issues for the selected team only.”
Thanks for your response
Could you please help me to send what Rovo instructions to write so that it behaves correct way I am unable to do
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In addition to @Jorge Cammarotaexcellent advice, you can use https://www.promptcowboy.ai/ to help construct agent prompts (make sure to select the relevant option) - it'll then nudge you to consider any other ideas or questions you should answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rovo Agent – Daily Scrum Update (team-wise)
Objective
Generate a daily summary per team.
Required Data
Issues in progress
Status per assignee
Blockages
Step-by-step
Create agent
Name: Daily Scrum Team Update
Sources
Jira Project
Issues in progress
Base prompt
Generate a daily summary per team.
For each member:
- What is in progress
- What has been completed since yesterday
- Blockages identified Organize by team.
Typical use
Asynchronous daily update
Update for managers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
do i need to paste in instructions
Also do i need to provide data manuall
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rovo Agent – Sprint Retrospective
Objective
Generate automatic insights for the retrospective.
Required Data
Sprint Issues
Status, reopenings, blocks
Comments (optional)
Step-by-step
Create new agent
Name: Sprint Retrospective Assistant
Sources
Sprint Issues
Transition history
Base prompt
Analyze the completed sprint.
Identify:
- What worked well
- Bottlenecks
- Blocked or reopened issues
- Suggestions for improvement Organize in an agile retrospective format.
Expected Result
Ready-to-paste text for the retrospective
Objective and actionable points
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How to solve: creating Rovo Agents for Scrum (step-by-step)
Overview
You don't create a single agent for everything. The correct approach is 1 agent per responsibility, with well-defined data sources.
In this case, there are 3 distinct agents.
Rovo Agent – Sprint Velocity Forecast
Objective
Predict the velocity of the next sprint based on historical data.
Required Data
Jira Software
Completed Sprints
Completed Story Points
Step-by-step
Go to Atlassian Intelligence → Rovo → Agents
Click on Create Agent
Configure:
Name: Sprint Velocity Forecast
Description: Analyzes previous sprints and predicts the velocity of the next one
Data Sources
Jira Project
Scrum Board
Completed Sprints
Base prompt for the agent
Analyze the last 5 completed sprints.
Calculate the average number of story points delivered.
Consider variations and trends.
Return a velocity forecast for the next sprint.
Test with questions:
“What is the predicted velocity for the next sprint?”
“What was the average for the last 5 sprints?”
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.