To gather data in the Agile retrospectives for jira app, the entire team inputs their ideas or issues at the same time. It’s a much better approach to have every team member input ideas separately, without fear of judgement or bias. This is not ideal since you want to know everyone’s perspective on a given issue. Groupthink is that phenomenon, where the first person brings up an issue, the whole team seems to agree or nod and any future comments on that issue will be withheld. During an in-house team Agile Retrospective session using a whiteboard where the team takes turns to input ideas, these give way for “Groupthink”. Gather DataĪs mentioned above, the team collectively inputs issues to be discussed. Using the Agile Retrospectives for Jira app means the stage is set for an efficient session. Which makes for a far more productive Retrospective session. This will allow for more and better ideas and issues to be brought up. Where issues will be input, but the author will not be revealed. Of course, some people need privacy to feel comfortable bringing up personal or professional issues (as is the case with eastern cultures). See relevant information from all of your Retrospectives. Meaning everyone can see what’s being input and will actively be participating.Īgile Retrospectives for JIRA Dashboard. The app will make the entire process totally transparent. Here’s where an app like Agile Retrospectives for Jira comes in handy. In order to build trust in your team, there needs to be transparency and accountability about the results. Just choose your preferred conference software and have the entire team connected and with their camera on. So it’s easy to follow up and to have in consideration for future sprints. JIRA is the perfect “Venue” to host your retrospectives since you already have all of the sprint information there. Everything from the venue, to the TRUST needed for people to freely share. Setting the stage involves creating that “safe space”. Set the Stage in JiraĪ retrospective is a place for everyone on the team to share. The 5 stages of Agile Retrospectives are: In this case, we will be using the “Agile Retrospective for Jira” app to demonstrate and facilitate the process. We’ll briefly describe them and explain why Jira is the perfect tool to leverage and have your Retros within. The 5 stages of agile RetrospectivesĪs you might already know, Retrospectives have 5 stages (Find out more in this article “Agile Retrospectives for Beginners”). Keep in mind, feedback is important for any system to work to it’s best capability. And you definitely would be missing out on the long-term benefits of Agile. Issues wouldn’t be fixed before you can prevent them from snowballing into proportions difficult to manage. Without a retrospective at the end of every sprint, Agile wouldn’t be the same. And most of all, it’s key for your team’s continuous improvement in the long term. Why are Agile Retrospectives important?įirst of all, we’ll start by stressing the importance of Retrospectives within the Agile framework.Īgile retrospectives might be regarded as overhead, or considered as “Post-Mortem” meetings, but these are held only when the project is concluded (not during the lifetime of the project).įrom an executive’s perspective: “Why would the whole team stop everything they’re working on just for playing with post-its? Especially when they could actually be building something of value.”Īgile coaches around the world will agree on the fact that the retrospective is the key to your products incremental value. Note: Atlassian also has a good overview on retrospective best practices here. We have also worked in Confluence which includes retrospective blueprint (template), or you can also use an app like Agile Retrospectives for Confluence, but this article shows an alternative approach based on JIRA. To help facilitate the process, teams can leverage their PM platform, especially remote teams.Īnd since 58% of respondents of the State of Agile Survey use Jira, here’s how to leverage your Jira projects to host efficient Agile Retrospectives. This is an even bigger challenge for distributed teams, since they are not in the same room and can’t share a physical space. Most of which we will discuss in this post. However, there’s still a lot of misconceptions and errors when it comes to retrospectives. “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” Continuous improvement is a challenge that Agile methodologies address in the 12 principles behind the Agile Manifesto: This blog post was written in collaboration with Luis Ortiz from NearsoftĪgile software development is all about delivering incremental value to the user and the continuous improvement of the team member’s abilities to do so.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |