No abstract

Abstract-Science and technology are growing fast both in case of software and hardware. Due this changes are inevitable in every aspect of development and manufacturing. When software development is considered new methods and technologies are being introduced for developing software products. This is due to constant change from the side of customer to developer. Because of this new process models are developed to meet the requirements of both customers and developers. Based on the requirements from customers to developers every enterprise has to go for change. Once a process model is adopted the whole enterprise mainly developers has to adjust to new culture. This work discuss on the problems faced by developers when they start using new model because they are habituated to old and experience process models. In this work, muscle memory of developers carried from traditional models to new process model with respect to Scrum and the impact on them is discussed and consequence on product development. The advantages of Scrum when the hurdles are controlled are also discussed.

Abstract-Software developing enterprises tend to go for new process models that help them in developing software products. This is because the change in the needs of customers and the developing enterprises are not constant. To meet this old and traditional process models are not applicable. When new process models are chosen they need to be adopted first into the enterprise. After the process model is adopted it is very important to control the process model in the enterprise. It is essential to know how the process model is integrated to the environment of the software developing enterprise. The behaviour of the process model in its early period after adoption is discussed in this work.Keyword -Agile, Scrum, Enterprise, Product development, Early Months. I. INTRODUCTION In software engineering software developing methodology is a framework that helps the developing enterprises to organize, plan, and regulate the course of developing a software product. Around 1960s for the first time these frameworks for software development appeared. In 2004 Geoffrey Elliott [7] described that these systems development life cycles for developing the products referred as SDLC. These are the eldest formal organized frameworks for developing information schemes. The key function this software development life cycle in the 1960s is to develop business oriented products in larger way.Enterprises to develop products or to manufacture products require process models to follow in doing the work because they help in smooth running of overall activities. Process models play an important role in the life cycle of a product. Without a process model it is difficult to get a successful product as it is considered as the path for carrying the work to be done. In software engineering to develop products process models are being used from the early days. Water fall model is considered as the base model for all new models in software industry. If a new process model is to be developed it has to follow the basic concepts of waterfall model. Fig.1 shows the phases of waterfall model which is sequential in approach. Every phase in waterfall model is processed one after the other in product development. Process models that exist in software engineering have it strengths and weaknesses and they are opted based on the environment of new product to be developed. They are measured based on the requirements of both the customer and developing organizations. Because of different requirements of customers and developers many process models has been developed to help in product development. In recent times a new group of methodologies has been developed that are acting as substitute to traditional and modern process models. These are agile methodologies that respond to changeability in product development. As other modern methods these agile methodologies are also iterative and incremental in nature [3]. These are suitable for developing business oriented products. Among the several agile methods the successfully and widely used methodologies are extreme ...

Agile development methods are key to the future of flexible software systems. Scrum is one of the vanguards of the new way to manage software development when business conditions are changing. However; the tricky part in agile software development is that there is no manual which tells you exactly how to do it. Scrum teams have to experiment and continuously adapt the process until it suits the specific situation and to overcome the challenges. The aim of this research paper is to address the quality challenges and issues in Scrum implementation and proposing solutions to overcome or minimize the issues. The common issues in Scrum implementation are Scope Creep, Requirement changes which is inherent, the biggest challenge of inadequate time to prepare test plans, minimal requirements documentation to prepare the test cases, highly compressed test execution cycles, minimal time for regression. In addition [10] communication and building trust is another issue if the team is working in a distributed environment. These factors may result in having an adverse impact on the quality of the product delivered. To overcome this to an extent the concept of the "principle of factor sparsity" or [13] pareto principle can be applied which states that, for many events, roughly 80% of the effects come from 20% of the causes. This was originally described by Vilfredo Pareto and later formalized by Joseph Juran.The principle is just a rule of thumb, but an important one. Whether the percentages are really 80/20 or 70/30 or 90/10, the reality is that most things are caused by a few underlying factors. The same applies for Scrum and 80% of the quality issues would a raise from the tasks that are performed related to 20% of the stories .So; [12] concentration on the vital few stories or tasks to arrest the critical issues and having a technique to double check the code quality delivered by agile scrum teams would provide better results. UI programming is one such new technique proposed. For an increase in quality and decrease in the defects generation; the call for a UI programming can be taken by the product owner while creation of product backlog or can be taken by the team along with product owner during the sprint planning meeting when actually the tasks are defined. The tasks that are candidates for UI programming would base on the story/tasks criticality, complexity, likeliness of being source for defects bugs, the need for high quality. At times the story and all its tasks defined can be candidates for UI programming or specific tasks within the story can be candidates for UI programming. In nutshell, the UI programming can be used in any projects which are implementing scrum and are having considerable quality issues in the implementations.