Scrumban - Jira

[Esteban RD]

How do you suggest implementing this methodology on Jira? Considering that the entire Board would have to be viewed.
In fact, the idea is to also be able to visualize several independent Sprint boards ... a group that we can say.

thanks and best regards

[Phill Fox]

Hi @Esteban RD 

Welcome to the community. 

To be able to help you effectively we need to understand a little more about what you are expecting in your Scrumban view. You talk about being able to visualise several independent sprint boards do you mean you want to roll up all of the activity so you have a single view?
Are these sprints in the same project? Are the sprints all on the same Jira instance? How do you want to interact with the board?

Depending on the answers to the above there are a number of different options available to you. 

You can start very simply with a single instance that has a board built using a filter that looks across multiple projects and pulls all the information pertinent to the Scrumban board which is then based on the filter. 

If your sprints are scattered across multiple projects on multiple instances then you need to look at solutions like Rozdoum Watchtower to bring that in to a single view. 

Kind regards

Phill

[Vladimir Radchenko]

What we need in our work is to have a chance to form a sprint and release features earlier than sprint ends - when the feature is ready - clean the board from ready stories and continue, then extend sprint with another tasks. But we want to keep all "rituals" from Scrum with retro and planning, standups etc in place. This is looks like a Scrumban, and we struggle to implement it in Jira. Any ideas of how we can do that?

[Phill Fox]

Hi @Vladimir Radchenko 

So what I take from reading the above is that you want to use a Scrum approach but end the sprint early when a feature is ready to deploy. 

I would take a slightly different approach to this and just keep my sprints running on a regular cadence but manage releases as soon as they are ready (you may be familiar with this approach in SAFe as Release on Demand). By always ensuring you have working software and do not release any functionality-breaking code you can still work with your regular sprints (and get all the benefits of that regular cadence) but keep your releases when you need them. 

[Trudy Claspill]

What definition of Scrumban are you using? And why are you trying to use that methodology instead of either Scrum or Kanban?