Earticle

최근에는 소프트웨어개발 프로세스나 도구보다는 개인과의 상호작용을 희망하고, 고객은 포괄적인 문서보다는 우선 작동하는 소프트웨어를 희망하며, 개발자는 계약에 대한 협상보다는 고객과의 협력을, 서로가 계획을 고수하기 보 다는 변화에 대응하는 것을 더욱 가치 있게 생각한다. 이러한 관점에서, 소프트웨어 개발은 프로세스 중심보다는 프로 젝트팀에게 자율성과 동기를 부여하고, 열정과 비전 등 인간관계 중심의 관리방식이 요구되고 있다. 최근에 와서 애자일 개발프로세스가 생산성 증대효과, 품질향상, 고객만족 등의 효용성이 입증되면서 프로젝트를 추 진 할 때 방법론 선택에 있어, 전문가들에게 주목을 받게 되었다. 시대적 요구와 사용자 요구에 부응하기 위한 방법론 선정과 관련, 본 논문에서는 조직 구성에 있어, 제품 기반의 Cross functional team의 문제점을 해결하고자 제안된 방 법론이 Feature Team 모델이며, 이 모델이 Cross functional team을 조직하고, 이 팀이 결과물(프로덕트) 단위가 아 니라, 기능단위로 여러 프로덕트에 걸쳐서 개발을 진행하는 모델이라는 점에 대해 조사하였으며, 가치-주도형 애자일 기법을 통해 계획-기반형 모델과 차이점을 제시하였다. 그리고 객체지향모델링을 위해서는 기존의 JAD(joint application development)회의가 목표로 하는 도메인 분석, 요구추출, 모델링과 정리, 검토과정에 있어, UML 구조도와 행동도를 사전에 숙지하고 프로젝트를 진행하도록 제안한다.

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 .

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.