scholarly journals THE CHALLENGE OF IMPLEMENTING SCRUM AGILE METHODOLOGY IN A TRADITIONAL DEVELOPMENT ENVIRONMENT

2013 ◽  
Vol 5 (2) ◽  
pp. 98-108 ◽  
Author(s):  
Renato Takeki Nishijima ◽  
Prof. Dr. José Gonçalo Dos Santos

Agile software development management is gradually gaining more profile and followers among technology companies. The current article presents a study on agile methodologies in contrast to traditional methodologies as well as the motivation to implement agile software development management techniques in small projects by providing an overview of the challenges, objectives, reasons, advantages and disadvantages compared to traditional software development management.

Author(s):  
Pankaj Kamthan

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.


Author(s):  
Vinay Kukreja ◽  
Amitoj Singh

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.


Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun

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.


Author(s):  
Pankaj Kamthan

The movement towards agility is one of the most significant human-centered and socially oriented changes in industrial software engineering. In the practice of agile methodologies, there are different types of content (data, information, or knowledge) that are created, communicated, and consumed. It is imperative for an organization to manage such content, both during development and beyond deployment. This chapter proposes a conceptual model for understanding and exploring the use of Wiki as a vehicle for managing content in agile software development. In doing so, the parity between agile software development and Wiki is shown, human and social aspects of each are emphasized, the Social Web-Context of Wiki is demonstrated, illustrative examples are given, and the implications of committing to a Wiki are considered.


Author(s):  
Iwona Dubielewicz ◽  
Bogumila Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz

Agile methodologies have become very popular. They are defined in terms of best practices, which aim at developing good quality software faster and cheaper. Unfortunately, agile methodologies do not refer explicitly to quality assurance, which is understood as a planned set of activities performed to provide adequate confidence that a product conforms to established requirements, and which is performed to evaluate the process by which products are developed. The chapter considers the relations of agile practices with software life cycle processes, especially those connected to quality assurance, and tries to answer the question of which agile practices ensure software quality. Next, agile practices associated with quality assurance are assessed from different perspectives and some recommendations for their usage are given. It is observed that modeling has a particular impact on quality assurance.


Author(s):  
Samar Alsaqqa ◽  
Samer Sawalha ◽  
Heba Abdel-Nabi

<p>Software engineering is a discipline that undergone many improvements that aims to keep up with the new advancements in technologies and the modern business requirements through developing effective approaches to reach the final software product, agile software development is one of these successful approaches. Agile software development is a lightweight approach that was proposed to overcome the convolutional development methods’ limitations and to reduce the overhead and the cost while providing flexibility to adopt the changes in requirements at any stage, this is done by managing the tasks and their coordination through a certain set of values and principles.</p><p>In this work, a comprehensive review that outlines the main agile values and principles, and states the key differences that distinguish agile methods over the traditional ones are presented. Then a discussion of the most popular agile methodologies; their life cycles, their roles, and their advantages and disadvantages are outlined. The recent state of art trends that adopts agile development especially in cloud computing, big data, and coordination are also explored. And finally, this work highlights how to choose the best suitable agile methodology that must be selected according to the task at hand, how sensitive the product is and the organization structure.</p>


2012 ◽  
Vol 85 (6) ◽  
pp. 1213-1221 ◽  
Author(s):  
Torgeir Dingsøyr ◽  
Sridhar Nerur ◽  
VenuGopal Balijepally ◽  
Nils Brede Moe

Author(s):  
Pattama Kanavittaya ◽  
Jocelyn Armarego ◽  
Paula Goulding

The alignment of business strategy and IT strategy has been recognised as a strategic weapon within organisations. Small and medium sized enterprises (SMEs) also recognise a need for new Information Technology and Information Systems (IT/IS) functions to support business strategies, and provide new services to the market. Agile methodologies support the timely and economical development of Web and Internet-based software, the technologies being exploited by organisations seeking to enhance their business performance. Based on multiple-case research, this paper explores the impact of agile software development on the alignment of business strategy with IT strategy in SMEs. Several models of strategic alignment developed for large enterprises were used to examine the SME environment. The findings suggest that agile methods are applied to provide added flexibility for organisations to create or react to new opportunities, to increase responsiveness to customer requirements not possible with traditional software development, and to gain competitive advantage. Personal interest was found to be a factor in adopting agile methodologies, in addition to IT maturity and technical IT sophistication. However, the use of agile methods in response to internal and external uncertainty may change the role of ICT in the firms, and hence impact on the alignment of business and IT/IS strategy.


Sign in / Sign up

Export Citation Format

Share Document