Experience Report: Introducing Kanban Into Automotive Software Project

• Autorzy: Majchrzak M. , Stilger L.

Identyfikatory

DOI

10.5277/e-Inf170102

• Języki publikacji: EN

Abstrakty

EN

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.

Słowa kluczowe

EN

kanban; lean; automotive; scrum; agile

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2017
• Tom: Vol. 11, nr 1
• Strony: 39--51
• Opis fizyczny: Bibliogr. 26 poz., tab., rys.

Twórcy

autor

Majchrzak M.

• Capgemini Polska

autor

Stilger L.

• Capgemini Polska

Bibliografia

• [1] T. Ohno, Toyota Production System: Beyond Large-Scale Production. Cambridge, MA: Productivity, 1988
• [2] J. Koplin, S. Seuring, and M. Mesterharm, “Incorporating sustainability into supply management in the automotive industry – the case of the Volkswagen AG,” Journal of Cleaner Production, Vol. 15, No. 11, 2007, pp. 1053–1062.
• [3] D.T.J. James P. Womack, “From lean production to the lean enterprise,” Harvard Business Review, apr 1994.
• [4] M. Poppendieck and T. Poppendieck, Lean Software Development: An Agile Toolkit. Boston, MA, USA: Addison-Wesley Longman Publishing Co., Inc., 2003.
• [5] D.J. Anderson, Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press, Apr. 2010, paperback.
• [6] H. Kniberg, Kanban and Scrum – Making the Most of Both. Lulu.com, 2010.
• [7] K. Petersen and C. Wohlin, “Measuring the flow in lean software development,” Software: Practice and Experience, Vol. 41, No. 9, 2011, pp. 975–996.
• [8] M. Host, B. Regnell, J.N. och Dag, J. Nedstam, and C. Nyberg, “Exploring bottlenecks in market-driven requirements management processes with discrete event simulation,” Journal of Systems and Software, Vol. 59, No. 3, 2001, pp. 323–332.
• [9] M. Staron and W. Meding, “Monitoring bottlenecks in agile and lean software development projects,” Product-Focused Software Process Improvement, 2011, pp. 3–16.
• [10] M.J. Michael Prokop, “Use of kanban in the operations team at spotify,” InfoQ, sep 2010.
• [11] H. Kniberg, Lean from the Trenches: Managing Large-Scale Projects with Kanban. Pragmatic Bookshelf, 2011.
• [12] M. Ikonen, E. Pirinen, F. Fagerholm, P. Kettunen, and P. Abrahamsson, “On the impact of Kanban on software project work: An empirical case study investigation,” in Engineering of Complex Computer Systems (ICECCS), 2011 16th IEEE International Conference on. IEEE, 2011, pp. 305–314.
• [13] P. Middleton and D. Joyce, “Lean software management: Bbc worldwide case study,” Engineering Management, IEEE Transactions on, Vol. 59, No. 1, 2012, pp. 20–32.
• [14] P. Middleton, A. Flaxel, and A. Cookson, “Lean software management case study: Timberline inc.” in Extreme Programming and Agile Processes in Software Engineering. Springer Berlin Heidelberg, 2005, pp. 1–9.
• [15] M. Majchrzak, Ł. Stilger, and M. Matczak, “Working with agile in a distributed environment,” in Software Engineering from Research and Practice Perspective, L. Madeyski and M. Ochodek, Eds. Polish Information Processing Society Scientific Council, 2014, pp. 41–54.
• [16] K. Beck and C. Andres, Extreme Programming Explained: Embrace Change, 2nd ed.Addison-Wesley Professional, 2004.
• [17] M. Robert C., Clean Code: A Handbook of Agile Software Craftsmanship, 1st ed. Upper Saddle River, NJ, USA: Prentice Hall PTR, 2008.
• [18] Atlassian, JIRA documentation, (2016). [Online].https://confluence.atlassian.com/display/ JIRA/JIRA+Documentation
• [19] Atlassian, Specification – confluence advanced editor, (2016). [Online]. http://confluence. atlassian.com/display/DOC/Specification+-+Confluence+Advanced+Editor
• [20] E. Shihab, C. Bird, and T. Zimmermann, “The effect of branching strategies on software quality,” in 2012 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ESEM, 2012, pp. 301–310. [Online]. http://doi.acm.org/10.1145/2372251.2372305
• [21] Atlassian, JIRA service desk documentation, (2016). [Online]. https://confluence.atlassian. com/servicedeskserver030/
• [22] Go2Group, Connect all, (2016). [Online]. http://www.go2group.com/connectall/
• [23] K.S. Rubin, Essential Scrum: A Practical Guide to the Most Popular Agile Process, 1st ed. Addison-Wesley Professional, 2012.
• [24] M. Cohn, Agile Estimating and Planning. Upper Saddle River, NJ, USA: Prentice Hall, 2005.
• [25] E.M. Rogers, Diffusion of Innovations, 5th ed. Simon and Schuster, 2003.
• [26] K.L. Jeffrey, The Toyota Way: 14 Management Principles From The World’s Greatest Manufacturer. McGraw-Hill, 2004.

Uwagi

PL

Opracowanie ze środków MNiSW w ramach umowy 812/P-DUN/2016 na działalność upowszechniającą naukę (zadania 2017).