정보과학회 논문지 (Journal of KIISE)

  • 제42권9호
  • /
  • Pages.1133-1146
  • /
  • 2015
  • /
  • 2383-630X(pISSN)
  • /
  • 2383-6296(eISSN)
한국정보과학회 (Korean Institute of Information Scientists and Engineers)
권호 표지
DOI QR코드

DOI QR Code

문서 지향적 프로세스에서의 SCRUM 프로젝트 적용: 실험 사례연구

Running a SCRUM project within a Document Driven Process: An Experimental Case Study Report

  • 투고 : 2015.03.17
  • 심사 : 2015.06.19
  • 발행 : 2015.09.15
⟨ 이전 논문 다음 논문 ⟩

초록

본 논문은 아주대학교에서 컴퓨터 공학과 대학원생들이 SCRUM을 이용하여 고급 소프트웨어 공학 프로젝트를 운용한 결과를 사례 연구로써 다루는 논문이다. 일반적으로 현장의 고객과 그들의 요구사항 문서에 대하여 제한사항들을 제공하는 환경은 문서 지향적인 단일 단계 방법론에서는 흔하지 않은 일이 아니다. 본 논문에서는 프로젝트를 진행하는 방법론과 실습 과정을 자세히 다루며 SCRUM 프로세스를 적용하는 과정에서 일반적인 소프트웨어 팀 구성원들이 마주하게 되는 몇 가지 문제들을 되돌아본다. 또한 본 논문은 Henrik Kniberg의 SCRUM 체크리스트와 Agile Manifesto을 사용하여 실무적 내용과 테크닉의 성공을 평가하는 것으로 결론을 지었다. 이 프로젝트는 아주대학교에서 진행되었다.

This paper examines how a Computer Engineering Graduate student team ran their Advanced Software Engineering Capstone project using SCRUM. The environment provided contextual challenges in terms of the on-site customer and upfront requirements document, not uncommon in a document driven single-step methodology. The paper details the methodology and practices used to run the project, and reflects on some of the challenges faced by the members of a typical software team when transitioning to a SCRUM process. The paper concludes by evaluating the success of the techniques and practices compared to the Agile Manifesto and Henrik Kniberg's Scrum checklist. The project was undertaken at South Korea's Ajou University.

키워드

과제정보

연구 과제 주관 기관 : National Research Foundation of Korea (NRF)

참고문헌

  1. Larman, Craig, "Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3rd Edition." Pearson Education India, 2012.
  2. Humphrey, Watts S., "A discipline for software engineering." Addison-Wesley Longman Publishing Co., Inc., 1995.
  3. Heeager, Lise Tordrup, and Peter Axel Nielsen, "Agile software development and its compatibility with a document-driven approach? A case study," 20th Australasian Conference on Information Systems Compatibility of Agile and Document-Driven Approaches, Melbourne. 2009.
  4. Hayata, Tomohiro, and Jianchao Han, "A hybrid model for it project with scrum," Service Operations, Logistics, and Informatics (SOLI), 2011 IEEE International Conference on. IEEE, 2011.
  5. Sumrell, Megan, "From waterfall to agile-how does a qa team transition?" Agile Conference (AGILE), 2007. IEEE, 2007.
  6. Lewis, Jeanne, and Kevin Neher, "Over the Waterfall in a Barrel-MSIT Adventures in Scrum," AGILE. 2007.
  7. Johnson, W. Lewis, "Deriving specifications from requirements," Proc. of the 10th international conference on Software engineering, IEEE Computer Society Press, 1988.
  8. N. Dan, "Introducing: Behaviour-driven development," [Online]. Available: http://dannorth.net/introducingbdd, 2007.
  9. Schwaber, Ken, and Jeff Sutherland, "What is Scrum," [Online]. Available: http://www.scrumalliance.org/system/resource/file/275/whatIsScrum.pdf, 2007.
  10. Weidenhaupt, Klaus, et al., "Scenarios in system development: current practice," Software, IEEE 15.2 1998, 34-45.
  11. Poppendieck, Mary, and Thomas David, Poppendieck, "Lean Software Development: An Agile Toolkit," Boston, MA: Addison-Wesley, 2003. Print.
  12. Boehm, Barry, and Richard Turner, "Management challenges to implementing agile processes in traditional development organizations," Software, IEEE 22.5, 2005, 30-39. https://doi.org/10.1109/MS.2005.129
  13. Alliance, Agile, "Principles: the agile alliance," [Online]. Available: www.agileallieance.org/principles.html, 2009.
  14. Kniberg, Henrik, "Scrum Checklist," [Online]. Available: https://www.crisp.se/wp-content/uploads/2012/05/Scrum-checklist.pdf, 2010.