Kanban

Scrumban User Cheat Sheet

SB-Cheat-Sheet-banner

The last of my cheat sheets (so far) comes in the form of Scrumban. A mixed Agile approach that aims to merge the two most popular practices Scrum and Kanban. While some say that this is the most unstable and changing approaches of the three, there are still some things that stay the same no matter the application.

So dig in, enjoy and let me know if you think anything else should be added!

Read More

Kanban User Cheat Sheet

K-Cheat-Sheet-banner

Ever felt lost about the Kanban terms or wanted to have a quick check whether you are doing it right? Below is another handy Agile framework cheat sheet combined just for that! Check it for a quick reminder on how to move forward.

Kanban-Cheat-Sheet

Read More

All You Need To Know About: Kanban

All About Kanban

In the spirit of continuing with the article roundup, this week I present to you everything related to Kanban. If you are still wondering how push and pull differs or what does WIP limit stand for, this one is for you. So take a look and dive into the world of self-organization and progress.

The Basics

Just starting with one of the more flexible Agile approaches? No worries we’ve got you covered. Learn the basics with 5 steps to start doing Kanban, configure your work space after reading Setting Up a Kanban Board and start adding work items with the knowledge of 5 Ways to Execute Kanban Task Cards.

Once your process is all set up and running, learn to measure the progress with two most popular Kanban reports:

Read More

Getting Things Done with Kanban

Startup Stock PhotosWe all strive to be the most effective in both our professional and business lives and there are plenty of ways to get there. To do lists, sticky notes, a constant flow of e-mails as well as methods to reduce our stress levels and increase productivity. Getting Things Done is a method that does just that and aims to create a work pace that frees up the mind and lets you focus on what is actually important instead of just being stressed. And while the original GTD talks about a filing system and physical lists, it is hard to miss the similarities to Kanban approach and wonder if it could enhance this process.

Getting Things Done or GTD is a concept introduced by David Allen in the early 2000s. In his quest to minimize the stress levels created by the constant flow of work, projects and emails, Allen developed a system to get us concentrated on just one thing at a time instead of keeping a running tab of things to do. To achieve this, he suggests one simple thing – taking the tasks out of your head and writing them down.

Most of the stress in our lives comes from uncertainty of the outcome and having a running list of things to do in our heads is the epithamy of that. Therefore GTD says you should get rid of that and instead write all of your tasks down, understand the desired outcome and then write down the next step that is going to help you achieve the end goal. This way, you can focus on one thing at a time, while knowing nothing will be forgotten.

Read More

Tips & Tricks On Using Agile

tips-tricksTaking on Agile can be a tough challenge, especially if you have no previous experience with it and have no one to coach you. The good news, however, are that all it takes is time and determination to take over and understand. To make that process more smooth for both you and your team, we came up 17 tips and tricks. Use them to reach your goals sooner and more easily.

Read More

Choose The Right Agile Method

Choose-Agile-method for posting

The next big question after deciding to go Agile is deciding which of the methods is right for you- will you go with Scrum, SoS or SAFe? While this decision is not an easy one and will take careful considerations, there are some aspects to each of the method that can help you along the way. Below you will find our easy 3 step process that will guarantee you consider the right options from the start.

 

Choose-Agile-method

For more helpful Agile cheats and tips see The Ultimate Agile Guide.

 

Read More

Transitioning to Agile: Running Effective Meetings

Startup Stock Photos

Ah, meetings.. The thing we all hate, yet cannot live without. No matter what project management method your team is using, meetings are always a part of it one way or another. And while most of us associate these gatherings with long and strenuous activities that often yield little to no actual results, when transitioning to Agile you should keep an open mind.

The whole idea of Agile is being effective and eliminating practices that create waste. So when talking about meetings there is no surprise, the same rules apply. No matter the chosen method, all meetings have to have a clear purpose, duration and must yield a result. So to get the Agile meetings right from the start, you should understand that contrary to other practices every single meeting has a very specific value to add to the table.

  • Understand the reason of the meeting

Depending on your chosen Agile method, the number, complexity and scheduling of these meetings will differ. Scrum meetings are planned based on the length of iterations, while Kanban meetings are held once the team feels the need for them. However, no matter which method you have chosen, the first thing you will have to do is to understand the purpose behind each of the accompanying meetings.

More often than not, the meetings will be very distinctive and specific – sprint planning is only held for planning tasks of that one sprint. Daily standup only discusses the results and plans and so on. While at first, it may seem hard to keep track of all the different rituals, it is understanding the reason behind them that will help pull you out of the dark. Ultimately this will not only help you, but will also make your teams transition a lot smoother.

  • Go by the rules

Another thing that might be difficult to do at first and will possibly slip your mind later, is that the meeting rules and rituals are there for a good reason. It might seem silly to be standing during daily Scrum for the first few times, but this will help to keep the meeting short and on point. And while planning the work for only a two week iteration could seem very irresponsible and short sighted, you will later realize this way of working cuts a lot of planning time in the long run.

Therefore make sure to stay along the lines of the meeting rituals, especially in the beginning. They will create right practices and rituals within your organization and that will help you avoid overcrowded, extended and useless gatherings. And if you still feel that some rituals don’t work for you after you’ve completed a good number of iterations, you can change them. Only then you will have experience and will actually understand what will work for you.

  • Have a clear goal to be achieved

Lastly, before going into any meeting, make sure to have a very clear goal and a plan to achieve it. It may be to show your client the results of a sprint and to get an informative feedback in a review meeting or it might be as simple as catching up with the team and logging the progress in the daily Scrum. No matter the type of meeting, without understanding what you are trying to get out of it, you chances of success are slim.

In order to avoid the possibility of making your meetings redundant and fruitless, take some time beforehand and draw a mini plan to understand what you are trying to achieve, who should be involved and how long it might take. By doing that you will save your team a great deal of time and frustration as well as will achieve your goals faster.

Agile meetings and meetings from any other project management practice are not much different – they are all set up to improve project success. However, as with anything else, Agile tries to eliminate as much waste as possible. So to make you do just that, take note of why those meetings were set up and fulfill their requirements as best as you can.

Happy meeting!

Read More

Scrum vs. Kanban vs. Scrumban – What’s the difference?

Scrum-Kanban-Scrumban for postingUnderstanding how do Agile methodologies differ can be a daunting task. Some get confused with the overwhelming amount of information, others are disappointed with the lack of clarity.

Ideal way is to have everything at single glance and compare pros and cons in each framework. To make sure it is easy enough, we present a short and clear table listing the main differences and similarities between Scrum, Kanban and Scrumban.

 

Scrum-Kanban-Scrumban

 

For more helpful Agile cheats and tips see The Ultimate Agile Guide.

 

Read More

Agile Hierarchy – How Are The Methods Related?

Have your ever got lost between all of the Agile practices and frameworks? With the methods evolving, changing and appearing constantly, it can get difficult to understand, how they evolved and turned into the form of today. Therefore we decided to make this quick cheat sheet for anyone wondering if SoSKanban and XP have anything in common.

Agile-Hierarchy

For more helpful Agile cheats and tips see The Ultimate Agile Guide.

Read More

5 Tips For A Smooth Agile Transition

tips

Whether you are taking Agile on for the very first time, coming back to it after a previous attempt or simply going from one Agile method to another, there are some key things to remember if you want to keep the transition smooth. Check out our 5 key tips on a smooth Agile transition to end up on the right side of change.

  • Understand what is ahead

As with any change in life, first and foremost, you have to take some time and understand what is ahead. We are sure you have not chosen your new method impulsively and put in time and thought making sure it was the right fit. So do not cheat yourself and take some time aside to really understand how this change is going to affect your processes, your team and your company. It may seem silly but having a clear future vision in your head will help you better understand and guide the transition once it takes place.

Read More