Kanban basics from A-Z in IT outsourcing (Part 1)
The last 20 years have observed the booming and rapid adoption of Agile software development. Through our last post Agile software development at a glance, we know that Agile refers to a collection of lightweight frameworks and practices, like Scrum, XP and Kanban, that are widely-embraced due to their versatility and effectiveness.
Together with Scrum and XP, Kanban is the next commonly adopted practice in both on-shore and offshore software development outsourcing settings. The latest 12th Annual State of Agile report (2018) shows that the “use of Kanban grew from 50% to 65%” from 2016-2017 alone. Kanban is also believed to be the “best method for executing lean thinking in practice”. As a result, Kanban is one important Agile methodology that Axon Active has been applying since our inception in 2008.
Use of Kanban board provenly enhances software outsourcing teamwork.
What is Kanban? What are the benefits of using it? How to learn more about Kanban? This article will give you the answers to some of your most basic questions about Kanban, particularly in software outsourcing industry.
1. What does “Kanban” mean?
The word “Kanban” comprises “kan” and “ban”, which literally mean “visual” and “card” (“board”, or “signal”) in Japanese. Generally, Kanban means visual board, signboard or visual signal. Kanban methodology is widely known for the use of Kanban board – which makes use of visuals, or cards on a white board or glass wall. In IT outsourcing (ITO) industry, Kanban is increasingly employed to enhance the effectiveness of Scrum and other Agile methodologies.
2. What is Kanban board?
A basic Kanban board includes three columns, based on 3 basic types of tasks: to-do, doing, and done. Kanban board gives visuals of how tasks progress in the development cycles as they move from column to column.
Kanban board is not confined to one single team or one iteration. In fact, it promotes the visualization of the whole workflow and encourages the collaboration of individuals in a team and collaboration of multiple teams across many functions and organizations.
Basic Kanban board version
“The power of Visualization” Scrum Breakfast Vietnam event in Da Nang (Vietnam) by Axon Active
3. Elements of a Kanban board
Elements of a basic Kanban board
Items in To-do column is called backlogs. Backlogs are tasks, or to-dos, that clients and development teams have in mind that need to be completed. Backlogs can be a breakdown of a bigger ambitious plan for the software, and there is no upper limit for backlogs in To-do column.
Some companies afford a Stories or User Stories column before To-do to give development teams better pictures of where the backlogs come from.
Items in Doing column is called works-in-progress, or WIPs. Unlike backlogs which are not constrained by an upper limit, WIPs needs one to make the whole process work efficiently.
In practice, people may habitually start off a project with 10 tasks, but they normally fail to get all 10 tasks to Done in the end. Delays in software development cost both clients and development teams time, money and other resources, while hurting client’s trust. This is when limits on WIP come to the rescue. WIP limit sets the maximum work items that a developer is handling and to accomplish at a time.
Benefits of WIP limits
Successful application of WIP limits guarantees development teams two seeable benefits:
- It encourages monotasking mindset and avoid multitasking – which wastes the team 50% more time in generating 50% more mistakes. Time and time again, studies by Stanford University, Iowa State University, and McGill University show monotasking workers score much higher indexes of productivity and performance than their peers. Obviously, using Kanban allows teams to deliver products of much higher quality and boost client’s trust in team’s capabilities.
- WIP limits help a team-member to stop starting new tasks and start finishing pending WIP, normally postponed due to unexpected obstacles (“bottlenecks”). In Scrum work environments, Kanban is usually incorporated; and in such a case, bottlenecks are easily revealed through daily stand-up meetings (daily Scrum) and resolved much more fruitfully with the help of other team members or whole team’s effort.
Advice of Axon Active expert
According to Scrum Alliance expert and Axon Active’s CIO Sebastian Sussmann (2019), it is important to note that a board without WIP limits in Doing is not a Kanban board. With the use of WIP limits, development team leaders and members can quickly revisit the team’s most valuable work and redirect their focus on the most important tasks at hand.
And because of this, Axon Active’s ICT team has applied Kanban over the years to develop and maintain some of the most stable and secure offshore IT infrastructures. This enables our development teams to solely focus on creating values for our clients.
In certain contexts, Doing can be jazzed up with smaller columns like Review, Deployment, or Testing, to help the teams become aware of work-progress in much more details. Columns like Pending can also be created for items that stumble upon obstacles that are not inclusive in the team’s scope-of-work and decision-making power.
An example of advanced Kanban board
Items in Done has no special name; we just simply call it Done items. Once the items are moved to Done, that means they are completely accomplished and there’s no future follow-ups or turning-back to previous columns.
A few more columns in Done like Production, Delivery, or Approval can come in handy for teams of sales, marketing, or events functions. It is due to the fact that the needs to follow up production of marketing merchandise, delivery of products from one place to another, or management approval for production designs and costs are typically required.
3.4 Other elements and relevant terms
- Swim lanes: Another way to visualize person-in-charge (or department-in-charge) and their tasks is by dividing the Kanban board with horizontal “swim lanes”. Swim lanes help managers easily spot each team member’s individual workload and how their work “flow” goes.
- Avatar: a visual representation of the person-in-charge of particular tasks. Color code for different members’ cards can also be used.
- Lead time: the total time length from when a task (ticket) is created in To-do until completed (Done).
In fact, lead time can be calculated using Little’s Law formulae (below, only for stable system with no bottlenecks – which influence the throughput). The law was originally invented by MIT Professor John Dutton Conant Little for service system but has been widely-applied in software development outsourcing industry.
- Cycle time: the time counted manually by teams since a ticket starts being worked on until it’s finished. It makes product deliveries predictable for both teams and clients.
Kanban methodology originated from the Toyota Production System (TPS), which was invented by Toyota manager Taiichi Ohno in the late 1940s – early 1950s. TPS was a model borrowed from supermarkets’ logistical control system, aiming to reduce costs of excessive inventory by managing stocks at levels sufficient and in time for customers’ purchasing. TPS, or just-in-time (JIT) manufacturing, did so through the use of cards to keep managers abreast with automotive in-stock supplies. It is interesting to know that till this day, JIT manufacturing model is still favored by Toyota, Harley Davidson, Dell, ZARA, Walmart, Oral-B, and McDonald’s.
Taiichi Ohno (on front cover) and his book, Evolution of Toyota Production System (published in 2017)
The booming of Kanban in software industry is marked by the publication of two books.The undeniable success of Kanban application in automotive manufacturing in the 1950s had convinced David J. Anderson to adapt Kanban to the software industry in 2004. When working on a project with Microsoft’s IT department, he had introduced Kanban to the team to help them visualize their workflow. This positive experience at Microsoft has led him to apply Kanban at Bill Gates’ Corbis from 2006-2007 (see Recommendations for Kanban learning resources section below for his free downloadable presentation on this occasion).
- Scrumban – Essays on Kanban Systems for Lean Software Development by former Microsoft’s software development manager Corey Ladas (published in 2009): Believing Kanban could improve on Scrum, he introduced Scrumban – a hybrid fusion of Scrum and Kanban, in this book.
- Kanban: Successful Evolutionary Change for Your Technology Business by David J. Anderson (published in 2010)
Here go the authors and their books that mark the booming of Kanban
Corey Ladas, former Microsoft’s software development manager (Image reproduced from Corey Ladas’ Twitter account)
Scrumban – Essays on Kanban Systems for Lean Software Development by Corey Ladas (published in 2009)
David J. Anderson, now chairman of Lean Kanban Inc and Lean Kanban University in Seattle (USA) (Image reproduced from David J. Anderson’s Amazon author page)
Kanban: Successful Evolutionary Change for Your Technology Business by David J. Anderson (published in 2010)
Axon Active’s Scrum Breakfast Vietnam event, “The Real Life of Scrumban team”, enables workshop attendees to have insightful understanding of how Scrumban teams work in practice.
5. Kanban methodology versus Kanban board
There are two most important features of the Kanban methodology:
- visualize the big picture of the entire workflow and business value chain from start to end, i.e. from even before the development process happens (such as business problems of customers that give rise to the need of developing requested software products), through the development period, to whether the post-development outputs bring any relevant business values for customers
- quickly identify the entire workflow and exactly where the problems arisen to tackle them in a timely manner; by this, the flow is optimized.
Although Kanban board helps carry out these important features of Kanban methodology, it is not Kanban methodology.
6. Local optimization and Global Sub Optimization
6.1 Local optimization
Kanban methodology demands users to uptake a lean mindset that reduces wastes and increase delivery outputs in quantity and quality on both local and global scales. If each team in a local outsourcing company can visualize its workflow and the individual workflow of team members and quickly determine the problems and resolutions to solve the problems, we may say that company can optimize its work effectively on the local scale (or local optimization).
6.2 The reality of IT outsourcing situation
However, ITO settings oftentimes – if not always, take place inter-continentally. This stems the need for global solution. Well, imagine a bike with broken brake and bent wheels with a pristine frame and a decent bell. The part of the frame and the bell are doing good jobs, but the whole bike cannot work as originally intended. Now, imagine a software that is good on its own, but doesn’t bring any values to customers’ business or help solve their clients’ problems.
This analogy shows that looking merely at the local scale won’t be efficient enough to work in an international business context, especially that of ITO industry.
6.3 Global sub-optimization
The Kanban methodology asks the users to also take into consideration the interactions and synchronization of itself and the bigger system where software development is just a single phase of its. This whole system can involve many departments:
- the customers where the software being developed comes into play
- the customers’ clients who use the product after the development process is over
- and of course, the workings of the development teams and any other factors (or departments) that brings about the success of the software being developed.
Once there is local optimization in each part of the system on the local scale, it will naturally lead to global effectiveness of the whole value chain, also called global sub optimization.
Axon Active – We do agile, we speak agile.
In the next article, Kanban basics from A-Z in IT outsourcing (Part 2), we are going to explore the characteristics, values, and core principles and practices of Kanban methodology. We will also discuss the motivation for Kanban use, as well as challenges when using Kanban among the practitioners. 🙂
Axon Active – the offshore partner you’re looking for
Axon Active is a tech firm from Switzerland with years of experience in developing agile software and applications for web and mobile platforms. We are the only organization in Vietnam offering official Scrum Alliance’s Certified ScrumMaster and Certified Scrum Product Owner certifications. The exclusive Scrum and agile coaching sessions have enabled distinguished clients like Soreco and CRIF, among others, to successfully adopt Agile working methodologies and observe major digital transformation over the years.
Looking for a well-versed, reliable offshore software outsourcing partner? Learn more about how to start software development outsourcing and let us know how we can help!
1. Alex Novkov, & Shane Hastie. (May 16, 2018). Kanban Step-by-Step Guide: from 3-Columns to Flexible Board Design. Retrieved from InfoQ.com
2. Alexandra Hall. (2018). Intro to Kanban Boards, the Highly Visual Project Management Method. Retrieved from Business 2 Community
3. Constantin Hofmann, Sebastian Lauber, Benjamin Haefner, & Gisela Lanza. (2018). Development of an agile development method based on Kanban for distributed part-time teams and an introduction framework. 8th Conference on Learning Factories 2018 – Advanced Engineering Education & Training For Manufacturing Innovation. 23, pp. 45-50. Germany: Institute of Production Science, Karlsruhe Institute of Technology, Germany. Retrieved from Science Direct
4. David J Anderson. (n.d.). David J Anderson. Retrieved from Amazon.com
5. Hamzah Alaidaros, Mazni Omar, & Rohaida Romli. (2018). Towards an Improved Software Project Monitoring Task Model of Agile Kanban Method. (School of Computing, Universiti Utara Malaysia, Ed.) International Journal of Supply Chain Management, 7(3), 118-125. Retrieved from Microsoft Academic
6. Henrik Kniberg. (2014). Connecting People and Technology – TDC2014. Retrieved from TrondheimDC
7. Henrik Kniberg. (2014). The resource utilization trap. Retrieved from Crisp Agile Academy
8. History-biography. (2018). Taiichi Ohno. Retrieved from History-biography.com
9. Howard Lei, Farnaz Ganjeizadeh , Pradeep Kumar Jayachandra, & Pinar Ozcan. (2017). A statistical analysis of the effects of Scrum and Kanban on software development projects. Robotics and Computer-Integrated Manufacturing, 43, 59-67. Retrieved from Science Direct
10. Ikonen, M., Pirinen, E., Fagerholm, F., Kettunen, P., & Abrahamsson, P. (2011). On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation. 2011 16th IEEE International Conference on Engineering of Complex Computer Systems (pp. 305-314). Helsinki, Finland: IEEE. doi:10.1109/ICECCS.2011.37
11. it-agile.de. (2013). Stop starting, start finishing. In it-agile.de, Stop starting, start finishing. Germany: it-agile GmbH.
12. Jack Wilson. (n.d.). Examples of Successful JIT Systems – Toyota, Dell, and Harley Davidson. Retrieved from Bright Hub PM
13. Kanbanize. (n.d.). Cumulative Flow Diagram for Best Process Stability. Retrieved from Kanbanize
14. Kanbanize. (n.d.). Kanban Explained for Beginners. Retrieved from Kanbanize
15. Kanbanize. (n.d.). Kanban: Lead Time vs Cycle Time – Details Explained. Retrieved from Kanbanize
16. Kent McDonald. (n.d.). What is Kanban? Retrieved from Agile Alliance
17. Klaus Leopold. (2017). Practical Kanban: From Team Focus to Creating Value. LEANagility Press. Poland: Amazon Fulfillment.
18. Laurie Vazquez. (2016). Why monotasking is the new multitasking. Retrieved from Big Think
19. Magdalena Maneva, Natasa Koceska, & Saso Koceski. (2016). Introduction of Kanban methodology and its usage in software development. Retrieved from Microsoft Academic
20. M.Raju Naik, E.Vijaya Kumar, & B.Upender Goud. (March 2013). Electronic Kanban System. International Journal of Scientific and Research Publications, 3(3), 1-6. doi:2250-3153
21. Mark Yang. (2016). Lecture 6-1 The Overview of Little’s Law. Retrieved from YouTube
22. Maureen Tanner, & Marcelo Dauane. (2017). The Use Of Kanban To Alleviate Collaboration And Communication Challenges Of Global Software Development. (Eli Cohen, Ed.) Issues in Informing Science and Information Technology Education, 14, 177-197. Retrieved from Informing Science
23. Michael Kitakis. (2017). Case study: How Premier Fixtures uses Japanese kaizen to improve efficiency and increase capacity. Retrieved from Japan Products
24. Moira Alexander. (2017). Kanban: The benefits of using this agile PM framework. Retrieved from TechRepublic
25. Muhammad Ovais Ahmad, Jouni Markkula, & Markku Oivo. (2016). Insights into the Perceived Benefits of Kanban in Software Companies: Practitioners’ Views. International Conference on Agile Software Development (pp. 156-168). Oulu, Finland: M-Group, University of Oulu. doi:10.1007/978-3-319-33515-5_13
26. Nancy Van Elsacker Louisnord. (May 2, 2018). Kanban, The World’s Oldest New Trend. Retrieved from Business 2 Community
27. Osama Al-Baik, & James Miller. (2015). The kanban approach, between agility and leanness: a systematic review. Empirical Software Engineering, 1861-1897. doi:10.1007/s10664-014-9340-x
28. Planview Leankit. (n.d.). 7 Lean Metrics To Improve Flow. Retrieved from Planview Leankit
29. Sergey Laptick. (2016). How & Why to Use the Kanban Methodology for Software Development. Retrieved from SitePoint Pty. Ltd
30. Simon Buehring. (2019). The 4 Kanban principles: A visual guide. Retrieved from Knowledge Train
31. Smartsheet. (2016). What is Kanban?. Retrieved from Smartsheet
32. Stefan Roock. (2010). Kanban: Definition of Lead Time and Cycle Time. Retrieved from Stefan Roock
33. Taiichi Ohno. (2017). Evolution Of Toyota Production System, paperback . Retrieved from Amazon.com
34. The Standish Group International, Inc. (2010). Modernization: Clearing A Pathway To Success. From The Standish Group International, Inc.
35. TradeGecko. (2018). Zara supply chain analysis – the secret behind Zara’s retail success. Retrieved from TradeGecko Pte. Ltd
36. VersionOne CollabNet. (n.d.). What Is Kanban? An Introduction to Kanban Methodology. Retrieved from VersionOne CollabNet
37. Yoshitaka Shiotsu. (July 9, 2018). Introduction to Kanban: What Software Developers Can Learn from a Japanese Manufacturing System. Retrieved from Business 2 Community