• 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 Korea Information Processing Society Conference
• /
• 2017.11a
• /
• pp.464-465
• /
• 2017

본 논문에서는 애자일 방법론과 스크럼 기법에 대해서 소개하고 국내 SI프로젝트에 스크럼 기법을 적용하기 어려운 이유와 스크럼이 적용된 SI프로젝트를 성공적으로 완료하기 위한 가이드를 제안한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2019.05a
• /
• pp.314-315
• /
• 2019

소프트웨어 개발은 협업이 가장 중요시 되는 분야 중 하나로 팀 단위의 소프트웨어 개발의 품질 및 생산성 향상을 위해 팀 단위 프로젝트 방법론이 발달하였다. 방법론의 선택에 따라 개발의 결과물과 만족도에 큰 차이가 나타나게 되는데, 고전적인 폭포수(Waterfall) 방식의 대안인 애자일(Agile) 방법론은 점진적인 개발로 프로젝트 진행도중 발생하는 이슈처리를 효율적으로 해결할 수 있어 현재 많은 개발에 적용되고 있다. 그 중 스프린트 기법을 바탕에 두는 스크럼(Scrum)을 사용하는데 소규모 개발팀은 스크럼(Scurm)의 교육 부담과 스크럼 마스터의 부재로 해당 방법론을 적용하기 어려움을 겪는다. 이에 본 논문에서는 소프트웨어 공학의 애자일(Agile) 방법론 중 하나인 스크럼(Scrum)을 실제 프로젝트 관리 시스템의 도구로 사용하기 위해 웹 응용 시스템으로 구현하고자 하며 해당 서비스가 SW개발뿐 만 아닌 다양한 분야의 프로젝트에 적용될 수 있도록 한다. Spring 프레임워크를 이용하여 서버를 구축하고 AWS EC2를 통해 배포하며, BootStrap과 JQuery를 이용하여 웹을 구성하여 팀 프로젝트에 있어 효율적인 관리 도구가 될 수 있도록 한다.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.15 no.6
• /
• pp.147-154
• /
• 2015

Recently agile development process became increasing effectiveness, quality, attention to experts in customer satisfaction, as evidenced in this methodology when selecting projects promoting productive efficiency. With regard to contemporary needs and user requirements on the methodology selected to meet this paper is the product based Cross functional team suggested methodology Feature Team model to solve problems of this model, and organizing the Cross functional team, this team but this outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-driven agile project through the Skills-based model and proposed a difference. And it examined the Agile Maturity metrics. PRINCE2 Agile Health-check entries future development direction of Agile techniques is a requirement of the project outset has studied the subject objective evaluation by the assumption that they can be changed at any time, not fixed this way and for the project team through research The proposed.

• Journal of the Korean Society of Systems Engineering
• /
• v.6 no.2
• /
• pp.47-57
• /
• 2010

Taylor and Ford in the 1910s led to the "scientific management" for the entire industry from the manufacturing spread of TQM Total Quality Management has been structured as a management efficiency, such as 6-Sigma techniques were developed. SW development also introduces the idea, such as CMMI and SPICE-based process management, management practices have evolved. However, in recent years to increase the knowledge of workers in the manufacturing process oriented management approach is under serious challenge. Business performance or productivity will be varied depending all motivation, human relationship, job involvement rather than simply putting a lot of time. Especially in the SW industry which is depending on human resource, Creativity should be limited in traditional management methods. Recently, Google and Apple, Cisco and global advanced companies adopt a human relationship management. Their productivity and creativity in product development has been successful by giving autonomy and motivation, enthusiasm and vision to tile employees. Human relationship management since the mid-1990s, appears as a new paradigm so called Agile process in the field of SW development. Agile processes emphasis on light, flexible and responding to changes immediately in the business environment step away from traditional management approach which is the heavy and complicated process. In this paper, agile project management concepts and practices which is applied to industry will be examined.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.16 no.1
• /
• pp.155-162
• /
• 2016

In recent years, hoping the interaction of individuals and rather than software development process and tools, and customers want software that works first, rather than a comprehensive document, in cooperation with the customer, rather than the developer negotiate a contract, to each other stick to the plan I think even more so than the value that corresponds to the change. In view of this, software development is given the autonomy and motivation to project team rather than process-oriented and have a passion and vision and human relations oriented management approach is required. In recent years, increasing the productivity benefits of agile development processes, improved quality, efficiency and customer satisfaction as is demonstrated in the methodology selected to promote the project, attention was given to the experts. Contemporary demands with regard to the methodology chosen to meet your needs, in this paper in the organization, and to solve the problems of product-based Cross functional team proposed methodology Feature Team model, this model is an organizational Cross functional team and the team is not the outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-plan through the driven agile technique-based model and proposed a difference. And the domain analysis, required extraction by conventional JAD (joint application development) meeting the targets for the object-oriented modeling, in modeling and organize, review, aware in advance and the UML Structure and Behavior Diagrams and proposed to proceed with the project.