Alexey Pavlenko (App Developer) Atlassian Partner

Hi @Jitin Ratra , To increase the effectiveness of retrospectives, I quantified them in the app I developed - Multi-team Scrum Metrics & Retrospectives. Please read this article. It can help you to increase throughput, flow efficiency and commitments (see concrete numbers inside the article - verified many times). Here is…

Hi @Deepali Dabholkar , Natively, unfortunately, it's not possible. You can achieve it using the app I developed - Multi-team Scrum Metrics & Retrospectives. * Track my sprint and PI performance. You can select Period (X-Axis) between sprints, months, quarters, half-years, or years. If you select a period higher than…

Hi @Bob Scudder , All what you outlined can be archieved with the app I developed - Multi-team Scrum Metrics & Retrospectives. Please refer to this dedicated article for your case. Best regards, Alexey

Hi @Suraj Pawar , One of the tools for tracking progress, if you use sprints, might be the Sprint Report. It's native, built-in in JIRA. If you want more flexibility and the following features that Jira does not support natively, you can install the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you…

@Neha Manchanda , Unfortunately, for this specific use case, there is no magic AI solution from my standpoint. In order for AI to make the right conclusions, the retrospective needs to be conducted by a team. With this in mind, I developed the app Multi-team Scrum Metrics & Retrospectives to analyze and answer exactly the…

Hi @Murali Ganesh Chitrothu , My app Multi-team Scrum Metrics & Retrospectives has all the info you are looking for. The screenshots below are with X-Axis = Story Points setup, but it can be changed to Issue Count. In this case, you will get * Done = Completed Scope, * Item id: description = tickets included in Completed…

Hi @Nicolae Victor Rusu , You can use the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can track * Completed issues = Completed Scope * issues not completed = Uncompleted Scope * issues removed from sprint = Removed Scope * issues added after sprint start = Added Scope metrics or any other…

@Sowjanya Mupparaju , Closed sprints are not available in this view. For the closed sprints you can use the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can create custom JQL metrics per assignee and track total story points, completed/uncompleted/added/etc points per engineer: Best regards,…

Hi @Angela O'Brien , Please be informed that Velocity, as well as Allocation vs Capacity were added explicitly to the header of the Chart: Best regards, Alexey

Hi @carl , Consider the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can track, measure and improve team performance - several teams, individual metrics, custom metrics, several periods, drill-downs, in-place retrospectives, trends, average metrics and so on and so forth. Here are a couple of…

Hi @Ann You can use JQL filters for that, but in this case you will have to manually do it over and over again. Another solution here is the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can see Initial, Final, Completed or any other scope for several teams over several periods (sprints, months,…

Hi @Wilson Ndeh , You can accomplish everything you mentioned with my app - Multi-team Scrum Metrics & Retrospectives, but, unfortunately, it's only for JIRA Cloud. I believe, in the upcoming years your organization will have to transit to cloud and you'd be able to consider the app in this case. For individual metrics,…

Hi @DFB , Unfortunately, JIRA doesn't provide the similar gadgets as projecttrack. If you consider alternatives, you can check the set of gadgets I developed - Heat Map, Projects, Roadmap, Labels Gadgets. One of the gadgets, provide the view below about projects: Best regards, Alexey

Hi @Ritu Agarwal (CW) , Natively, unfortunately, it's not possible to archieve. You can try as an option the app I developed - Multi-team Scrum Metrics & Retrospectives, in terms of view it's a bar chart, but it covers your request in terms of data and partially the reporting period. With it, you can view: * data across…

Hi @Pratik Acharya , When it comes to dashboard gadgets, there are not so many options, unfortunately, by default. Personally, I used Filter Results, Jira Road Map, Two Dimensional Filter Statistics, Pie Chart. Using these gadget, you can cover many cases, including some of the ones you mentioned. For measuring individual…

Hi @Paulo Fonseca , To track allocation vs capacity of a single tester, you need to create a separate team board for this tester. For that you can use either * JIRA Plans (there is capacity vs allocation feature) OR * The tool I developed - Multi-team Scrum Metrics & Retrospectives: Best regards, Alexey

Hi @kafka max , You are right. It doesn't make sense to calculate capacity and velocity this way. In case these are the same contributors, I would suggest your employer organize 3 occasional contributers into a team, so that you can just sum up velocity and capacity of two teams. It won't be super accurate either, but it…

Hi @Carter ethan , Many things are available in Jira out of the box, but not the following: Track and measure: 9 pre-built sprint metrics (Initial Scope, Final Scope, Completed Scope, Uncompleted Scope, Scope Completed Outside, Removed Scope, Unestimated Scope, Re-estimated Scope, Added Scope). Any custom metric…

Hi @Sherwin Soriano , Most likely, you added scope to the sprint after it had already started. If that’s the case, you need to make sure the sprint is fully planned before it starts. Unfortunately, the Sprint Report doesn’t include a Final Scope metric. If you want to see the complete list of tasks in a sprint under a…

Hi @Vladislav Sinkevitch , One option for managing labels might be one of the apps I developed - Heat Map, Projects, Roadmap, Labels Gadgets for Jira. With the Labels Gadget, you will be able to extract the labels that are used across all your projects: With the Heat Map, you will be able to represent them in a Heat Map…

Hi @Zoya Bedelyants , Since metrics are key for you, I recommend using as few projects as possible if you want to solve as many tasks as possible with native Jira tools. Many things are available in Jira out of the box, but metrics for multi-team or multi-project setups are not. You should probably consider using a single…

Hi @Jose Souza , There is no native JIRA gadget for that, unfortunately. You can try the app I developed - Multi-team Metrics & Retrospectives. With it, you can get this view: Or this view: Best regards, Alexey

Hi @Jon Harry , Yes, unfortunately, natively it's impossible to create a multi-project/team sprint report on a dashboard, you will need a 3rd party app for that. This was one of the reasons why I developed Multi-team Metrics & Retrospectives. With it, you can address all your requests. You can display multiple teams across…

Hi @Chasovskikh Kirill , You are right, there is no possibility to extract the Capacity field from JIRA Plans, but it shouldn't be a big deal to fill it from scratch, from my standpoint. I've added the Capacity field for you to Multi-team Metrics & Retrospectives. To configure it, please do the following on the…

Hi @Brodie Chivers , >I think you’re making a bit of an assumption that these methods are trying to be the whole answer Maybe partially, but not quite, in my opinion: * Having tool with 70-99.9% preciseness would just definitely make it worth using as a basis for discussions. * There is a real possibility that a tool can…

Hi @Carolyn McNicoll , Personally, I don't believe in any of those attepts, the same applies to the AI attempts. I am making a guess, but I think your projects/programs are not super similar to one another and differ in terms of complexity, uncertanty and other conventional stuff. How can a tool make a valid assumption if…

Hi @Natalie Keane , If you are using sprints, you can use the app I developed - Multi-team Metrics & Retrospectives. With it, using custom JQL metrics, you can create a metric per each engineer (check j: CustomMetric: Linus - To Do on the screenshot). Information will be updated in the real-time. Periods, boards, table…

Hi @Stacy Norman , If I understand you correctly, there are 2 requests: * Unified view of resouce allocation for measuring and tracking purposes across 7 teams For that, you can use the app I developed - Multi-team Metrics & Retrospectives. You can render several teams across several periods (periods might be sprints,…

Hi @Chasovskikh Kirill , Thank you for the follow-up. I've added the Capacity field for you to Multi-team Metrics & Retrospectives. To configure it, please do the following on the configuration screen: * Select one of the following values for Measurement Unit (Y-Axis): * Story Points * Story Points Estimate * Original…

Hi @Harry Carter __ , Kindly check if any filters are applied to the view. If you don't mind I want to suggest you the app I developed for program management - Multi-team Metrics & Retrospectives. From my standpoint, it can ease what you are trying to do. With it, you can see multiple boards/teams for multiple periods…