Best practices for Retrospectives with Jira

[Nataliya.Naydenova]

What are some best practices for conducting sprint/team retrospectives using Jira and/or Confluence?

I want to compare different options and tools and would love to hear from the community.

[Carlos Garcia Navarro]

Hi @Nataliya.Naydenova ,

Welcome to the Community! I personally like Trello to conduct retrospectives. This article has good insights: 

https://medium.com/@redheadjessica/a-step-by-step-guide-to-using-trello-for-team-retrospectives-da327daf7e47

And this is a template:

https://trello.com/templates/engineering/sprint-retrospective-template-trello-hkaQsLWx

[Tenille _ Easy Agile]

Hi @Nataliya.Naydenova 

Tenille here from Easy Agile. We make an app for Jira called Easy Agile TeamRhythm designed to help agile teams to improve their ways of working. We link retrospectives with your work in Jira; you can turn a retro action item into a Jira issue in just a few clicks, which is automatically saved on your backlog so that you refine it when you next refine your backlog and sequence the issue in your next sprint planning ceremony.  

TeamRhythm itself is built around a User Story Map that you can use for planning your work (sprint/version planning, user story mapping, backlog refinement), and retrospective boards that sit side by side.   

If you’d like to check it out, you can jump into our sandbox demo here: https://go.easyagile.com/TRdemo

I’ll also share a retrospective workshop that we ran with Chris Stone (The Virtual Agile Coach) a few months ago that you might find interesting. It’s product agnostic - so not specific to Jira - but Chris has such a wonderful approach to retrospectives. It was a live workshop but we’ve made the recording available on demand: https://www.easyagile.com/events/retrospective-chris-stone/

Good luck with your search; I'm sure you'll get some great responses here.

Please feel free to get in touch if you have any questions.

Cheers

Tenille

[Walter Buggenhout]

Hi @Nataliya.Naydenova and welcome to the Community!

Best practice questions are often a bit difficult to position, definitely when you bring tooling in the picture.

But in this specific case, when comparing Jira to Confluence to manage retrospectives, go with Confluence. Confluence has a ready made template to help you run and document the retro at the same time. You can tweak it to a different format if you would like to run a different style of retrospective.

Most importantly: Jira is designed to define, plan and complete tasks essentially. Once they are done, they intentionally disappear from view so you can focus on the next things that need to be done. That is exactly the opposite of why you would hold a retrospective: to learn lessons that hopefully stick. Confluence, by nature, is a much better fit for that.

"But wait, I want to track tasks we define during a retrospective afterwards", If those require a bit of follow-up, that may indeed be a got time to create issues in Jira for them for further tracking of the required work.

As a bonus, you could use whoteboards or a Trello board to facilitate the retrospective workshop itself. Tools like that allow you to model a canvas to create and organise cards on in a pretty free format. The Atlassian platform lets you embed a lot of external content in Confluence using smart links (i.e. pasting a url to content creates a rich content representation automatically that can often be configured to your liking.

Hope this helps!