Kanban in Software

Table of Contents

KANBAN IN SOFTWARE 6

ABSTRACT 6

Chapter 1: INTRODUCTION 6 1.1 Lean Thinking 8 1.2 Applying in Software Development 9 1.3 Kanban for Software 9 1.4 Scope of the study 11

Chapter 2: LITERATURE REVIEW 11 2.1 Lean Manufacturing vs. Lean Development 11 2.2 Applying Lean in Software Development 12 2.3 Kanban 13 2.4 Waterfall methodology 16

Chapter 3: Methodology 19

Chapter 4: ANALYSIS 21

Chapter 5:- Findings 24

Chapter 6:- Conclusions 25

Chapter 7:- References 25

List of Figures

Fig 1: Lean Principles in Software
Fig 2: Impact of Kanban in Software Development
Fig 3: kanban Card

Fig 4: Example of implementation of Kanban board

Fig 5: Waterfall methodology

List of Tables

Table 1: Comparison between Lean Manufacturing and Lean Development

Table 2: Comparison between Agile and Lean software engineering practices

Table 3: Nine aspects of project work

Table 4: Empirical evaluation of the Kanban with respect to the research framework

KANBAN IN SOFTWARE

ABSTRACT

The mission of software project management is to continuously achieve more and more successful projects. In the field of software development, the Kanban method has gained momentum recently, mostly due to its linkages to Lean Thinking. However, only a few empirical studies investigate the dynamics and impacts of Kanban on project success. The aim of this study is to improve the understanding on how Kanban impacts on software project work. For the purpose of the study, a framework is developed and empirically investigated in an experimental software R&D setting called Software Factory. The impact of Kanban is evaluated from nine theoretically derived perspectives. The qualitative findings indicate considerable positive support for the application of Kanban in the case setting. This bears direct managerial implications, which are addressed. The key implications

References: [1] J. Womack and D. Jones, “From lean production to the lean enterprise,” Harward Business Review, 1994. [2] S. P. Robbins, Essentials of organizational behaviour. San Diego State University, Prentice Hall, 2002. [4] A Guide to the Project Management Body of Knowledge, 4th ed.Pennsylvania, USA: Project Management Institute, Inc., 2008. [5] S. Raman, “Lean software development: Is it feasible?” in Proceedigns of the 17th Digital Avionics Systems Conference (DASC) ’98, vol. 1.The AIAA/IEEE/SAE, 1998, pp. C13/1–C13/8 vol.1. [6] J. Liker, The Toyota Way. New York, NY, USA: McGraw-Hill, 2004. [7] P. Middleton, “Lean software development: Two case studies,” Software Quality Journal, vol. 9, pp. 241–252, 2001. [8] M. Poppendieck and T. Poppendieck, Lean software development: An agile toolkit. Boston, Massachusetts, USA: Addison Wesley, 2003. [9] D. G. Reinertsen, The Principles of Product Development Flow: Second Generation Lean Product Development. Redondo Beach, CA, USA:Celeritas Publishing, 2009. [15] A. Alwardt, N. Mikeska, R. Pandorf, and P. Tarpley, “A lean approach to designing for software testability,” in AUTOTESTCON ’09. IEEE, 2009, pp. 178–183. [16] D. Boddy and D. Macbeth, “Prescriptions for managing change: A survey of their effects in projects to implement collaborative working between organizations,” International Journal of Project Management, vol. 18, no. 5, pp. 297–306, 2000. [17] D. Boddy, Managing Projects: Building and Leading the Team. Prentice Hall International UK Limited / Pearson Education, 2002. [19] B. Curtis, H. Krasner, and N. Iscoe, “A field study of the software design process for large systems,” Communications of the ACM, vol. 31, no. 11, pp. 1268–1287, 1988. [20] B. Boehm, “Software risk management: Principles and practices,” IEEE Software, vol. 8, no. 1, pp. 32–41, 1991. [21] D. Phan, D. Vogel, and J. Nunamaker, “The search for perfect project management,” Computerworld, vol. 22, no. 39, pp. 95–100, 1998. [22] J. Jurison, “Software project management: the manager’s view,” Communicationsof the AIS, vol. 2, no. September, 1999. [24] T. Hutchings, M. G. Hyde, D. Marca, and L. Cohen, “Process improvement that lasts: An integrated training and consulting method,” Communications of the ACM, vol. 36, no. 10, pp. 105–113, 1993. [26] V. Bullen and J. Rockart, A Primer on Critical Success Factors. Homewood, Illinois, USA: Dow Jones-Irwin, 1986. [27] S. Teasley, L. Covi, M. S. Krishnan, and J. S. Olson, “How does radical collocation help a team succeed?” in CSCW ’00: Proceedings of the2000 ACM conference on Computer supported cooperative work. New York, NY, USA: ACM, 2000, pp. 339–346. [29] W. W. Royce, “Managing the development of large software systems: Concepts and techniques,” in ICSE ’87: Proceedings of the 9th international conference on Software Engineering. Los Alamitos, CA, USA: IEEE Computer Society Press, 1987, pp. 328–338. [31] P. Abrahamsson, O. Salo, J. Ronkainen, and J. Warsta, Agile Software Development Methods: Review and analysis, ser. VTT Publications. Espoo, Finland: VTT Technical Research Centre of Finland, 2002, no. [34] K. Petersen, Implementing Lean and Agile software development in industry, ser. Doctoral Thesis No 2010:04. Sweden: Blekinge Instituteof Technology, School of Computing, 2010. [35] V. Kajaste and T. Liukko, Lean-toiminta. Tampere, Finland: Metalliteollisuuden Kustannus Oy, 1994. [37] V. Basili and A. Turner, “Iterative enhancement: A practical technique for software development,” IEEE Transactions on Software Engineering, vol. 1, no. 4, pp. 390–396, 1975. [38] P. Abrahamsson, “Unique infrastructure investment: Introducing the Software Factory concept,” Software Factory Magazine, vol. 1, no. 1,pp. 2–3, 2010. [39] F. Fagerholm, “Psychometric measurements in software development,” Software Factory Magazine, vol. 1, no. 1, pp. 12–13, 2010. [40] M. Q. Patton, Qualitative evaluation and research methods, 2nd ed. Sage, 1990. [41] M. Korkala and P. Abrahamsson, “Extreme programming: Reassessing the requirements management process for an offsite customer,” in EuroSPI, 2004, pp. 12–22. [43] W. Tichy, “Hints for reviewing empirical work in software engineering,” Journal of Empirical Software Engineering, vol. 5, no. 4, pp. 309–312, 2000. [44] M. H¨ost, B. Regnell, and C. Wohlin, “Using students as subjects: A comparative study of students and professionals in lead-time impact assessments,” Journal of Empirical Software Engineering, vol. 5, no. 3,pp. 201–214, 2000. [45] L. Madeyski, Test-driven development: An empirical evaluation of agile practice. Berlin Heidelberg: Springer–Verlag, 2010.