Skip to main content
SpringerLink
Log in

Towards Lean Thinking in Software Engineering

  • Chapter
  • First Online:
Lean Software Development in Action

  • 2175 Accesses

Abstract

Lean concepts are not completely alien to software development. To show that Lean ideas already influenced past approaches, we briefly look at 21 of them and categorize them according to three perspectives: value, knowledge, and improvement. Additionally, as an example that also single Lean ideas already influenced the software engineering practice, this chapter presents two examples of how the “pull” concept was used to address the value perspective.

Quod potest fieri sufficienter per unum, superfluum est si per multa fiat.

(If a thing can be done adequately by means of one, it is superfluous to do it by means of several)

Thomas Aquinas, Summa Contra Gentiles, Ch. 70

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 54.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    In fact, for almost all the approaches, one could say that they contribute to all three perspectives, because the three perspectives influence each other. For example, a better understanding of the production processes helps to increase the delivered value, constant improvement also improves the ability to collect and reuse knowledge, and so on.

References

  1. Abran, A., Moore, J.W., Bourque, P., Dupuis, R. (eds.): Guide to the Software Engineering Body of Knowledge. IEEE Computer Society, Los Alamitos (2004)

    Google Scholar 

  2. Ambler, S.W.: Disciplined agile delivery and collaborative devops. Cutter IT J. 24(12), 18–23 (2011)

    Google Scholar 

  3. Ambler, S.W., Lines, M.: Disciplined agile delivery: an introduction. IBM Software Design and Development, Thought Leadership White Paper. Online: http://public.dhe.ibm.com/common/ssi/ecm/en/raw14261usen/RAW14261USEN.PDF (2011). Accessed 3 May 2014

  4. Ambler, S.W., Lines, M.: Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise. IBM Press Series. IBM Press, Upper Saddle River (2012)

    Google Scholar 

  5. Basili, V.R.: The experience factory and its relationship to other improvement paradigms. In: Sommerville, I., Paul, M. (eds.) Proceedings of the European Software Engineering Conference (ESEC). Lecture Notes in Computer Science, vol. 717. Springer, Berlin (1993)

    Google Scholar 

  6. Basili, V.R., Rombach, H.D.: Tailoring the software process to project goals and environments. In: Proceedings of the International Conference on Software Engineering (ICSE). IEEE Computer Society Press, Monterey (1987)

    Google Scholar 

  7. Basili, V.R., Caldiera, G., McGarry, F., Pajerski, R., Page, G., Waligora, S.: The software engineering laboratory: an operational software experience factory. In: Proceedings of the International Conference on Software Engineering (ICSE). ACM, Melbourne (1992)

    Google Scholar 

  8. Basili, V.R., Caldiera, G., Rombach, H.D.: The goal question metric approach. In: Marciniak, J.J. (ed.) Encyclopedia of Software Engineering, vol. 1. Wiley, New York (1994)

    Google Scholar 

  9. Basili, V.R., Heidrich, J., Lindvall, M., Munch, J., Regardie, M., Trendowicz, A.: Gqm+Strategies — aligning business strategies with software measurement. In: Proceedings of the International Symposium on Empirical Software Engineering and Measurement (ESEM). IEEE Computer Society, Madrid (2007)

    Google Scholar 

  10. Beck, K.: Extreme Programming Explained: Embrace Change. Addison Wesley, Reading (1999)

    Google Scholar 

  11. Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R.C., Mellor, S., Schwaber, K., Sutherland, J., Thomas, D.: Manifesto for agile software development. Online: http://www.agilemanifesto.org (2001). Accessed 4 Dec 2013

  12. Becker, S.A., Bostelman, M.L.: Aligning strategic and project measurement systems. IEEE Softw. 16(3), 46–51 (1999)

    Article  Google Scholar 

  13. Boehm, B.W.: A spiral model of software development and enhancement. IEEE Comput. 21(5), 61–72 (1988)

    Article  Google Scholar 

  14. Boehm, B.W.: Software risk management: principles and practices. IEEE Softw. 8(1), 32–41 (1991)

    Article  Google Scholar 

  15. Boehm, B.W.: Spiral development: experience, principles, and refinements. Technical Report CMU/SEI-2000-SR-008, Carnegie Mellon University, Software Engineering Institute, Pittsburgh (2000)

    Google Scholar 

  16. Boehm, B.W., Papaccio, P.N.: Understanding and controlling software costs. IEEE Trans. Softw. Eng. 14(10), 32–68 (1988)

    Article  Google Scholar 

  17. Briggs, R.O., Grünbacher, P.: Easywinwin: managing complexity in requirements negotiation with gss. In: Proceedings of the Annual Hawaii International Conference on System Sciences (HICSS), vol. 1. IEEE Computer Society, Big Island (2002)

    Google Scholar 

  18. Chrissis, M.B., Konrad, M., Shrum, S.: Cmmi: Guidelines for Process Integration and Product Improvement. The SEI Series in Software Engineering. Addison-Wesley, Boston (2003)

    Google Scholar 

  19. Coad, P., Luca, J.D., Lefebvre, E.: Java Modeling Color with UML: Enterprise Components and Process. Prentice Hall PTR, Upper Saddle River (1999)

    Google Scholar 

  20. Cockburn, A.: Crystal Clear a Human-Powered Methodology for Small Teams. Addison-Wesley, Boston (2004)

    Google Scholar 

  21. Collins: Collins English Dictionary — Complete & Unabridged, 10th edn. HarperCollins. Online: http://www.collinsdictionary.com (2009). Accessed 4 Dec 2013

  22. Crosby, P.B.: Quality is Free: The Art of Making Quality Certain. New American Library, New York (1979)

    Google Scholar 

  23. Deming, W.E.: Out of the Crisis. Massachusetts Institute of Technology Centre for Advanced Engineering Study (MIT-CAES), Cambridge (1982)

    Google Scholar 

  24. Deming, W.E.: Quality, Productivity, and Competitive Position. Massachusetts Institute of Technology Centre for Advanced Engineering Study (MIT-CAES), Cambridge (1982)

    Google Scholar 

  25. Fenton, N.E., Pfleeger, S.L.: Software Metrics: A Rigorous and Practical Approach, 2nd edn. PWS Publishing, Boston (1998)

    Google Scholar 

  26. Fowler, M., Beck, K., Brant, J., Opdyke, W., Roberts, D.: Refactoring: Improving the Design of Existing Code. Addison-Wesley Object Technology Series. Addison-Wesley Professional, Reading (1999)

    Google Scholar 

  27. Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley Professional, Reading (1994)

    Google Scholar 

  28. Highsmith, J.A.: Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. Dorset House Publishing, New York (1999)

    Google Scholar 

  29. Humble, J., Farley, D.: Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation. Addison-Wesley Professional, Upper Saddle River (2010)

    Google Scholar 

  30. Humphrey, W.S.: Introduction to the Personal Software Process. Addison-Wesley Professional, Reading (1996)

    Google Scholar 

  31. Hüttermann, M.: DevOps for Developers. Apressus Series. Apress, New York (2012)

    Book  Google Scholar 

  32. Juran, J.M.: Juran on Leadership for Quality: An Executive Handbook. Free Press, New York (1989)

    Google Scholar 

  33. Kaplan, R.S., Norton, D.: The balanced scorecard: measures that drive performance. Harv. Bus. Rev. 70(1), 71–79 (1992)

    Google Scholar 

  34. Kasse, T.: Practical Insight into CMMI. Artech House Computing Library. Artech House, Boston (2008)

    Google Scholar 

  35. Martin, J.: Rapid Application Development. Macmillan Publishing, New York (1991)

    Google Scholar 

  36. Nyfjord, J., Kajko-Mattsson, M.: Commonalities in risk management and agile process models. In: International Conference on Software Engineering Advances (ICSEA). IEEE Computer Society, Cap Esterel (2007)

    Google Scholar 

  37. Ōno, T.: Toyota Production System: Beyond Large-Scale Production. Productivity Press, Cambridge (1988)

    Google Scholar 

  38. Padayachee, K.: An interpretive study of software risk management perspectives. In: Proceedings of the Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists on Enablement Through Technology (SAICSIT). South African Institute for Computer Scientists and Information Technologists, Port Elizabeth (2002)

    Google Scholar 

  39. Pande, P.S., Neuman, R.P., Cavanaugh, R.R.: The Six Sigma Way: How GE, Motorola, and Other Top Companies are Honing Their Performance. McGraw-Hill Education, New York (2000)

    Google Scholar 

  40. Paulk, M., Curtis, B., Chrissis, M.B., Averill, E.L., Bamberger, J., Kasse, T.C., Konrad, M.D., Perdue, J.R., Weber, C.V., Withey, J.V.: Capability maturity model for software. Technical Report CMU/SEI-91-TR-24, Carnegie Mellon University, Software Engineering Institute, Pittsburgh (1991)

    Google Scholar 

  41. Poppendieck, M., Poppendieck, T.: Lean Software Development: An Agile Toolkit. Addison-Wesley Professional, Boston (2003)

    Google Scholar 

  42. Rus, I., Lindvall, M.: Knowledge management in software engineering. IEEE Softw. 19(3), 26–38 (2002)

    Article  Google Scholar 

  43. Schnabel, I., Pizka, M.: Goal-driven software development. In: Proceedings of the Annual IEEE/NASA Software Engineering Workshop (SEW). IEEE Computer Society, Columbia (2006)

    Google Scholar 

  44. Schwaber, K.: Agile Project Management with Scrum. Microsoft Press, Redmond (2004)

    Google Scholar 

  45. Selby, R.W. (ed.): Software Engineering: Barry W. Boehm’s Lifetime Contributions to Software Development, Management, and Research. Practitioners Series. Wiley, Hoboken (2007)

    Google Scholar 

  46. Shewhart, W.A., Deming, W.E.: Statistical Method from the Viewpoint of Quality Control. Dover Books on Mathematics Series. Dover, New York (1939)

    Google Scholar 

  47. Software Engineering Standards Committee of the IEEE Computer Society: IEEE standard for software life cycle processes: risk management (2001). IEEE Std 1540-2001

    Google Scholar 

  48. Stapleton, J.: DSDM Dynamic Systems Development Method: The Method in Practice. Addison-Wesley, Reading (1997)

    Google Scholar 

  49. Takeuchi, H., Nonaka, I.: The new product development game. Harv. Bus. Rev. 64(1), 137–146 (1986)

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Libera Università di Bolzano, Bolzano, Italy

    Andrea Janes & Giancarlo Succi

Authors
  1. Andrea Janes
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Giancarlo Succi
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 2014 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Janes, A., Succi, G. (2014). Towards Lean Thinking in Software Engineering. In: Lean Software Development in Action. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-00503-9_3

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-00503-9_3

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-662-44178-7

  • Online ISBN: 978-3-642-00503-9

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation