nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I have a Kanban board, but need to run a velocity chart based on the Releases already in place. How?

Tasnim Mansur

Hello,

I am a new Release Manager, working to organize an already existing Kanban board. I need to plan for Capacity Planning. How can I do the following?

1. Show Capacity Planning through an existing report using story points on each issue?

2. Change the board to a scrum board? Can I add Sprints?

3. Do you have any other options or ideas for me to try?

Taz

Accepted answers

All comments

Trudy P Claspill

Hello @Tasnim Mansur

Welcome to the Atlassian community.

Are you using Jira Cloud or Jira Data Center? What information do you get when you click the Help button (the question mark) near your avatar in the menu bar, and then select About Jira?

If you go to the View All Projects page under the Projects menu, what do you see in the Type column for the project you are working in?

If you are working with a Team Managed Software project in Jira Cloud you can can have either a Kanban board or a Scrum board in the project, and you change between the two using Project Settings / Features and enabling the Sprints feature.

If you are working with a Software project in Jira Data Center or a Company Managed Software project in Jira Cloud then you would create a new board of the Scrum type using the same filter as the Kanban board you already have.

Velocity Reports are not natively available based on Release information. If you must have that you would need to look for a third party app.

Velocity Reports are natively available based only on Sprints. If you have not been using Sprints then you will not have any Velocity history. You would have to start using Sprints to build up Velocity history over the next several sprints.

That would give you basic capacity planning in the sense of telling you how many story points are being completed per sprint, but it doesn't really tell you anything about how many people-hours were available to do the work in that time.

If you want to investigate more detailed capacity planning capabilities you could look at the Advanced Roadmaps feature that is available in Jira Data Center and in Jira Cloud Premium and Enterprise product plans. There are also third party apps that you could purchase that provide capacity planning features. Here is a search from the Atlassian Marketplace to help you get started finding such apps (for Jira Cloud):

https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=capacity

Amay Purohit_RVS

Hi @Tasnim Mansur

Welcome to the community !!

A mktplace app can help to plan the capacity of your teams. If you are open to try one, take a look at :

Capacity Planner

We do have the option of planning capacity for a project fix version or a sprint.

With the add-on you can :

Maintain the team members daily capacity in a template and decide work allocation.
Define resource leaves.
Plan capacity either for time estimates or story points.
Check the effort progress of the resource and make decisions accordingly.
Track the actual time spent per task

Do try it out.

Disclaimer : I work for the vendor who built this app

Capacity Report Fix Version - New.PNG

Resource Tasks.jpeg

Danut M _StonikByte_

Hi @Tasnim Mansur,

Jira does not offer a native gadget or report to measure the velocity in Kanban. And this might be because "velocity" is not a Kanban term; it is specific to Scrum.

A possible solution would be to look for an add-on on Atlassian Marketplace that offers this functionality.

For example, our Great Gadgets app includes a Kanban Velocity / Throughput gadget that will help you calculate the velocity for your Kanban team.

This gadget can calculate the average velocity as completed issues or story points in past time intervals, thus giving you an idea of how much work your team delivers in certain time-frames (like 2 or 3-weeks long intervals). See this article: How to track the Kanban velocity / throughput with Great Gadgets app for Jira.

Hope this helps.

Disclaimer: I work for the company who made this app.

Danut.

Dave Rosenlund (Trundl)

@Amay Purohit_RVS: Please stop answering community questions with ads for your products.

As an Atlassian partner, it's crucial to adhere to the marketplace guidelines. These guidelines are designed to help you share your expertise with the community in a way that aligns with the feedback Atlassian consistently receives from community members.

Responding to community questions with ads for your products is a violation of these guidelines:

Atlassian Community online guidelines | Marketplace + Solution Partners | App Central

Atlassian developed the guidelines based on feedback from the many customers who come to the community to learn from their peers. They have said loudly, many times, that they greatly dislike this sort of reply. So, in reality, you are not helping them or yourself when you reply with an ad for your product.

I'd be happy to discuss this with you. I have personal experience being an active member of the Atlassian Community while working for Atlassian partners. I will gladly share what I've learned over the years.

You can find me easily on LinkedIn.

Danut M _StonikByte_

Vasyl Krokha

Hi @Tasnim Mansur

You can have an overview of completed issue grouped by periods filtered by releases, epics and/or custom JQL using the Velocity for Kanban boards gadget which is part of Agile Reports app by Broken Build.

It is possible to deep dive into each interval to see the two-level issue breakdown. In the example below project->issue type.

The lowest level of details gives you the list of issues for the whole selected period or breakdown item.

Kanban velocity with issue breakdown and issue list.png

Thanks,

Vasyl

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

unknown-hosting-type

jira-unknown-hosting-type