Parabol lets engineering teams hold engaging retrospective meetings through anonymous reflections, multi-player grouping and voting, and guided discussions. Choose from retrospective templates based on best practices or customize your own to suit your team’s needs.
During your guided discussion, collaboratively decide on next steps and log issues directly in Parabol.
Many leading teams use JIRA to manage backlogs, plan sprints and log issues.
Avoid managing multiple tools or relying on notes in another tool – send issues from Parabol directly to your backlog in JIRA during your sprint retro. These issues are now ready to be prioritized for an upcoming sprint.
If you’re managing multiple projects or backlogs, you can quickly select the target JIRA project before sending the task over.
You can also include additional details on the issue. By default, the first line of your Parabol card will be the title of the issue. On the Parabol task card, press shift + enter to break the line and start entering the JIRA ticket description.
Once you migrate the card from Parabol to JIRA, it’ll be read-only. This means changes can only be made in JIRA, sidestepping the problem of different changes in different tools.
In future retrospective or team check-in meetings, you can see which tasks are managed in JIRA, and click through to see what progress you’ve made since your last meeting.
Atlassian’s JIRA is the industry leader in developer tools for agile teams, but doesn’t provide tools to run retrospectives – a critical component of a healthy team and continuous improvement.
With Parabol, you can raise the bar for sprint retros and also bring your new powerful insights to your JIRA workflow. Run a JIRA retrospective without relying on JIRA for your meeting.