Is it possible to use scrumban on Jira?

[Akarsh S]

I have to start a project. The team is a shared resource among different platforms. We have our own project but we keep getting tickets from other platforms. We need to start our project at the same time, we need to keep track of these tickets. A scrumban approach would be best suited. What are the possible ways scrumban can be implemented on jira?

[Antuan Sammak]

Hi @Akarsh S 

You might want to give a try our new application  it offers a new approach of reporting that shall help your organization and teams to analyze teams performance and identify potential improvements.

This application would suit the ScrumBan approach you are trying to achieve by applying Scrum methods while using Kanaban boards.

Happy schedule a demo to take you further into our app and how it works.

Regards,

[Bill Sheboy]

Hi @Akarsh S 

When you state a "scrumban approach would be best suited", why do you believe that?

I suggest the alternatives depend on what your team means by a "scrumban approach", and how you plan to measure to manage flow and value delivery.

• Do you mean using Kanban, with cadenced events like queue replenishment, planning, operations review, retrospective, etc., and minimum WIP, pull-based delivery?
  • This is essentially the Kanban Method, as David Anderson's books describe it
  • You could use a Jira Kanban board and manage your events independently of Jira
  • When you need measures / reporting on the cadence schedules, use marketplace addon gadgets with dashboards
• Do you mean use the Scrum framework, and there is a lot of unplanned work added to the "sprint"
  • You could use a Jira Scrum board, although the amount of unplanned work will render most of the built-in reports less helpful
• something else?

Kind regards,
Bill

[Akarsh S]

I feel so because, we work on a ticket basis. we have a project to run at the same time. We need to keep track of both as it is an organisational requirement. 

I mean the second scenario, we must use the scrum framework to timebox the deliveries.

[Bill Sheboy]

Thanks for that information. 

Perhaps try using the Jira Scrum board, and investigate other reports / dashboard gadgets that will help manage the unplanned work.  With this approach, you may have difficulty with sprint planning and capacity management.  I also predict it will be difficult to observe how improvement experiments from retrospectives impact the team flow.

Another approach would be to use a defined intake process with the other teams offering requests; that would be similar to Kanban's queue replenishment.  Those requests could then be scheduled / selected for a specific sprint, reducing the disruptions from unplanned work.

[Akarsh S]

Thank you for your response. Can you please suggest some gadgets that could be used?

[Bill Sheboy]

My disclaimer is that I am just a Jira user, and do not work for Atlassian or any marketplace vendor...

I have used Great Gadgets from Stonikbyte and found them helpful.  Before selecting an addon, I suggest listing out what you want to measure / visualize, and then compare the products to learn what may help.

[Nagabharana S]

Hi @Akarsh S ,

Are you looking for ways to use both scrum and kanban features under one roof?

[Akarsh S]

Yes @Nagabharana S 

[Nagabharana S]

@Akarsh S ,

You can have both boards on a project.  Only a scrum board can be used with sprints (Add backlog to Sprint).  Really it comes down to how you run your projects, your teams, and the processes you have in place.  You can learn more about Kanban vs Scrum here: https://www.atlassian.com/agile/kanban/kanban-vs-scrum

Start with a Scrum board, and then, well, just don't use the bits you don't need.

Most of the time I hear "Scrumban", it translates into "scrum without estimating" (in Jira - the scrum rituals stuff isn't done in Jira, so there's no need to talk about them as well here) because you're using the Kanban principle of 1 card = 1 estimate unit.  Of course, no estimation renders a lot of scrum reporting useless, and there is no cycle time reporting in Jira directly.

But the Kanban equivalence of 1 card = 1 estimate unit is the way to get something.  If you were to enable story points or any numeric field as the scrum estimate unit, and then use automation or scripting to always populate it with "1", then a lot of the scrum reports would start working and give you something almost usable as cycle time.

We must first create a scrum board, then create sprints by that, and then just back to our kanban board to use the sprints.

[Akarsh S]

Thank you for your response!