I would really like to use Scrumban with Jira.

I know that there is now a kanban backlog but it's not the same for various reasons:


1) No timeboxed sprints

2) Which means no sprint goals, burndowns etc

3) the 'Done" column will just grow indefinitely


Ha sanyone any resoution to this?


2 answers

0 votes
Maarten Cautreels Community Champion May 01, 2017

Hi Michael,

At De Persgroep, some teams work Scrum and some use Scrumban. Basically they work Kanban but since we'd like the reporting for all teams to be the same we are working Scrumban. 

So these Scrumban teams do have two weekly iterations with a demo and retrospective at the end and a backlog grooming session in the middle of the sprint. They don't have a sprint planning session anymore as they don't commit on a set of features but they commit on an amount of story points (usually the average of the 5 last sprints taking into account the availability of the team).

We do have a burnup which we built with lego and we keep track of all the numbers in a Google Sheet, where we have a lead time chart, a velocity chart and an overview of all the unexpected features (read bugs) we've been working on each sprint. Simply to track evolution of the team and find out if there are any particular things we can do differently.

We're sharing this data with the rest of our company using a two weekly Sprint Report on Confluence.

You can view an example of such a sheet here: https://docs.google.com/spreadsheets/d/1iIatT_TRmhgH3U2mMLd8qbZNyTkpfPbI8Rm4SWEAKWI/edit?usp=sharing (feel free to make a copy)

I've also created a dummy version of the last Sprint Report for the same team:

Sprint Report   20170406   20170420   Maarten Cautreels   De Persgroep Confluence.png

It uses the HTML macro (not enabled by default in Confluence) to include an iframe to the Google Sheet Charts.

And we have a quick filter to hide the issues in the Done column as well as adjusted our filter to not show issues that haven't been updated in the last 2 weeks:


(status = DONE AND updatedDate > -2w)


We've tried filtering issues that haven't been put in Done in the last 2 weeks but while those History queries are very powerful, they become slower in time (if there's more issues). And you won't want your board to become slow obviously.



@Maarten thanks for that in depth reply. It really helped and I will definitely be taking some of your practices and implementing them.


Since asking this question I came across the Jira "version" and "release" functionality. This does in effect allow for timeboxing as when you create a release you are asked to enter start and end dates - and after the end date, everything in the "done" column is removed.


I'll persevere for a couple of weeks and see how we go.


@jira - it would be relatively simple to implement proper Scrumban. Is it on the roadmap?

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

661 views 4 15
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot