• Journal of Korea Multimedia Society
• /
• v.18 no.6
• /
• pp.753-762
• /
• 2015

As the computer graphic technology has developed rapidly, the management of visual effects production has also changed. However, the insufficient rest and the inefficiency of communication have resulted in more pressure which would weaken the strength of the whole team. For searching the possible solution, this research has applied the SCRUM in VFX production and analyzed the impact of SCRUM for VFX project management. SCRUM was first used in the projects of software development, but now there are already many successful examples of introducing SCRUM into their facilities in various fields. This paper has used SCRUM in the experimental group and present methodology in VFX project management in the control group for the same project. Based on the analysis of the questionnaire investigation from both group with using t-test for data analysis, it has confirmed the credibility of the questions in the questionnaire index as α > 0.72. With the result of analysis based on the corresponding samples of the t-test, it shows the diversity of SCRUM for project management, and the convenience of communication within the team can enhance the team strength. Follow-up research will attend to provide more suggestions for applying SCRUM in other areas in project management.

• Journal of KIISE
• /
• v.42 no.9
• /
• pp.1133-1146
• /
• 2015

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.

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2013.01a
• /
• pp.221-222
• /
• 2013

대학에서 게임 개발 교육을 수행할 때 체계적인 방법론을 적용하는 것이 필요하나, 대부분의 방법론이 복잡하고, 또 사전에 방법론에 대한 교육을 시키기도 어려워 학교 교육에서 적용하기 어렵다는 문제가 있다. 여러 방법론 중 대표적인 애자일 방법론인 스크럼은 단기간의 개발을 지원할 수 있고, 상대적으로 쉬운 구조를 가지고 있어 학기 기반의 프로젝트 교육에 적합한 특성을 가지고 있다. 본 논문에서는 기존의 스크럼 방법론을 한 학기의 게임 개발 프로젝트 교육에 적합하도록 최적화한 CK-Scrum 방법론을 실제로 적용한 사례를 분석하고, 문제점을 보완하여 새로 개선된 CK-Scrum 1.1 방법론을 제시한다. 이 방법론으로 학생들이 프로젝트를 수행하며 품질이 높은 게임을 개발하고 방법론에 대한 학습도 병행할 수 있다.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.8 no.2
• /
• pp.646-663
• /
• 2014

Scrum is one of the most popular and efficient agile development methods. However, like other agile methods such as Extreme Programming (XP), Feature Driven Development (FDD), and the Dynamic Systems Development Method (DSDM), Scrum has been criticized because of lack of support to develop secure software. Thus, in 2011, we published research proposing the idea of a security backlog (SB). This paper represents the continuation of our previous research, with a focus on the evaluation in industry-based case study. Our findings highlight an improved agility in Scrum after the integration of SB. Furthermore, secure software can be developed quickly, even in situations involving requirement changes of software. Based on our experimental findings, we noticed that, when integrating SB, it is quite feasible to develop secure software using an agile Scrum model.

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2012.07a
• /
• pp.361-362
• /
• 2012

대학의 게임 개발 프로젝트 교육을 수행함에 있어 개발 방법론을 적용하여 체계적인 단계를 거치도록 하는 것이 필요하나 기본의 소프트웨어 개발 방법론들은 복잡성과 기간 등의 제약으로 적용하기 어렵다. 애자일 방법론 중 하나인 스크럼은 주기적인 개발을 지원하고 있어 프로젝트 교육에 적합한 특성을 가지고 있다. 본 논문에서는 기존의 스크럼 방법론을 한 학기의 게임 개발프로젝트 교육에 적합하도록 최적화한 CK-Scrum 방법론을 제시한다. CK-Scrum 방법론을 적용할 경우 주기적으로 산출물을 생산하여 검토하고 반복적으로 개발함으로써 학생들이 프로젝트를 수행하며 품질이 높은 게임을 개발하고 방법론에 대한 학습도 병행할 수 있다.

• International journal of advanced smart convergence
• /
• v.8 no.3
• /
• pp.161-166
• /
• 2019

Viewed in the rate of change in the web environment, it is very difficult to remain the initial planning at the time until the time of launch, and there is a need for a method to accommodate changes and satisfy market demands during the development process. Unlike the traditional waterfall approach of maintaining initial planning, scrum is one of the agile methodologies that enables flexibility to respond to changes in the market and customers' needs and drive customer satisfaction and business success. However, to apply the scrum to a project in actual, the practice method itself is relatively simple but not easy to apply. The reason is that the members of the organization need to understand and participate in scrum's philosophy and principles and the continuous observation and change management should be carried out. Therefore, in this paper, we presented the feature dashboard and customized scrum methodology to enable continuous observation and change management using visibility, and we shared the case that periodically reflected inspection and adaptation with the explanation of the main points. Also, based on the experience with participants, the strengths and weakness of the feature dashboard and the customized scrum methodology are summarized.

• Journal of Digital Convergence
• /
• v.10 no.10
• /
• pp.339-345
• /
• 2012

Despite agile methods and software reuse being distinct approaches, there has been a growing amount of research on combining these approaches. Although Scrum is one of the most popular agile methods, reuse has not been actively supported. In this paper, we identify a new type of reusable Scrum assets, simplify the backlog process and propose a backlog factoring technique by extending task factoring to support reuse in the Scrum method. In addition, we can apply the proposed technique and show prototyping of backlog reuse in e-business applications.

• Journal of Digital Convergence
• /
• v.11 no.12
• /
• pp.439-445
• /
• 2013

There has been a growing amount of research on combining Agile methods and software reuse. Most of it introduces Agile into software product line rather than software reuse into Scrum method. Meanwhile, some assets such as backlogs and incremental artifacts in Scrum development are reusable. In this paper, we identify a backlog binder that aggregates reusable Scrum assets and proposes a backlog binder reuse technique. In addition, we can apply the proposed technique and show prototyping of backlog binder reuse in job matching applications.

• Information Systems Review
• /
• v.10 no.3
• /
• pp.185-205
• /
• 2008

As time to market and rapid reaction to changes in demand is much required, agile software development methodologies whose characteristics are great adaptability and short iteration developments are getting more popular. Though there have been a number of literature suggesting the great potential of agile software development, some recent studies have also mentioned its limitations. We believe there remains much confusion as to whether agile approaches are good to introduce or not. In an effort to provide 'real' characteristics of agile development, this paper evaluates Scrum, one of the most used agile approaches, using a software measurement framework. It also presents a Scrum measurement case study of a web portal company. We believe this study will provide some concrete guidelines as to whether Scrum is worth, what are weak points, and how to control the agile process in order to get over the weakness.

• Journal of Digital Convergence
• /
• v.12 no.12
• /
• pp.337-343
• /
• 2014

There have been many efforts to find a new way to combine software reuse and agile software development methods. This paper studies the integration of software reuse techniques in agile methods, such as Scrum. Agile methods have the advantage of accepting frequent requirement changes, while software reuse reduces development time. Despite the rapid acceptance of the Scrum method in industry, not much emphasis has been placed on active reuse in the Scrum method, and most studies have focused on introducing agile practices into software product line engineering. However, the iterative development and backlog refinement activities of the Scrum method present the advantage of facilitating software reuse. In this paper, we identify sprint characteristics and components for reuse and suggest extended backlog refinement steps. Based on the results of this research, we integrate a backlog factoring technique into backlog refinement to support reuse in agile methods. In addition, we apply the proposed technique and demonstrate a prototype of product backlog reuse in backlog refinement for an Internet shopping mall application.