DEV Community: Dovile Miseviciute

Kanban for Multi-Project Management

Dovile Miseviciute — Tue, 17 Sep 2024 14:42:06 +0000

Kanban is great for visualizing your process and tracking effort. But when it comes to larger or multiple projects it often gets cast aside as unsuitable.
This may have been true a few years ago, but with modern Kanban tooling such as Teamhood, you no longer have to give up the visual approach.

While you may be skeptical about this, here are the unique features that allow for multi-project management within a Kanban system.

1. Flexible Kanban board structure with swimlanes, statuses, and sub-statuses.

Many Kanban tools on the market offer very limited Kanban boards, but that is not true for Kanban systems. Here, you can easily classify your tasks with Swimlanes and multiple commitment points. Thus making it easy to manage and identify the most important work.

2. Customizable visual cues.

Another crucial aspect of multi-project management is focusing your attention where it matters. For this, systems like Teamhood allow you to go beyond coloring tags or overdue items.
You can choose to color rows, statuses, and items, as well as feature attached images on item cards. All of which lends to the quest of getting attention where it is needed.

3. Global reporting.

Lastly, make sure your chosen Kanban system offers global reporting for all the boards within your workspace. This may seem minor, but it means you will be able to track each project on a separate Kanban board while reviewing progress for all of them in one place.
This includes a global workload view to easily match capacity with the project needs.

Seems like you could use a system like this? Learn more about multi-project management with Kanban.

Find Your Pace as a New Team Leader

Dovile Miseviciute — Fri, 05 Jul 2024 08:47:27 +0000

Starting a new position in a company always comes with some level of uncertainty. You have to adapt to the style of work, understand the processes, and possibly learn new skills.

What if this new position is now a leading role you did not have previously? It's a chance for personal and professional growth, a journey that may bring pressure and uncertainty but also immense learning.

Here are some tips on what helped me when faced with a similar scenario.

1. Rethink Your Responsibilities

Moving from a team member to a team leader does not usually happen overnight. However, it is still a big change in your responsibilities and expectations.

For me, the most important thing to understand was where my new priorities lie. As such, I had to sit myself down and think about the process by answering questions such as:

How much of the work I did previously am I supposed to output now?
How much time will I spend on leading my team?
What type of support do they expect from me?
Which types of tasks should I pass down to the team instead of handling them myself?

It is all quite self-explanatory, but when moving from a functional to a leading role, things might get a bit mixed up. Being a team leader is a multiple-hat role, but this does not mean e a doing-everything role.

And from personal experience, it is really easy to go down that slope. All you need to do is say, 'I’ll handle that' one too many times.

2. Adjust Your Process

Once I had a clear understanding of my new responsibilities, I needed to review and set up a process that would fit them.

It took me a few tries and even going on a short vacation to gain perspective on how things should be done. But I think I am slowly getting there.

The keyword being 'getting there'.

What I would love to have done differently? I should have spent more time on this in the beginning instead of trying to continue with my old tasks on top of the new responsibilities.

As a new team lead, I will still need more time to feel fully confident in the process or will likely learn that it is never perfect, just right for right now. And that is what I am working with.

Of course, having a visual collaboration tool on hand is quite beneficial and helps me see how things are or aren't moving along.

3. Expand Your Skillset

My last piece of advice is to continue learning and improving.
Again, this may seem too simple, but too many of us forget how important it is to keep on learning past that initial phase of change.

What helps me in this case is keeping the learning diverse. You have multiple resources such as courses, conferences, YouTube, LinkedIn, and other channels for people leading their own teams.

Most importantly, do not forget those working within your own company. They have immense knowledge of your industry and operations. Which gives you quite an advantage as a successful leader.

Also, here is a handy post on developing timelines and roadmaps.

To sum up, I am still on the path of learning to be an inspiring and efficient leader to others, and surely there will be many challenges ahead. But for now, these are the tips that helped me feel more confident in the first few months and I hope they will help you too.
Share your thoughts in the comments below.

How to Tame Kanban for Your Team's Success

Dovile Miseviciute — Wed, 29 May 2024 15:42:51 +0000

Welcome to the wild world of Kanban! It's a bit like trying to tame a dragon with a whiteboard and a stack of sticky notes. But don't worry; we're here to help you become the ultimate Kanban practitioner, ready to conquer workflow chaos and lead your team to success.

So grab your notepad, and let's dive into the adventure!

Kanban Inventory: The Starting Point

First things first, let's talk about Kanban inventory. Think of it as the pantry of your workflow. You need to know what's in there before you can start cooking up some productivity magic. This means listing all the tasks, projects, and ideas your team is juggling.

Now, if your inventory looks anything like mine, it's a mishmash of post-its, digital notes, and the occasional forgotten to-do list. Trust me, you’re not alone!

A colleague once quipped:

"My Kanban board looks like a crime scene investigation—strings everywhere, no clear suspects!"

Kanban Prioritization: Taming the Beast

Once you've got your inventory sorted, the next challenge is Kanban prioritization. Imagine you’re at an all-you-can-eat buffet. You can’t eat everything at once without regretting it later (and probably getting a stomach ache).

Prioritizing tasks is about picking what to tackle first to keep your team from biting off more than they can chew.

To make this fun, some teams use a "Kanban Party" where they get together and prioritize tasks while eating pizza. Pro tip: it’s best to avoid using pizza grease as a ranking system.

A good laugh often accompanies the realization that half the backlog could probably be labeled "wishful thinking" or "never gonna happen". As one team member put it:

"Our backlog is like Narnia—every time we venture in, we get lost and meet talking animals."

Visual Collaboration Tools: The Kanban Wizards

Next up are your visual collaboration tools. These are your magic wands for Kanban success. Tools like Trello, Jira, and Teamhood turn your messy thoughts into organized workflows. But hey, if you’re feeling adventurous, explore this list of Notion alternatives for a fresh spin on visual task management.

Using these tools can feel like being in a high-tech spy movie. One minute you're dragging tasks across your digital board with the finesse of a secret agent, the next you're frantically searching for that one overdue task like a hacker trying to defuse a virtual bomb. But fear not! With these tools, you’ll soon master the art of visual collaboration and keep your team in sync.

Developing Roadmaps and Timelines in Kanban: The Treasure Map

Creating roadmaps and timelines in Kanban is like drawing a treasure map. You want clear paths, achievable milestones, and a big X marking the spot of your final goal. But let's be real: sometimes it feels like we're more likely to discover buried treasure than hit our deadlines perfectly.

To navigate these treacherous waters, involve your team in the planning process. Set realistic milestones and celebrate small victories. And always, always have a backup plan. Remember, "A roadmap without flexibility is like a treasure map with the X in the wrong place—confusing and pointless."

Embracing the Chaos with Humor

Kanban can be a challenge, but embracing the chaos with humor makes it more manageable. When things go awry (and they will), a good laugh can ease the tension. As one wise project manager once said:

"Kanban is like herding cats—just when you think you’ve got it under control, everything scatters."

So, post funny quotes and memes around your workspace. Here are a few to get you started:

"Why does Kanban always seem like a good idea until you have to move tasks? It's like playing Tetris with real-life consequences."
"I have a love-hate relationship with my Kanban board. Mostly hate during crunch time, but it’s pure love when the last task moves to 'Done'."
"Managing tasks in Kanban: 90% moving sticky notes, 10% actual work."

Final Thoughts: Becoming a Kanban Connoisseur

By now, you should have a better grasp on how to tame Kanban for your team's success. Remember, the key lies in managing your Kanban inventory, prioritizing like a pro, utilizing visual collaboration tools effectively, exploring notion alternatives for the best fit, and developing clear roadmaps and timelines.

Most importantly, keep a sense of humor. Kanban might feel like a rollercoaster, but it’s all part of the ride. As you master the ups and downs, you’ll find your team working more smoothly and efficiently.

So, go forth, Kanban conqueror! Organize those sticky notes, drag those tasks across the board, and celebrate every win, big or small. Your team’s productivity (and sanity) will thank you.

And remember, when in doubt, there's always pizza.

Now, get out there and tame that Kanban dragon! 🐉

Managing Software Development Teams: 8 Tips for Success

Dovile Miseviciute — Thu, 23 May 2024 12:18:47 +0000

Managing a software development team can feel like herding cats, but with the right strategies, it can be a rewarding and incredibly productive experience. Whether you’re a seasoned manager or new to the role, these tips will help you foster a positive and efficient team environment.

Below I have gathered 8 tips that are sure to help you in the efforts to put your team on top.

1. Foster Clear Communication

While this may seem obvious, communication is the backbone of any successful team. Ensure that every team member understands their role, responsibilities, and the project’s goals. Utilize tools like Slack, Microsoft Teams, or Teamhood to keep everyone on the same page. Daily stand-ups, regular check-ins, and open-door policies can also encourage continuous dialogue.

"Effective communication is the foundation of any successful project. Clear expectations and regular updates can prevent many issues down the road." – Alex Johnson, Senior Project Manager*).

2. Embrace Agile Methodologies

Agile practices like Scrum or Kanban project management can help manage workflow efficiently. These methodologies promote iterative development, regular feedback, and flexibility to changes, which are crucial for software projects.

"Adopting Agile was a game-changer for our team. It brought in a structure that improved our productivity and helped us adapt to changes more swiftly." – u/devguy1985.

3. Encourage Continuous Learning

The tech industry evolves rapidly, and staying up-to-date is essential. Encourage your team to attend workshops, webinars, and conferences. Providing access to online courses or allocating time for self-study can also be beneficial.

"The tech landscape is ever-evolving. Encouraging continuous learning not only keeps the team updated but also fuels innovation and personal growth." – Emily Davis, Lead Software Engineer.

4. Promote a Collaborative Environment

A collaborative environment encourages team members to share ideas and solve problems together. Use pair programming, code reviews, and collaborative tools like GitHub to foster teamwork.

"We've seen a significant improvement in our code quality since we started emphasizing pair programming and collaborative problem-solving. It’s amazing what a difference teamwork makes." – u/codemonkey2020.

5. Set Realistic Goals and Expectations

Setting achievable goals is crucial for maintaining team motivation and project momentum. Break down larger tasks into manageable chunks and set clear deadlines. This helps avoid burnout and keeps the team focused.

Create a project planning timeline that follows the project goals but is also deliverable and accounts for possible setbacks.

"Setting realistic goals is crucial. Overpromising leads to burnout and disappointment. It's better to underpromise and overdeliver." – Sarah Thompson, Product Manager.

6. Provide Constructive Feedback

Regular feedback helps team members improve and grow. Be specific, positive, and constructive with your feedback. Celebrate successes and address areas of improvement with a supportive approach.

Rely on engineering productivity metrics to ensure you are tracking the right things and focusing on effective work, not just the quantity of it.

"Constructive feedback is vital. It helps people grow without feeling attacked. Always balance the negatives with positives to keep morale high." – u/techleadjane.

7. Recognize and Reward Efforts

Acknowledging hard work and achievements boosts team morale and motivation. Whether it’s a shoutout in a meeting, a bonus, or a simple thank you note, recognition goes a long way.

It is too often that team leaders focus solely on growth. Do not be the manager that simply says - that's great. Be one that celebrates the achievement of what it truly is and means to the team.

"Recognition doesn’t always have to be monetary. Acknowledging hard work and contributions in meetings can go a long way in keeping the team motivated." – Michael Brown, Engineering Manager.

8. Cultivate a Positive Work Culture

A positive work culture enhances productivity and job satisfaction. Encourage work-life balance, provide opportunities for team bonding, and ensure that your workplace is inclusive and respectful.

"A positive work culture where people feel valued and respected can lead to incredible outcomes. It’s the difference between a team that’s just working and a team that’s truly excelling." – u/happydev.

Final Thoughts

Just like with any other team, being the leader of a software development team requires various skills and takes time to master. Become a better leader by getting to know what drives the team and what makes it tick, and acknowledge their achievements just as you would talk through the setbacks.

Teamhood - Unique approach to Kanban project management

Dovile Miseviciute — Thu, 20 Apr 2023 14:05:44 +0000

Visualize your process and track progress. Teamhood is free to use for unlimited users.
Try now

Here is a short video highlighting how Teamhood can be used to set up simple and advanced Kanban boards for your needs.

Kanban Board Example - From Simple to Advanced - YouTube

Try Flexible Kanban Board: https://teamhood.com/product/kanban-board/?utm_source=youtube&utm_medium=video-description&utm_campaign=yt-kanban-exampleLearn abo...

youtube.com

Is Asynchronous the New Way to Go?

Dovile Miseviciute — Thu, 16 Mar 2023 12:28:43 +0000

We have been through quite a few changes in recent years when it comes to organization and management of work. First, most had to find new ways to work from home, then others struggled when having to come back to the office.

With all this commotion going around, we have witnessed a rise in one term that has not been widely used before - asynchronous. Thus, I wanted to explore whether this new trend is here to stay or will it fade away as we sort out our working procedures once again.

What is asynchronous work?

To begin this discussion, let's have a brief refresher on what the term asynchronous means in the context of work or collaboration. In this context, there are two ways of working - synchronous and asynchronous.

Synchronous is when the whole team is working using the same schedule. A good example of this is a traditional office where everyone begins work at 9 and finishes at 6. In this type of scenario, it is easy to communicate with colleagues and collaborate as everyone is on at the same time.

Asynchronous talks about each team member being able to choose when they prefer to work. This means there is no predefined time for you to work instead you can do so depending on your schedule, time zone, and other factors. While this is great on a personal level, it can bring certain difficulties for collaboration, especially when there are limited processes in place to help regulate the team.

What are the benefits of asynchronous

So, as synchronous work seems to be much more preferable on the organizational side of things, why are we witnessing a rise in the asynchronous approach? Well, the biggest contributor to this has to be the shift to remote or hybrid work approaches that require a certain level of flexibility. Here, the asynchronous practices help set up a system in which the whole team can thrive.
Let's look at those practices in more detail.

In general, asynchronous says that the team is not coordinating in terms of the time each team member works. However, in most work environments this cannot be applied blindly. And in fact, the asynchronous approach tends to work best when there are certain guidelines in place. Here are some we practice in Teamhood to ensure we maintain the communication lines open.

Weekly check-ins Our team is fully remote which means we could go without talking for days. Thus, to ensure the whole team is up to what is happening we hold a weekly check-in meeting to see what each department is working on and to report on progress.

While this may seem just like another progress meeting, it has a different purpose. Here we aim to briefly discuss what is the main focus of each team for the week so that others can stay in the loop. To make this as pain-free as possible, this meeting usually lasts just 15-20 minutes.

Expected response times
Another important factor in asynchronous work is ensuring there are certain spoken or unspoken rules about when are you expected to respond. These usually differ depending on the communication channel.
For example:
For a quick answer, I would go on and type up an instant message.
For something more complex or in cases I could wait a full day for the answer, I would leave a comment in the task details (in the task management system).
For a brainstorming session or a discussion, I would actually consider leaving asynchronous behind and holding a more productive session in person.

Defining the expected response times on the company or team level allows you to manage your expectations accordingly and use the correct communication channels depending on urgency.

Live sessions Lastly, being asynchronous first does not mean you have to forgo meeting in person altogether. These meetings will be rare and far between, but having them is great for team morale and a sense of increased productivity.

In the case of our team, we chose to schedule such meetings for bigger brainstorming sessions and discussions. And in the case of anything longer than 2 hours, we meet in person instead of scheduling an online meeting. This gives us a space to not only complete the task at hand more efficiently, but also catch up with other team members we might not have spoken to in a while

What are the possible downfalls?

Asynchronous work surely brings quite a few benefits to those using the remote or hybrid working approach. At the same time, it requires some maturity from the team. Especially for those going from working together in the office to this approach.

You have to get used to the longer response times, get accustomed to planning your personal work accordingly, and get in a habit of reporting your progress in a way that allows other team members to stay in the loop. These are not difficult tasks, but you have to give your team some time to get used to the new processes and master them.

If you feel that the team is too set in the old ways or that management will not approve of this change, asynchronous might not be the right fit for you at the moment.

Example of asynchronous work tooling

Another thing to consider when switching to asynchronous work is tooling. If you are already working remotely, you most likely have everything needed. However, it is always a good idea to revisit what you main need before taking the plunge.

The basic list can be compiled out of an instant messaging solution, a visual Kanban board, and an online meetings app. Everything else will greatly depend on your process and work specifics.
Here are some free asynchronous work solutions you may like.

Final thoughts

So, is asynchronous the new way to go? It seems the answer is not definitive at this point.
For some, it will be a no-brainer, as a way to improve their remote or hybrid team communication and work practices. And for others, it will prove to be an additional thing to do that does not yield the desired results.

However, most of us would certainly benefit from including just a few simple asynchronous practices in the workday. Such as getting fewer notifications or not feeling the urge to answer every email as soon as it comes in would definitely improve the workflow and productivity. Thus, if I may say, asynchronous is here to stay. As it will most likely be applied in one form or another by quite a few professionals in the coming years.

5 Things to Look for In Kanban Tools

Dovile Miseviciute — Wed, 08 Mar 2023 17:48:54 +0000

If you are familiar with Kanban, you most likely know that the market for Kanban tools is quite large. Thus, picking your next solution can become a daunting task. Especially, if you are doing so for the first time or are unsure of what to look for.
To help you out, I wanted to overlook the most common and more advanced Kanban features. As well as to point out which of them are crucial for specific situations.
Ready to make your list of requirements? Let's begin.

1. Visual interface

While this goes without saying with such a visually based practice as Kanban, I think it is still worth mentioning. One of the biggest benefits of Kanban is being able to visualize your process and understand the status from a glance. As such, the Kanban software you decide to go with must meet this initial requirement.
Most kanban tools will provide you with the traditional kanban board out of the box. However, you can find some examples like Miro, that are created like a whiteboard. Thus you are free to draft your own board in any way.
Additionally to liking the visual layout of the tool, also think about what information you would like to see on the task cards. Is adding the title and assignee information enough? Or would you like to visualize subtasks, tags, preview images, and add hyperlinks? Different Kanban solutions offer varied options and having your priority list will help in understanding which of them are your favorites.

2. Kanban features

Moving on from the board itself, you will want to understand which of the Kanban-specific features you need. I am talking about WIP limits, lead and cycle time reports. If you use such features daily, you will want to ensure the new solution also supports them. Otherwise, you will be stuck doing calculations manually which is a counterpoint to even having a Kanban tool.
This will be a requirement for more advanced Kanban teams or for those that are looking to expand their practice and knowledge further.

3. Scalability

Now, this is a big one. If you are working in a small team that is not likely to grow or expand, scalability may not be a concern. However, most businesses tend to grow and at some point, certain Kanban solutions become just too limited.
You will most likely feel the Kanban board becoming too crowded or having to dedicate separate boards for separate processes to keep them manageable. To avoid such struggle, look for tools that support larger processes or allow scaling. Features such as Kanban swimlanes or secondary process columns to track subtasks, provide a great sense of structure even for the largest teams.

4. Inclusion of other practices

Another feature set you may want to look out for is related to more traditional project management tools such as time tracking, workload management, and Gantt charts. Many Kanban solutions now offer such features out of the box or as add-ons. So, before you make the final decision, ensure to check what is available.
If you are used to planning out longer periods of time with Gantt, a tool that can seamlessly switch between Kanban Gantt chart will do wonders. By considering this step, you are minimizing the tooling needed for your process and boosting productivity.

5. Customization

Lastly, pay some attention to the customization features each tool offers. No two teams practice Kanban the same. Which is natural due to different processes, products, and even goals. And working in an environment that is optimized for you helps achieve better results.
Pay attention to things such as creating templates, creating custom fields, and customizing the available reports and views to show what is important to you.

Final words

At first, it may seem there's an endless choice of Kanban tools out there. But by creating a clear priority list, you will soon be able to see which of them are the true contenders. You may soon find yourself quite surprised that the market favorite is far from the best for you.

Kanban vs Gantt Chart - Do You Have to Choose One?

Dovile Miseviciute — Thu, 19 Jan 2023 17:58:07 +0000

Both Kanban and Gantt charts are tools that initially disrupted the project management field. They introduced new ways of working and organizing your team that promised more efficiency and better results. However, due to the time gap between them, they are more often seen as opposites which one must choose between.

While many believe this to be true, with new project management apps, there is no more need to pick just one. In fact, you can use both of these tools when needed and yield the benefit of having more options within one solution.

Here is what using a Kanban and Gantt chart looks like.

Using the Kanban Board

If you have the option to use both tools within one solution, you will most likely find out that each have their strong points. In my personal experience, Kanban boards are best for day to day task management and tracking.

Each team can set up their board to represent the specific process and have a good understanding of the progress. This visualization of what is being done is useful for the team as they get a better sense of what is yet to be done. And to the manager as they can understand the teams velocity and estimate the completion of the project a lot easier.

Using the Gantt Chart

The Gantt chart on the other hand will be most useful when applied to project planning and monitoring the overall progress. Set the initial plan in place and measure against that baseline to see how any discrepancies may affect the overall outcome.

Get the Best of Both Worlds

By combining the usage of the two tools, you will be able to do more in one tool and get a different viewpoints into the data. Have a centralized place for all the project tasks and save time on logistics.

Taking Full Advantage of Kanban

Dovile Miseviciute — Fri, 13 Jan 2023 10:11:04 +0000

Most of us are familiar with Kanban on some sort of a level. Some heard about it, others already tried it. But as a team that develops a Kanban tool we see that many still see the approach as shallow and lacking for larger project management.

That is a case for some Kanban tools and applications, but not all. And this is where a simple Kanban board differs from a Kanban system. Later being able to handle more difficult processes and aid in management of larger efforts.

So, let's talk what such systems include and how they empower the Kanban teams.

Components of a Kanban System

At a first glance, Kanban system is very similar to a Kanban board. As it visualises the teams tasks using a board and item cards. However, for most Kanban boards this is more or less the limit of what they can be used for. While the Kanban system carries much more functionality within.

Here is the most common list of tools you can expect to find.

1. Swimlanes or Classes of Service

This first and probably the most noticeable difference you will find in such a system is the ability to add Kanban swimlanes. For those not familiar with the concept, they can simply be described as rows on a Kanban board.

And while this seems like a very simple addition, it brings the ability to categorise your items in multiple ways and focus the attention of the team to the right place at all times. Which becomes especially important with a larger project or a larger team.

2. Commitment Points

Another structural difference in a Kanban system will be the ability to clearly mark the commitment points on your board. The commitment point is used as a marker on the board that symbolises once an item goes past this point, it should not be moved back.

This is important to encourage effective problem solving and ensuring that the team members are not working on multiple items and switching back and forth.

3. WIP Limits

One more element of a Kanban system are WIP limits. Traditionally these are limits set to ensure only a certain number of items can be placed in any one column. Depending on the process steps, these numbers can be different for each column, but their purpose remains to limit work in progress and reduce lead time.

Some Kanban systems offer the ability to add such limits the the Swimlanes as well as process columns. Thus giving the team even more control of their process.

4. Kanban Metrics

Lastly, a Kanban system differs from a Kanban board by the simple fact that it carries the ability to calculate and review Kanban metrics automatically. Giving you important information about the capacity of the team and highlighting problem areas that could be solved to improve.

At the end of the day, it really is up to you and your team whether a simple Kanban board or a more advanced Kanban system is needed for your process. However, knowing there is more to Kanban than just columns and items, may help you make the right decision.

Choosing between Scrum and Kanban

Dovile Miseviciute — Thu, 05 Jan 2023 13:23:56 +0000

Managing any process means having to constantly look for ways of improvement. Which often entails trying out new practices and approaches.

Since my team has experimented with the best ways of managing tasks, I thought of sharing the biggest differences of Scrum and Kanban, as well as which I would choose for what process.

Agile project management

As you may know, implementing Agile practices can mean different things for different teams. There are various applications and frameworks to choose from as well as simply upholding the principles and creating your own rules. The manifesto does not specify any particular way of implementation, thus allowing you to choose which path to take.

Having said that, a few of implementations seem to be the most popular and today I want to explore 2 of them - Scrum and Kanban.

Scrum

Scrum is an Agile project management framework that organizes the teams work into iterations called Sprints. This approach defines specific roles and responsibilities for the team members, meetings to be taken as well as their duration. Teams working in fixed-time iterations to deliver the result.

Kanban

Kanban is another Agile framework that is based on visualizing the teams work on a Kanban board. Contrary to Scrum, there are no specific roles or meetings to be taken. Instead, the team plans on the demand basis. Plans when the backlog is empty and finishes an iteration when substantial value is delivered.

Choosing between Scrum and Kanban

When starting out with Agile, many of newcomers pose the question "So which should I choose?" Or even more often, we can hear something like "Which is the best?"

The answer to this question really depends on the team, but in most cases, Scrum is easier to start with. as it offers more rules and structure. Kanban on the other hand, is more suited to those that already have some experience and want to have more freedom over the process. And most teams will try both before deciding which is best for their needs.

So, what are the strengths of each? Let's see.

Choose Scrum For

Predictable delivery dates. Working with predefined Sprints allows to estimate more precisely.
Formal process to organize your team and project around.
Steady pace for delivery, planning, and all other activities.

Choose Kanban For

Continuous work that does not have predefined pace or delivery dates that must be followed.
Process visualization and monitoring on a Kanban Board with swimlanes and WIP limits.
Support or any client-related operations where there is a need to react quickly.

Here is a full story on why our development team chose to move from Scrum to Kanban. And if you are looking for Agile tools, here is a review of the best Kanban board software.