Experience Report: Introducing Kanban Into Automotive Software Project

The boundaries between traditional and agile approach methods are disappearing. A significant number of software projects require a continuous implementation of tasks without dividing them into sprints or strict project phases. Customers expect more flexibility and responsiveness from software vendo...

Full description

Bibliographic Details
Main Authors: Marek Majchrzak, Łukasz Stilger
Format: Article
Language:English
Published: Wroclaw University of Science and Technology 2017-03-01
Series:e-Informatica Software Engineering Journal
Subjects:
Online Access:http://www.e-informatyka.pl/attach/e-Informatica_-_Volume_11/eInformatica2017Art2.pdf
Description
Summary:The boundaries between traditional and agile approach methods are disappearing. A significant number of software projects require a continuous implementation of tasks without dividing them into sprints or strict project phases. Customers expect more flexibility and responsiveness from software vendors in response to the ever-changing business environment. To achieve better results in this field, Capgemini has begun using the Lean philosophy and Kanban techniques. \\The following article illustrates examples of different uses of Kanban and the main stakeholder of the process. The article presents the main advantages of transparency and ways to improve the customer co-operation as well as stakeholder relationships. The Authors try to visualise all of the elements in the context of the project. \\There is also a discussion of different approaches in two software projects. The article fokuses on the main challenges and the evolutionary approach used. An attempt is made to answer the question how to convince both the team as well as the customer, and how to optimise ways to achieve great results.
ISSN:1897-7979
2084-4840