Earticle

Agile methods are highly attractive for small projects, but no agile method works well as a standalone system. Therefore, some adaption or customization is always required. In this paper, the Agile Framework for Small Projects (AFSP) was applied to four industry cases. The AFSP provides a structured way for software organizations to adopt agile practices and evaluate the results. The framework includes an extended Scrum process and agile practices, which are based on agility and critical success factors in agile software projects that are selected from Scrum, XP, FDD, DSDM and Crystal Clear. AFSP also helps software managers and developers effectively use agile engineering techniques throughout the software development lifecycle. The case study projects were evaluated on the basis of risk-based agility factors, the agility of the adopted practices, agile adoption levels, and the degree of the agile project success. The analysis of the results showed that the framework used in the aforementioned cases was effective.

In principle, structural coverage criterion enables the evaluation of test results and the automation of test execution; however, it is limited in that it cannot be applied to specification based testing. Model-Based Testing is one of the solutions used to overcome this limitation. We propose an approach in which UML activity diagrams are used as a model. Once these activity diagrams are generated from program specifications, test cases are selected systematically according to the coverage criteria identified for the activity diagrams. Applying criteria to specification-based testing is very helpful for programmers who are supposed to write tests before source codes in Agile developments. With our proposed approach, they design tests in accordance with test models rather than their intuition. In this paper, we report on an empirical study conducted in which our approach generated a more effective suite of test cases than that of the Siemens Suite.

The popularity of Agile Development has been increasing over the last several years. Many Agile techniques include unit testing as a basic activity. Unit testing has two characteristics: it is performed by programmers, and it is normally based on source code structures. However, the problem arises that programmers are unlikely to design structure-based tests. Test design process draws graphs that represent structures; and applies coverage criteria these graphs. The coverage criteria concept is very important in unit testing. Support tools are required, especially by programmers performing unit testing. However, the existing tools do not cover all the steps of the process. This study develops a method that fills the gap between the graph generation and the test design step. This paper We analyzes the extent to which the method decreases the effort required for unit testing, and show that the method effectively reduces the effort. The effort is measured in ManMonths.

Agile development model solved a lot of its predecessor the waterfall model problems like time, cost, resources and high risk of failure due to incomplete or inaccurate requirements. However, agile model introduced the client communication problem; due to the structure and nature of agile methodologies, it depends heavily on communicating with client. With four layers of communication that get repeated in almost every agile iteration, failing to handle client communication is one of the main reasons behind failure of agile based projects. In this paper, we survey the existing methods of communication which are classified into two main categories: physical meetings/workshops and software communication tools. Each category is assessed and compared based on certain attributes such as availability, productivity, cost, reliability, trust and project coverage. In addition, the available solutions to address the communication problem, which include enhanced physical meetings/workshops and software tools like requirement engineering tools, agile management tools and social media sites and applications, are analyzed and assessed based on attributes such as usability, formality and project coverage. The study revealed that the available solutions did not address all the aspects of the communication problem. Therefore, it is desirable to develop an integrated solution which utilized communication software tool using social media frameworks as its backbone and physical meetings to benefit from human interaction and relationships to solve the communication problem in agile environment.

An acceptance test refers to a test that confirms whether the specified requirements are met. Recent studies on acceptance test automation appear to focus only on easy and simple test automation, while the importance of living documentation for the general application life cycle, which is the ultimate goal, is overlooked. Compared to traditional development methodologies, it points to marked absence of systematic planning and prediction, overhead due to the application of new process and tools, and in turn, a decline in development productivity. This study designed an architecture that can be used repeatedly through the common application of the agile software. Concrete action plans for automating the acceptance test are presented.

Software development, as a whole, is a complex process and on top of it, the requirements keep changing during the development phase. Software configuration management happens to be the most critical part as it necessitates doing considerable modification in the software design and code. Agile software development process provides a solution to such a changing environment. Agile methods use an incremental approach to develop high quality software within time, cost and other associated constraints through several iterations. In this paper we provide a critical assessment of the agile software development process in a systematic manner. This study is based on the survey of previous research reported in the contemporary literature and the practices being followed in this area.

Software industry is increasingly using Agile Methods due to its benefits. However the way industry practices agile methods is some time divergent to the basic Agile Principles. For example customer involvement in the entire software development process is considered essential; but under certain conditions this requirement is not so critical. We have studied in detail such an adaptation by a large software company using Agile Method i.e. SCRUM. The organization develops software products using SCRUM; however, after initial development; they customize the product for their potential customer. At no time (during initial development or customization stage), real customer is present at the development site; but still their products are immensely successful in terms of number of products sold, and customer satisfaction. In the real world case study we have analyzed reasons for the success of the organization and have studied in detail the circumstances which obviate the need of readily available customer. The results show that, extensive domain knowledge, prior experience of the product and experienced workforce mitigate the need of onsite customer.

The use of story cards for user stories in many Extreme Programming software development projects has been widespread. Several popular traditional methods for story cards (e.g., Cohen M, Kent B) have been used in successful fashion at some extent, but all lack of the powerful features for story cards guidelines, right sort of information on story cards and quality of user stories on story cards. They also do not involve anybody apart from customer on story writing workshop. This paper has described the INSERT model, new proposed frame work of story cards, and a new improved requirements elicitation process in XP. The experience with INSERT model and new framework of story cards indicates that it is feasible to contemplate improving user stories and story cards in Extreme programming. This paper also introduces best practices guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

Many software companies are interested in using Agile methods in their software projects. Contrary to traditional software development methods, Agile methods are people oriented. This fact shows the significant role of individuals in these methods. Increasing prevalence of Agile methods forces software companies to consider people related factors as critical issues in adoption and transition to Agile methods and practices. This article focused on human aspects of Agile transformation process by conducting a Grounded Theory study involving 32 Agile experts. The main contribution of this article is identification and classification of diverse human aspects of Agile transformation process. Analyzing collected data showed that human aspects of Agile transformation process can be classified in several categories. While some of them are impediments to change, some others act as change accelerators. At the same time people’s perceptions about change process and incentive factors can shape and form human aspects during the Agile transformation process. Each of these categories encompasses its own factors which have negative or positive effect on change process.

There has been a tremendous importance in the field of agile software development approaches in the recent past. This is because of the fastness that agile approaches bring in the life cycle of software development. This interest in the field shows that there are benefits to reap through successful implementation of agile methods. The field is relatively nascent and research is in its initial stages. The paper has been carried with the distinct objectives of examine and gain insights into the current agile methods and practices, understanding the strengths and weaknesses of agile methods and various issues of their applicability. To meet the set goals and objectives, we used both qualitative and quantitative research methodologies. Apart from a systematized literature survey and review, we performed a case study of four software companies in India. The data collection methods included questionnaires, interviews and analysis of the companies’ web-sites.

Global software development (GSD) has become a customary way of developing software whereas distributed agile software development is now gaining popularity. However, effectiveness of agile practices in GSD is a contradictory issue that needs to be explored in detail. The paper intends to investigate the effectiveness of agile practices in GSD. The research is conducted in two phases. Firstly, literature is explored to extract benefits and challenges of agile practices in GSD. Supporting practices, tools, and modifications to agile practices are also unearthed. Secondly, we have performed a survey to validate the outcome of literature review. We have identified 19 benefits and 14 challenges of distributed agile practices, and also discovered 16 supporting practices and various tools. The results of the literature review and survey both indicate that most of the agile practices can be adapted for distributed projects. Supplementary practices and tools further alleviate the incongruity between GSD and agile methods.

Agile based software development approach is increasingly gaining much interest among software practitioners and researchers due to its ability to produce high quality software in shorter period of time. Even though its importance has been revealed, only few studies were conducted regarding its current practices in the software industry, particularly in Malaysia. Thus, an exploratory study was conducted among software practitioners in Malaysia to study their practices and perceptions on the agile based software development in the real-world projects. Moreover, the practices were covered in a wider perspective by considering the software development, management and documentation practices. This paper discusses the findings from the study, which involved 73 agile practitioners. Structured questionnaire was used for data collection purpose while statistical methods such as frequency, mean, and cross tabulation were used for data analysis. Outcomes from this study reveal that the most implemented agile principles are early delivery and face-to-face communication, whilst the least implemented is self-organizing team. Additionally, majority of the respondents agreed that agile based software development practices are important in order to produce high quality software.

There are many limitations in applying agile methodology to projects so far. In fact, projects overlap with other development methodologies and management processes, resulting in confusing progress, while there are often cases where the benefits of agile cannot be embraced due to a lack of understanding of agile processes and the organization's inability to adapt to change. It is an important role of information system development to improve the quality of agile application projects by discovering the problems and improvements in these cases. In this paper, we analyze the differences between existing development and project management methods and agile, and analyze agile processes. The optimal agile methodology was proposed by analyzing and applying methodologies established and applied mainly by large domestic development companies. In addition, the effectiveness was verified through a questionnaire of IT experts, and the result of the questionnaire was verified to be 4.75 points on a 5-point scale.

최근에는 소프트웨어개발 프로세스나 도구보다는 개인과의 상호작용을 희망하고, 고객은 포괄적인 문서보다는 우선 작동하는 소프트웨어를 희망하며, 개발자는 계약에 대한 협상보다는 고객과의 협력을, 서로가 계획을 고수하기 보 다는 변화에 대응하는 것을 더욱 가치 있게 생각한다. 이러한 관점에서, 소프트웨어 개발은 프로세스 중심보다는 프로 젝트팀에게 자율성과 동기를 부여하고, 열정과 비전 등 인간관계 중심의 관리방식이 요구되고 있다. 최근에 와서 애자일 개발프로세스가 생산성 증대효과, 품질향상, 고객만족 등의 효용성이 입증되면서 프로젝트를 추 진 할 때 방법론 선택에 있어, 전문가들에게 주목을 받게 되었다. 시대적 요구와 사용자 요구에 부응하기 위한 방법론 선정과 관련, 본 논문에서는 조직 구성에 있어, 제품 기반의 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 .

최근 애자일 개발프로세스가 생산성 증대효과, 품질향상, 고객만족 등의 효용성이 입증되면서 프로젝트 추진 시 방법론 선택에 있어 전문가들에게 많은 관심을 갖게 되었다. 시대적 요구와 사용자 요구에 부응하기 위한 방법론 선정과 관련해서, 본 논문에서는 제품 기반의 Cross functional team의 문제점을 해결하고자 제안된 방법론이 Feature Team 모델이며, 이 모델이 Cross functional team을 조직하고, 이 팀이 결과물(프로덕트) 단위가 아니라, 기능단위로 여러 프로덕트에 걸쳐서 개발을 진행하는 모델이라는 점에 대해 조사하였으며, 가치-주도형 애자일 기법을 통해 계획-기반형 모델과 차이점을 제시하였다. Agile 성숙도 측정기준을 검토하였으며, PRINCE2 Agile Health-check 항목 연구를 통해 Agile 기법이 프로젝트 착수단계의 요구사항은 확정 본이 아닌 언제라도 변경될 수 있다는 것을 전제를 해서 객관적인 평가를 받는 방법에 대해 연구하고 프로젝트 팀 구성에 대해 향후 발전방향을 제시하였다.

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

형상 관리는 형상 관리의 대상이 되는 형상 항목을 선정하여 프로젝트 생명 주기 동안 선택된 산출물의 무결성을 확보하는 활동이다. 반면 짧은 생명주기를 반복하여 고객에게 배포하는 애자일 개발 방법에서는 문서 산출물보다는 구성원의 지식에 기반한 개발을 요구한다. 그러나 애자일 개발에서도 필요한 산출물은 반드시 작성하라고 하며, 그러한 산출물은 형상 관리의 적절한 관리를 통해 무결성을 유지할 수 있는 프로세스가 필요하다. 본 논문에서는 애자일 개발의 기민함을 유지하면서 산출물에 대한 무결성을 확보할 수 있도록 애자일 개발의 대표적인 방법론인 XP에 형상 관리 프로세스를 연구 및 개발하여 그 적용을 제안한다.

형상 관리는 형상 관리의 대상이 되는 형상 항목을 선정하여 프로젝트 생명 주기 동안 선택된 산출물의 무결성을 확보하는 활동이다. 반면 짧은 생명주기를 반복하여 고객에게 배포하는 애자일 개발 방법에서는 문서 산출물보다는 구성원의 지식에 기반한 개발을 요구한다. 그러나 애자일 개발에서도 필요한 산출물은 반드시 작성하라고 하며, 그러한 산출물은 형상 관리의 적절한 관리를 통해 무결성을 유지할 수 있는 프로세스가 필요하다. 본 논문에서는 애자일 개발의 기민함을 유지하면서 산출물에 대한 무결성을 확보할 수 있도록 애자일 개발의 대표적인 방법론인 XP에 형상 관리 프로세스를 연구 및 개발하여 그 적용을 제안한다.

아직도 많은 프로젝트에서 지속적으로 변화하는 요구사항과 불가능한 납기일정 그리고 품질을 무조건 만족해야 하는 상황에 많은 개발자들이 괴로워하고 있다. 또한 최근 들어 프로젝트들이 그 개발의 방법으로 컴포넌트 기반 개발(CBD)를 많이 사용하고 있다. 이러한 상황에서 재사용성을 강조하는 품질 좋은 컴포넌트를 식별하고, 개발하기란 매우 어렵다. 또한 기존의 CBD 개발 방법의 프로세스가 요구사항을 초기에 고정하고, 그 기반 위에 여러 단계를 거치기 때문에, 납기기간이 짧거나, 요구사항이 고정되지 않았을 경우 많은 어려움에 직면하고 있다. 본 논문에서는 요구사항이 불명확하고, 납기일정이 짧은 프로젝트에서 유용하도록, 작은 단위의 반복과 그 피드백을 통해, 고객의 요구사항 변경에 빠르게 반응할 수 있고, 기존의 컴포넌트 개발 방법을 단순화한 기민한 컴포넌트 개발 프로세스를 제시한다. 이러한 제안된 기법의 실용성을 검증하기 위해 기존 식별 방법과의 비교, 평가를 제시한다.