Download presentation

Ivan Ivanov

Ivan Ivanov

Got his first computer, a ZX-Spectrum, as a child. Took interest in programming then and thus decided on his future career. Altai State University graduate (Software and Computer Science). Worked as an Oracle-developer in a commercial bank for the first two years after graduation. Java-programmer since 2008. At the moment Senior expert on software development in T-Systems CIS now.

German Kryukov

German Kryukov

A graduate with honours of St.Petersburg State University, department of Mathematics and Mechanics. A software developer since 2002, has been involved in the development of various commercial applications in the area of modeling, supply chain planning and logistics. Joined T-Systems in 2010 as a Senior Developer and worked his way up to Team Leader.

In 2011 German and his project manager were the first to introduce the Kanban practices into their project.

Presentation: How we applied Kanban to the project

The word “Kanban” comes from production, and to be more precise, from Toyota production system. Literally, this term means “visual card” or “visual board”. At Toyota manufacturing plants such cards are used to limit the number of parts to be produced in order not to overload warehouses and workplaces.

Kanban as a methodology or more as an approach to change management in software development applies a similar principle: the amount of work-in-progress is limited. A new task is performed only if the preceding one has moved into the next stage of development, for example, testing. This principle is implemented with the use of Kanban board, divided into several columns, each of which has a limit on the number of cards which can be put in columns.

In the report we shall give attention to our experience of introducing Kanban into an industrial project. We’ll talk about our aims and the reasons we have opted for Kanban and not some other popular Agile methodology. We shall describe the tools which we use to maintain the process, its development from the beginning of implementation to the present time. We’ll share the results, which we were able to achieve through using the new practice and our personal impressions.

However, there is no one-size-fits-all Cloud, and it is up to each business to decide how much change is tolerable and decide how far into the Cloud to step. Adoption of Cloud is a personal journey that no two businesses will undertake in exactly the same way. Wherever a business may land on the Cloud spectrum, there are benefits to be had.