You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Kanban (Japanese 看板, signboard or billboard) is a lean method to manage and improve work across human systems. This approach aims to manage work by balancing demands with available capacity, and by improving the handling of system-level bottlenecks. — wikipedia
In Project and Product Management, Kanban utilises the power of visualisation to increase team efficiency and deliver value to the team and customers faster. A kanban board can be used to visualise work, limit work-in-progress, and maximise efficiency (or flow). Kanban boards use a board, cards, columns, and continuous improvement to help technology and service teams commit to the right amount of work, and get it done!
The main goal of a team using Kanban is to take cards/tickets from the commitment point(BACKLOG) to the delivery(DONE) point as fast as possible. The elapsed time between these points is called Lead Time. So we can say that the main goal here is to reduce the lead time as much as possible.
Understanding the Components of the Kanban framework and how they work is set to lead your team to better project workflows and product launches.
The image above describes the basic components of the Kanban framework which are;
Physical Kanban Boards are easier and does not need any technical skills to setup and is ideal for teams who are the same physical location, just with your white or black board, marker, stickies and eraser, you can have your Kanban board. However physical boards are not ideal for remote and software teams since team member(s) will at some point be distributed or remote.
kanban boards went through a digital transformation when the Kanban Methodology started gaining favour with Engineering and Software teams. Digital boards allow teams that do not share a physical office space to use kanban boards remotely and asynchronously. The electronic board has many advantages over the traditional board. Advantages include; ability to be used by remote/distributes teams, ability to customise to contain many features, ability to integrate with other engineering tools like Slack, Git, etc. To use an electronic Kanban Board, you will need a software( I will talk about my favourite Kanban Software — Jira from Atlassian and how to use it in my next article), a product or project Manager who will set it up and oversee things on a high level, assignees who will handle each task or deliverable.
In as much Kanban boards have undergone digital transformation, I still recommend you use both the traditional board and the digital board. The traditional or physical board will promote physical team communication at the workplace for team members who are at the same place. Actually, I still use it professionally alongside the digital Kanban Board.
Among the listed advantages, I find the self organising point very dear. As a project manager, I don’t always have to move the tickets myself, other team members are responsible for each task they have been assigned to and failure to move for example a ticket(s) that is supposed to be “IN LOCAL DEV” means that the she/he is not working on anything even when they are actually working. That sense of responsibility it gives everyone is something huge, and then it does not stop there, It goes further to be transparent for everyone to see, you even get alerts in your communication tools like Slack for every update on the board(digital board).
Oh wow, you made it to this point, thanks for taking out time to read. At this point, you must have understood what Kanban is and why it is very necessary for your software team. However, if you are interested in setting it up and using it for your team or any other question(s), you can send me a DM on twitter @tech_bella or send me an email on gmail. Don’t forget to leave comments in the response section regarding any other thing.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.