Prepare for sprint planning with Rovo's readiness checker agent

10 min

By the end of this lesson, you’ll be able to:

  • Use the readiness checker Rovo agent to assess ticket readiness automatically
  • Streamline sprint planning by ensuring only actionable tickets are included
  • Improve team efficiency and reduce sprint disruptions

Use Rovo to prepare for sprint planning

👉 Our scenario: Sally is a product owner preparing for sprint planning with the development team working on Project Phoenix, an innovative mobile application aimed at enhancing user engagement for small businesses. Sally uses the Rovo readiness checker agent to automate this process. It reviews Jira work items against your team’s “definition of ready,” checking for required fields, clear descriptions, acceptance criteria, estimates, and relevant links. The agent provides a readiness score and actionable feedback, helping teams focus only on tickets that are truly ready for development.
👇 Click the boxes below to explore how Sally prepares the backlog for sprint planning.

Use the readiness checker to report on multiple work items

The readiness checker agent can also be used to assess multiple work items at once, making it ideal for large backlogs or teams with high ticket volume.
Sally could run the readiness checker agent for a group of work items using Jira automation. She will need to configure an automation rule that calls for the readiness checker agent.
To configure an automation rule:
  1. Sally creates a radio button custom field called Readiness score. It has the following values:
    🟢 Pass
    🟡 Warnings
    🔴 Fail
  2. Sally goes to the team’s Jira project settings, then in the sidebar, selects Automation.
  3. She selects Create rule to start a new automation rule.
  4. She sets the trigger to Scheduled and configures it to run every two weeks at 9 AM, which is before every sprint.
  5. She adds a branch rule and sets the Type to JQL. In the JQL field, she adds the following JQL query: project=PLAT and status=To Do
    This means the automation will run through each work item returned by the JQL query.
  6. Sally adds the Use Rovo Agent action and sets the prompt to:
    Review this Jira work item {{issue}} and return a readiness score: Pass, Warnings, or Fail.
    Only return one of the following options:
    🟢 Pass
    🟡 Warnings
    🔴 Fail
    The {{issue}} smart value returns the current work item that the automation is going through.
  7. She adds the Edit work item action and sets the value of the Readiness Score custom field to {{agentResponse}}. The smart value {{agentResponse}} is the readiness checker agent’s response, which should be either Pass, Warnings, or Fail.
👇 This is what the automation should look like for Sally.
A screenshot of an automation rule in the Platform Development project titled Run Readiness Checker for open work items. The automation rule runs as follows When work item transitions to Ready for development, and JQL is project=PLAT and status To Do, then use Rovo readiness checker and edit work items field.
8. Sally saves the automation rule and runs a test to ensure it works as expected. She uses the work item navigator to check that the automation is updating the Readiness Score custom field.
👇 Sally checks if the automation rule runs successfully.
A screenshot of All work page in Jira. The JQL Project=PLAT and status = To Do is written in the JQL field and the results from the JQL show the automation rule ran successfully.
How was this lesson?

Community

FAQsForums guidelines
Copyright © 2025 Atlassian
Report a problemPrivacy PolicyNotice at CollectionTermsSecurityAbout