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
id doaj-f126b12fc4b74d498b0aa9dc0cf7a042
record_format Article
spelling doaj-f126b12fc4b74d498b0aa9dc0cf7a0422020-11-24T22:19:03ZengWroclaw University of Science and Technologye-Informatica Software Engineering Journal1897-79792084-48402017-03-01111415910.5277/e-Inf170102Experience Report: Introducing Kanban Into Automotive Software ProjectMarek MajchrzakŁukasz StilgerThe 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.http://www.e-informatyka.pl/attach/e-Informatica_-_Volume_11/eInformatica2017Art2.pdfkanbanleanautomotivescrum
collection DOAJ
language English
format Article
sources DOAJ
author Marek Majchrzak
Łukasz Stilger
spellingShingle Marek Majchrzak
Łukasz Stilger
Experience Report: Introducing Kanban Into Automotive Software Project
e-Informatica Software Engineering Journal
kanban
lean
automotive
scrum
author_facet Marek Majchrzak
Łukasz Stilger
author_sort Marek Majchrzak
title Experience Report: Introducing Kanban Into Automotive Software Project
title_short Experience Report: Introducing Kanban Into Automotive Software Project
title_full Experience Report: Introducing Kanban Into Automotive Software Project
title_fullStr Experience Report: Introducing Kanban Into Automotive Software Project
title_full_unstemmed Experience Report: Introducing Kanban Into Automotive Software Project
title_sort experience report: introducing kanban into automotive software project
publisher Wroclaw University of Science and Technology
series e-Informatica Software Engineering Journal
issn 1897-7979
2084-4840
publishDate 2017-03-01
description 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.
topic kanban
lean
automotive
scrum
url http://www.e-informatyka.pl/attach/e-Informatica_-_Volume_11/eInformatica2017Art2.pdf
work_keys_str_mv AT marekmajchrzak experiencereportintroducingkanbanintoautomotivesoftwareproject
AT łukaszstilger experiencereportintroducingkanbanintoautomotivesoftwareproject
_version_ 1725780318330290176