Can I get a velocity report using the kanban method/board?

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.

2 answers

1 vote

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.

Thanks Nic.  Since Kanban does not have a velocity report, how do you estimate when something will be done?  

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 [Adaptavist]

It's the same answer - the velocity calculation is based on "we did x amount of work over period Y".  Kanban does not actively record "period Y".

So you need something to define the period when you are generating a velocity report.

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.

Yes, it's an easy thing to do, but you need to be able to define different periods for different users.  The recommended default for scrum is indeed 2 weeks.  Kanban doesn't need the periods and hence doesn't record the period.

0 vote

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 Mind sharing a copy of your sheet?

David Culp I'm New Here Wednesday

@Chris Berry  Hi Chris,  I, too, would like to see a copy of that spreadsheet.  Without any proprietary data, of course.  

I'm looking to do the very same thing and would like to know more about how you did it.

Thanks very much,

davidaculp46@gmail.com

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Jun 14, 2018 in Jira Service Desk

How the Telegram Integration for Jira helps Sergey's team take their support efficiency to the bank

...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...

491 views 2 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you