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 – capture bugs, feature requests or needed research.
Many leading teams have a GitHub workflow to manage backlogs, plan sprints and log issues. As a fully-distributed team building an open-source project, we use GitHub at Parabol to do just this – check out our backlog.
Avoid managing multiple tools or relying on notes in another tool – create GitHub issues during your sprint retro so they’re ready to be prioritized for an upcoming sprint. Send any card in any view – during a meeting or from your Dashboard – to GitHub.
If you’re managing multiple repositories, you can select the right one when publishing an issue. This works for both private and public repositories.
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 task card in Parabol, press shift + enter to break a line and start the description.
Once you migrate the card from Parabol to GitHub, it’ll be read-only. This means changes can only be made in GitHub, 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 GitHub, and click through to see what progress you’ve made since your last meeting.
GitHub lets agile teams manage their code, 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 into your GitHub Issue backlog. Make retrospectives a natural part of your GitHub workflow.