Application of Agile methodologies for software development

Agile Methodologies ◽

Agile Software ◽

Software Lifecycle

In this work explored evolution of software lifecycle models firstly to lightweight and then to agile software development methodologies, and factors that have led to a search for ways to improve approaches to software development. Also compared "outdated" development designing approaches with modern flexible and made conclusions whether the advantage of the latter over the firsts is absolute and whether or not they and only they should be used in practice or maybe older approaches still have their advantages and it is too early to exclude them.

Achieving Enterprise Agility through Innovative Software Development - Advances in Systems Analysis, Software Engineering, and High Performance Computing ◽

Agile Enablers and Adoption Scenario in Industry Context

10.4018/978-1-4666-8510-9.ch008 ◽

2015 ◽

pp. 157-178

Author(s):

Vinay Kukreja ◽

Amitoj Singh

Keyword(s):

Software Development ◽

Agile Development ◽

User Requirements ◽

Distributed Environment ◽

Team Members ◽

Agile Methodologies ◽

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.

Adopting Agile Software Development Methodologies in Big Data Projects – a Systematic Literature Review of Experience Reports

2020 IEEE International Conference on Big Data (Big Data) ◽

10.1109/bigdata50022.2020.9378118 ◽

2020 ◽

Author(s):

Iva Krasteva ◽

Sylvia Ilieva

Keyword(s):

Big Data ◽

Literature Review ◽

Software Development ◽

Systematic Literature Review ◽

Extreme Programming and Agile Software Development Methodologies

IS Management Handbook ◽

10.1201/9781420031393-48 ◽

2003 ◽

pp. 531-550

Keyword(s):

Software Development ◽

Extreme Programming ◽

Handbook of Research on Information Architecture and Management in Modern Organizations - Advances in Information Quality and Management ◽

Using Wiki for Managing Knowledge in Agile Software Development

10.4018/978-1-4666-8637-3.ch018 ◽

2016 ◽

pp. 397-423

Author(s):

Pankaj Kamthan

Keyword(s):

Software Engineering ◽

Software Development ◽

Software System ◽

Web Environment ◽

The Past ◽

Agile Methodologies ◽

The Social ◽

Industrial Software ◽

The movement towards agility is one of the most significant changes in industrial software engineering over the past decade. In the practice of agile methodologies, there are different types of knowledge that is created, communicated, and consumed. For the benefit of the stakeholders involved, there is a pressing need to manage this knowledge, both during development and beyond deployment of a software system. This chapter proposes a framework comprising related conceptual models as means for understanding the use of Wiki for managing knowledge in agile software development. In doing so, Wiki is considered beyond that of a technology or a tool, as a facilitator of knowledge, and placed in a larger context of the Social Web environment. For the sake of practicality, a number of illustrative examples are given, and implications of deploying a Wiki are highlighted.

Agile Software Development

Security-Aware Systems Applications and Software Development Methods ◽

10.4018/978-1-4666-1580-9.ch001 ◽

2012 ◽

pp. 1-15

Author(s):

Torstein Nicolaysen ◽

Richard Sassoon ◽

Maria B. Line ◽

Martin Gilje Jaatun

Keyword(s):

Software Development ◽

Agile Development ◽

Implementation Team ◽

Agile Methodologies ◽

Development Organizations ◽

Development Lifecycle ◽

Software Development Lifecycle ◽

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Advances in Systems Analysis, Software Engineering, and High Performance Computing - Emerging Innovations in Agile Software Development ◽

Usability Engineering in Agile Software Development Processes

10.4018/978-1-4666-9858-1.ch011 ◽

2016 ◽

pp. 208-221

Author(s):

Muhammad Aminu Umar ◽

Sheidu Salami Tenuche ◽

Sahabi Ali Yusuf ◽

Aminu Onimisi Abdulsalami ◽

Aliyu Muhammad Kufena

Keyword(s):

Software Development ◽

User Interaction ◽

Functional Requirements ◽

Usability Engineering ◽

Agile Processes ◽

Software Product ◽

Development Processes ◽

As the popularity and acceptance of agile software development methodologies increases, the need to integrate usability engineering in the design and development processes is imperative. While, agile the focus is on technical and functional requirements not on end-user interaction, usability is usually only dealt with on the side. Combining this two in practice will go a long way in development of better product. Since the success and acceptance of software product depends not only on the technologies used but how well it integrates user-oriented methods. Therefore, this chapter puts together works on how usability engineering has been integrated with agile processes.

Agile Software Development Quality Assurance

Software Applications ◽

10.4018/978-1-60566-060-8.ch156 ◽

2009 ◽

pp. 2680-2699

Author(s):

James F. Kile ◽

Maheshwar R. Inampudi

Keyword(s):

Software Development ◽

High Performance ◽

General Rule ◽

Adaptive Methods ◽

Agile Development ◽

Performance Requirements ◽

Small Project ◽

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.