scholarly journals The Alignment of Business Strategy with Agile Software Development within SMEs

2010 ◽  
pp. 215-233 ◽  
Author(s):  
Pattama Kanavittaya ◽  
Jocelyn Armarego ◽  
Paula Goulding
Keyword(s):  
Software Development ◽  
Business Strategy ◽  
Business Performance ◽  
Agile Software Development ◽  
Agile Methods ◽  
It Strategy ◽  
Agile Methodologies ◽  
New Information ◽  
Multiple Case ◽  
Agile Software

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.

Some Method Fragments for Agile Software Development

2009 ◽  
pp. 223-242
Author(s):  
Q. N.N. Tran ◽  
B. Henderson-Sellers ◽  
I. Hawryszkiewycz
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Method Engineering ◽  
Additional Method ◽  
Engineering Approach ◽  
Agile Methodologies ◽  
Process Framework ◽  
Australian Standard ◽  
Agile Software

The use of a situational method engineering approach to create agile methodologies is demonstrated. Although existing method bases are shown to be deficient, we take one of these (that of the OPEN Process Framework) and propose additional method fragments specific to agile methodologies. These are derived from a study of several of the existing agile methods, each fragment being created from the relevant powertype pattern as standardized in the Australian Standard methodology metamodel of AS 4651.

Using Wiki for Managing Knowledge in Agile Software Development

2016 ◽  
pp. 397-423
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Software Development ◽  
Software System ◽  
Web Environment ◽  
The Past ◽  
Agile Methodologies ◽  
The Social ◽  
Industrial Software ◽  
Agile 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 Enablers and Adoption Scenario in Industry Context

2015 ◽  
pp. 157-178
Author(s):  
Vinay Kukreja ◽  
Amitoj Singh
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
User Requirements ◽  
Distributed Environment ◽  
Team Members ◽  
Agile Methodologies ◽  
Software Development Methodologies ◽  
Agile Software

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.

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

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.

A Framework for Analyzing Structural Mechanisms Deployed to Support Traditional and Agile Methods

2021 ◽  
pp. 205-227
Author(s):  
Michal Dolezel ◽  
Alena Buchalcevova
Keyword(s):  
Software Development ◽  
Classification Scheme ◽  
Organizational Structures ◽  
Agile Software Development ◽  
Agile Methods ◽  
Two Dimensional ◽  
Dimensional Classification ◽  
Agile Software ◽  
Structural Mechanisms ◽  
Development Methods

People rely on structures to make their worlds orderly. This chapter conceptually probes into the problem of the differences between organizational structures deployed in traditional and agile environments. The authors develop an argument that all common forms of organizational entities can be classified by involving a two-dimensional classification scheme. Specifically, they constructed a typology to examine the issues of formal vs. informal authority, and disciplinarity vs. cross-functionality in terms of their significance for traditional and agile software development workplaces. Some examples of concrete organizational forms—including traditional project team, independent test team, self-organizing agile team and developers' community of practice—are discussed. In sum, they argue that by employing this classification scheme, they can theorize the nature of the on-going structural shift observed in conjunction with deploying agile software development methods. They acknowledge that the structures have fundamentally changed, terming the move “democratization” in the software development workplace.

Extending Security in Agile Software Development Methods

2007 ◽  
pp. 143-159 ◽  
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
R. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Extending Security in Agile Software Development Methods

2008 ◽  
pp. 845-858
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
T. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

scholarly journals Adopting to Agile Software Development

2014 ◽  
Vol 16 (1) ◽  
pp. 64-70 ◽  
Author(s):  
Gusts Linkevics
Keyword(s):  
Expert System ◽  
Reference Material ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Complex Process ◽  
Agile Software

Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for a particular organization or a team. This research focuses on identification of agile methods and practices. Result of the research is the ranking of agile methods, practices and their usage trends. As some terms of agile software development are interpreted differently in different organizations and teams, terminology used is analyzed. Results of the research can be used as a reference material for those who are planning to adopt agile methods or are looking for the next agile practice to implement. Results will be used for the development of an expert system to support agile adoption.

Sign in / Sign up

Export Citation Format

Share Document