Efficient Agile Retrospectives with improved follow up on action items.

SoftwareDevTools has some huge news for you! We have just released a new feature to create Jira tasks from your resulting Retrospectives action items in our app: Agile Retrospectives for Jira and for Confluence!! Because you asked for it, we deliver! Read on to learn more:

Software Development teams that are very large, or that are working distributed usually have a hard time with Agile ceremonies. We can tell asynchronous teams have struggled the most to really perceive the value of Agile methodologies. This is due to several factors:

  • Lack of visibility of the results.
  • Lack of engagement.
  • No follow-up on the results.

When we first built Agile Retrospectives for Confluence and then worked on Agile Retrospectives for Jira we decided to create the ultimate tool to improve these three factors:

  • Visibility: A collaborative retrospective that allows for real-time collaboration. No more taking turns results in a lot of time saved (Translation: Money $$$). Collaborative Voting in Agile Retrospectives Also, Everyone has access to the session's results at any time so they can go back and check the results of previous sessions to confirm their status.
    Historic results in Jira

  • Engagement: An interactive tool, with a beautiful UI. Custom templates to use your favorite Retro technique, collaborative voting and real-time assignment of action items generate a lot of engagement from the team.

Custom Retros sessions

  • Follow-up: This is a tricky one. We thought creating action items in our app would make it easy for the team to follow up on the results of the Retrospective session. But that is not enough. The app is only used once every sprint and the team is never back on it. Here's how it looked:
    So, how to make the action items visible and guarantee a follow-up?
    Simple answer: Create Jira tasks!

This is a new feature on our tool: Turn resulting action items from your Agile Retrospectives into Jira tasks to assign to each team member and include them on your sprint!!
This is how it looks now:
Creating Jira tasks We have had a bunch of users suggesting this feature. We listened, got to work, and delivered!

This feature makes so much sense. Agile Retrospectives are not really a valuable exercise unless they're followed-up on. And we know sometimes we need a bit of help on it. Especially when the team is distributed and do not have a physical board for reference to the results of previous retrospectives sessions.

There you have it! Our Agile Retrospectives tools are the perfect way to getting real value out of your Agile Retrospective sessions. Whether your team uses Jira or Confluence, we got your back!

Give Agile Retrospectives for Jira a try and let us know what you think of it. We're always looking for ways to improve and we'd love to hear what you have in mind.

Answer this: How can we help you get real value out of Agile Retrospectives (and every other agile ceremony)?


Trying to improve your #Agile practices? OR are you getting started with Agile? Are you in a remote team? Check out our products for Agile teams at SoftwareDevTools. We focus on making agile ceremonies more effective and easier to adopt for remote teams.

Check out our Atlassian tools:

Follow us on our networks:
Facebook: /SoftwareDevTools
Twitter: @softwaredevtool
Email: hello@softwaredevtools.com
And Subscribe to our blog below!


Agile transformation for distributed teams needs the right tools. At SoftwareDevTools we focus on building tools that enable #Agile in remote teams. Real-time collaboration and productive discussions.

Subscribe to SoftwareDevTools

Get the latest posts delivered right to your inbox.

or subscribe via RSS with Feedly!