scholarly journals Estimation of effort in agile software development: Study of the current state in Bogotá

Author(s):  
Fernando Prieto Bustamante

Context: Over the years, numerous studies have been developed related to estimating effort in agile software development, which allow us to understand the advances that have been made and the need for their use in companies. Objective: To know the perspective of entrepreneurs from different organizations in Bogotá that work in the sector or are related to the development of agile software and those who have had projects related to the subject. Method: For the elaboration of the article, a bibliographic research is carried out. Results: The data obtained are from 314 respondents in the city of Bogotá, the main findings are: 1) For companies it is extremely important with (34%) the adoption of an effort estimation methodology. 2) The most used estimation technique is the use case point with (43.31%). 3) The most used effort predictor is the Code Line (38.85%) and followed by this STORY POINT with (33.76%). 4) The agile methodology adopted in companies is SCRUM with (43.95%). 5) As the most determining factor to estimate the effort, the team experience with (53.50%) is considered. 6) In the percentage of error between estimate of projected effort and real effort (26.75%) of the respondents determine that this 5% -25% is underestimated. 7) Finally, as a difficulty in your company to estimate the effort of projects through agile software development, the respondents recognize (26.11%) that the resources are the greatest. Conclusions: The estimation of effort is relatively variable, for many companies this depends on the needs of each one, on the other hand, the use of agile methodology and estimation techniques varies in its use depending on the cross between them and how they are used. complement each other.

Author(s):  
Gopalkrishna Waja ◽  
Jill Shah ◽  
Pankti Nanavati

Agile Software Development plays a quintessential part in modern day software development. The term Agile refers to frequent reassessment and adaptation of plans and techniques and dividing tasks into shorter tasks for efficiency. Agile Software Development differs considerably from Traditional Software Development Methodology. Agile methodology aims to deliver features of a software project in small steps within a short duration of time (i.e., iterations). Hence, it becomes necessary to use agile software development methodology in todays’ fast-paced revolutionizing software industry. This paper discusses the important subtopics of Agile Software Development which gathered by reviewing/surveying of research papers. First, is the Agile Planning Life Cycle which consists of various stages such as pre-planning, planning, release planning and product backlog management. In the next section, principles such as Scrum, Extreme Programming, Kanban and Lean are discussed. The last section comprises the impact of Agile principles on software quality.


Author(s):  
David Parsons ◽  
Rosemary Stockdale

Multi-User Virtual Environments (MUVEs) are the subject of increasing interest for educators and trainers. In the context of software development, they are beginning to see increasing use both as learning spaces and as a richer means of collaboration for virtual teams. This chapter reflects on a project that developed and evaluated a virtual agile software development workshop hosted in the Open Wonderland MUVE, designed to help learners to understand the basic principles of some core agile software development techniques. The work took a design-based research approach, following a reflective path of development through two major iterations. The authors trace the research process from a real world implementation of the “agile hour” workshop to its virtual incarnation, describing the design philosophy and the constructed virtual artifacts. They conclude by reflecting on the insights into learner perceptions and practical implementations gained from building and evaluating the Open Wonderland workshop.


Author(s):  
Emanuel Dantas Filho ◽  
Mirko Perkusich ◽  
Ednaldo Dilorenzo ◽  
Danilo Santos ◽  
Hyggo Almeida ◽  
...  

Author(s):  
Handrie Noprisson

In recent years, the software development methodology evolves from the traditional approach to agile software development. This paper attempted to conduct a systematic literature review (SLR) regarding the improved agile software development to tackle its weakness based on recent research papers. Systematic Reviews and Meta-Analyses (PRISMA) as Systematic Literature Review Method (SLR). SLR is the review method which uses some protocols in order to minimize bias in the reviews. The improved of agile software methodology mostly regarding code reusability, usability, project quality, estimation, software delivery, usability, user responses and requirements delivery, communication between members, usability, practical activities, communication between team and stake holder, usability, workflow (learning), problem identification and effort estimation.


Author(s):  
Ali Sever

In distributed agile software development, to conquer the problems raised by rapid development of complex products with ever changing technological advances and risks, there is a need of a model with specific tools and technology supported approaches to manage them. Distributed environment has challenges and complexities in many ways of over collocated teams. However, they seem to enhance the basic principles in which agile methodology thrives on. Agile projects and distributed projects are compatible and therefore practices, principles, tools, and techniques for distributed agile software development are introduced to the distributed teams to ensure that the agile projects become successful. Although cloud computing is well established for software system developments, its effect on agile methodology has not been extensively studied. This study outlines how agile projects can be modeled in the cloud-computing era, namely, seamless agile-cloud integration. We propose a model to improve Agile Methodology in distributed computing platform. This model has uncovered a gap between the distributed agile development phases that are overemphasized and the phases that require actual attention. In addition to this, emphasis on appropriate phases would help build desired software that can exploit the benefits of cloud computing in numerous ways.


In present senario Agile methodology perform very popular role in software design & development with the help of customer requirement. In development process we generally consider functional requirement more than non-functional requirement but non-functional requirement also contain equal weightage in Agile Software Development. This paper incorporates to find non functional requirements based on priority algorithm. With the help of this algorithm author tries to find comparisons different non functional requirement


Sign in / Sign up

Export Citation Format

Share Document