경영정보학연구 (Information Systems Review)

  • 제13권1호
  • /
  • Pages.61-74
  • /
  • 2011
  • /
  • 2982-6551(pISSN)
  • /
  • 2982-6837(eISSN)
한국경영정보학회 (The Korea Society of Management Information Systems)
권호 표지

린(Lean) 개념을 소프트웨어 개발 방법에 적용하기 위한 사례 연구: 낭비 제거의 가시화를 중심으로

How to Implement 'Lean' Principles into Software Development Practice?: Visualization of Delays and Defects

  • 투고 : 2011.04.12
  • 심사 : 2011.04.26
  • 발행 : 2011.04.30
PDF 다운로드
⟨ 이전 논문 다음 논문 ⟩

초록

소프트웨어 산업은 아직도 뿌리깊은 문제에 시달리고 있다. 어떻게 보면, 제조업과 같은 보다 성숙한 산업의 모범사례로부터 뭔가를 배워야 할 지 모른다. 제조업에서의 '린' 원칙을 소프트웨어 개발에 적용하는 것도 한 방안일 수 있다. 소프트웨어공학 문헌에서 이런 '린' 원칙은 시도해 볼만 한 것으로 언급되었다. 그러나 이들 원칙을 실제 어떻게 적용할 수 있을 가에 대한 구체적 방안을 제시한 연구는 별로 없었다 본 연구는 '린' 원칙을 소프트웨어 개발에 적용하는 방안을 제시하고자 한다. 이 방안의 핵심은 낭비제거라는 린의 관점을 구체화하기 위하여 프로젝트에서의 리드 타임과 결함을 누적 흐름도(Cumulative Flow Diagram)을 통해 관리하는 방법이다. 또한 이 방안을 실제 프로젝트 사례에 적용함으로써 타당성을 검증하고 적용 방법에 대한 이해를 돕고자 하였다.

Software industry still has many deep-seated problems. As a natural consequence, it may have to learn from best practices in more mature industry like manufacturing. An example is 'lean' software development which is defined as translation of 'lean manufacturing' principles to the software development domain. The principles include 'eliminate waste' and 'amplify learning.' It was much asserted that these principles are worth applying. Not much study, however, was done on how to practically implement these principles into software development practice. In this study we attempt to present a method in which project lead time and software defects are regarded as major targets of management and are visualized using Cumulative Flow Diagram. We further applied this method on actual projects. The result confirms that agile is positively effective on reducing wastes.

키워드

과제정보

연구 과제 주관 기관 : 중앙대학교

참고문헌

  1. Cooke, J., Agile Principles Unleashed: Proven approaches for achieving real productivity gains in any organization, IT Governance Publishing, the United Kingdom, 2010.
  2. Dictionary. corn, "Agility", Dictionary.com, LLC, 2011, online at http://dictionary.reference.com/browse/agility.
  3. Fowler, M., "The New Methodology", MARTINE FOWLER, 2005, online at http://www.martinfowler.com/articles/newMethodology.html.
  4. George, M., Lean Six Sigma, McGraw-Hill, New York, 2002.
  5. Griffiths, M., "Creating and Interpreting Cumulative Flow Diagrams", 2007, online at http://www.leadinganswers.com
  6. Hamilton, T., A lean software engineering system for the Department of Defense, Massachusetts Institute of Technology, 1999.
  7. Hibbs, C., S. Jewett, and M. Sullivan, The Art of Lean Software Development: A Practical and Incremental Approach, O'Reilly Media, Inc., USA, 2009.
  8. Kim, E. H. and J. H. Park, "Analysis of Lean Six Sigma Methodology for Postal Logistics", EIRI, 2007.
  9. Larman, C., Agile and iterative development: a manager's guide, Pearson Education, Inc., Boston, 2004.
  10. Middleton, P., "Lean Software Development: Two Case Studies", Software Quality Journal, pp. 241-252, 2001.
  11. Morgan, T., Lean manufacturing techniques applied to software development, Massachusetts Institute of Technology, 1998.
  12. Parnell-Klabo, E., "Introducing Lean Principles with Agile Practices at a Fortune 500 Company", IEEE Computer Society, 2006.
  13. Petersen, K. and C. Wohlin, "Software process improvement through the Lean Measurement (SPI-'LEAN') method", The Journal of Systems and Software, 2010.
  14. Poppendieck, M. and T. Poppendieck, Implementing Lean Software Development: From Concept To Cash, Addision-Westey, 2007.
  15. Poppendieck, M. and T. Poppendieck, Lean Software Development: an agile toolkit, Addison Wesley, Boston, 2003.
  16. Poppendieck, M., "Principles of lean thinking", Technical Report. LLC, 2002.
  17. Schwaber, K., Agile project management with Scrum, Microsoft press, Redmond, 2003.
  18. Shalloway, A., G. Beaver, and J. Trott, Lean-Agile Software Development: Achieving Enterprise Agility, Addison Wesley, 2009.
  19. Shingo, S. and A. Dillon, A study of the Toyota production system from an industrial engineering viewpoint, Productivity Press, New York, 1989.
  20. Sowmyan, R., "Lean software development: is it feasible?", Digital Avionics Systems Conference, Vol.1, 1998.
  21. Tierney, J., "Eradicating mistakes from your software process through Poke Yoke", Software Quality Week, Software Research Institute, pp. 300-307, 1993.
  22. Wirth, N., "A Plea for Lean Software", IEEE Computer, 1995.