Last week, we announced the integration between two of the best Kanban plugins for Jira: Kanban Analytics by Nave and Advanced Kanban & Agile Boards by Release Management.

This partnership is a game-changer in the Kanban industry, as it provides all the tools to implement the Kanban Method in Jira without spending any time or effort, allowing you to start your improvement initiatives as early as tomorrow morning.

Although we covered the basics in our previous article, I’d like to reveal the power of the AKB plugin in your efforts when transitioning from Scrum to Kanban.

For teams looking to make this transition, we know it isn’t an overnight shift. This is where AKB comes into play, helping teams move gradually from Scrum to Kanban without any pain or overhead.

The goal here is to slowly enable the main Kanban practices without changing the way teams work right from the get go.

Let’s explore how we can achieve that using the AKB Plugin.

Now, let’s dig deeper into the concepts.

How to Perform Relative Estimations

In the Advanced Kanban & Agile Boards plugin, you can create an Estimation board. You can assign story points as columns and labels (which we use to specify teams) as swimlanes.

Clustering Agile Estimation Board | Illustration

You can now use that board to perform user story estimations.

Furthermore, what you can do is simply drag and drop stories of the same size; the application will then assign an estimate of the same amount of story points to them.

You can use the exact same approach to assign hours or T-shirt size estimates.

Kanban Estimation Board | Illustration

The goal here is to keep doing what you’re currently doing but slowly introduce alternative estimation approaches like Monte Carlo Simulation.

Monte Carlo Simulation by Nave | Illustration

Use both approaches in parallel and let the teams decide on their own which one is the faster, less time-consuming, and ultimately more reliable one.

How to Prioritize Your Work

Another cool feature of the Advanced Kanban & Agile Boards Plugin is its ability to convert your board columns to a backlog. This view has proven to be very useful during Sprint Planning.

Convert Board Columns To Backlog | Illustration

Using the exact same approach, you can create a new board and assign estimates as columns and importance as swimlanes. As a result, you’ll find all the tickets with small size and high importance in the first quadrant, and all the items with low priority and significant effort in the last quadrant.

Assign Estimates and Importance As Swimlanes | Illustration

These two views are super helpful when you need to decide which stories to prioritize first, which can wait for later, and which can be discarded altogether.

With this feature, you can continue planning the work as you used to while simultaneously introducing more Kanban practices supported by the tool.

How to Manage Your Sprints

Now, if you’ve started your initiative to move from Scrum to Kanban, you already know that transitioning from time-boxed releases to continuous flow is one of the biggest challenges you’ll face.

That’s why you may want to keep the Sprints until the team is mature enough to effectively manage their work and shift their focus to continuous flow of work.

To support this concept, you can use the AKB tool to create a board with Sprints as swimlanes.

Create board With Sprints as Swimlanes | Illustration

While you’re managing your sprints, make sure to keep tracking the age of your work in your Aging Charts.

Aging Chart by Nave | Illustration

The goal here is to pay special attention to all stories that move from one sprint to another and keep the team’s focus there. If you’re running 14-day sprints, ensure the teams have a discussion about everything that surpasses the 14-day mark on the Aging Chart. This action alone will ultimately lead to an improvement in their flow metrics.

Here’s Your Action Item: If you haven’t explored the Advanced Kanban Boards Plugin for Jira, this is the right time to get started. It’s free for 30 days, no CC required

Start your free trial today and get 10% off all yearly plans using code AAKBNAVEANNUALLY and all monthly plans with code AAKBNAVEMONTHLY for the first year!

The transition from Scrum to Kanban doesn’t have to be challenging. It can be gradual and seamless if you let it be. Take advantage of all the tools at your disposal.

Enabling Kanban on Jira has never been easier, so don’t delay—start as early as tomorrow morning.

I wish you a productive day ahead! I’ll see you next week, same time and place, for more managerial insights! Bye for now.

Do you find this article valuable?
Rating: 5 stars (2 readers voted)