I have used the velocity report in Agile scrum. I have recently moved to an area that uses kanban and I don't see the velocity chart. I understand velocity needs a date range, so I would like story points per week. I see the control chart and cumulative flow but not the velocity.
Just an idea. I run a googlesheet that connects to the JIRA API, downloads story data, we measure our velocity through to our 'Test Done' phase.
The sheet allows me to define the period of the delivery and counts the cards/story points delivered in the selected time frame.
This in turn has allowed me to determine the velocity of the team through from when we first started with Jira and report a monthly velocity of the back of that.
This means that as we measure the time from the start date to the test done phase we can measure the points delivered in any time period.
This allows me to create a Burndown and project forward based on the current velocity.
The sheet is rather complex and has grown overtime to our specific needs, but certainly it is possible to get what you need through this method.
@Chris Berry Hi Chris - I'd like to see what you did with that if at all possible. We're exploring how to do some common metrics across the org. We have some teams that are scrum and some using Kanban, and the ask has been to see velocity and trends. I'm too new to Jira to know what the heck I'm doing other than using the provided reports.
Thanks in advance!
I know it's only been a short 10 days since your post but wanted to check in with you to see if you've been able to make any progress on de-sensitizing. I have a meeting Monday, July 8th where we will be talking about everyone's favorite subject...metrics. <- insert sarcasm here. Anyway, if it's ready...I would like to show them what you've come up with to see if it will meet our needs. Just let me know.
Thanks! ~ Renee (Renee.Stella@wolterskluwer.com)
This is the sheet that I use. Please take a copy, you will need to change the value of the domain held in line 3 of code.js to reflect your installation
Data is downloaded into the backlog sheet
The headings in the sheet determine what is loaded in, if you have different data you wish to load simply change the headings in the sheet and the code will pick that up and load in what you specify
When running the sheet you need to configure the query that you wish to run
Jira Options>>Configure Jira
This will ask a number of questions, this in turn builds the query
You can also configure the sheet to automatically update every x number of hours.
The burndown charts in this sheet are all calculated using the 'Moved to Testing Done on' Date - this is the point that we record that work is completed. This is a custom field so you may wish to use something else
This works for our installation of Jira Cloud.
Velocity is calculated based on sprint data such as start and end, what you planned into it and what you managed to complete during the sprint. Only the "what we did" data is captured in Kanban, so you can't generate a velocity.
Average points solved per week, as you say, is possible, but there's no real reporting on it. Although I'm sure I saw one in the marketplace that did exactly that a while ago.
Depends on how the estimates are done in the team or what the business wants. Some places ask a developer to fill in an expected date when they move it to "in progress", others for a time based estimate. Some ask for something like story points. Most do some form of estimate (even though Kanban isn't really heavily into estimating), but when they start getting demands for fixed timings, multiple estimates and team load, they move to ScrumBan or Scrum. (If you want to try Scrumban in JIRA, you usually start with a Scrum board and trim stuff off it to simplify it, so that you get the iteration stuff)
@Marty Johnson - I just came to the Atlassian community to ask exactly the question you have asked above. Our Dev team have recently moved from a scrum board to a Kanban board because we're not able to plan in advance to fix our scope for a sprint... Kanban as a concept is working well for us.
BUT - I'm the Product Owner and I want to know when things are going to get done so we still estimate our stories using story points - which I think is fine - I don't see why it should matter whether it's Scrum or Kanban as far as estimating with story points go.
So what I want to know is how many story points do we deliver within x period say every two weeks. As far as I understand that's velocity so I don't quite understand Nic's response where he says you can't generate velocity in a Kanban wall.
So - are you able to give me an update on what you've learnt on this since you made this post? I would have thought that this is VERY common requirement for product owners/Dev teams.
Feel free to also chip-in if I'm missing something @Nic Brough
Yep - that's what I need. Any ideas on how I might be able to do that?
I guess I feel like wanting to know velocity, even though operating on a Kanban wall, would be a common need for teams so I'm a bit surprised it doesn't come out of the box or am I fundamentally missing something?...
Looking at Nic's response--isn't this a really simple thing to do? We have well-known ways of defining time periods. We call them weeks and months. We don't actually need sprints to define a time period.
I'm one more product owner looking for a way to measure velocity--really simple--stories/week or points/week. Any progress on this?
Edit: Just saw the note about the gadget below. Gonna look at that.
So, clearly, no easy solution for Kanban.
As a workaround, I apply filters. I search for tickets that were estimated "Story Points" = "1", then replace "1" with "2", an so on. Record the numbers and sum them up.
So the detailed steps are the following:
1. Decide on the period. The format is: (2019-01-01, 2019-02-01)
2. Decide which JIRA statuses mean start of work on the ticket / completion of work. For me, statuses are called "In Progress" / "Deployed".
3. Write a Search query in JIRA to get all tickets that were estimated as 1 story point
project = "PROJECT" AND status=Deployed AND status CHANGED during (2019-01-01, 2019-02-01) TO "In Progress" AND "Story Points" = "1"
4. Write down the number of tickets that you got with this search.
5. Repeat similar search for other values of Story Points: 2,3,5, whatever you use. Example:
project = "PROJECT" AND status=Deployed AND status CHANGED during (2019-01-01, 2019-02-01) TO "In Progress" AND "Story Points" = "2"
project = "PROJECT" AND status=Deployed AND status CHANGED during (2019-01-01, 2019-02-01) TO "In Progress" AND "Story Points" = "3"
project = "PROJECT" AND status=Deployed AND status CHANGED during (2019-01-01, 2019-02-01) TO "In Progress" AND "Story Points" = "5"
Record your results:
6. Now if you calculate the sum, you will have total number of story points accomplished within a period.
For the example above, total Number of Story Points = 14*0.5 + 10*1 + 8*2 + 3*3 + 2*5 = 52 (Story Points).
P.S. You may want to add some automation. I get the queries automatically assembled in Google Sheets:
You can make a copy of it and set it up to your liking.
Hey Valentyn. Try our Great Gadgets add-on. It has a Kanban Velocity gadget that should solve your problem. It is based on a filter. https://marketplace.atlassian.com/apps/1218777/great-gadgets-for-jira-server?hosting=server&tab=overview
This is pretty simple for Kanban boards:
project = "Project Name" AND status changed to "Production Installed" DURING (startOfWeek(), endOfWeek()) AND "Story Points" in (1, 2,3,5,8,13)
then download it in excel and select all data from story point coloumn in excel and excel will automatically sum all story points.
Hi community members, My name is Erika and I’m a product manager at Atlassian. We’re currently investigating how teams are planning work at the program level. We understand that every team in a tea...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events