scholarly journals Teaching Agile Methods to Software Engineering Professionals: 10 Years, 1000 Release Plans

Author(s):  
Angela Martin ◽  
Craig Anslow ◽  
David Johnson
Author(s):  
Zaidoun Alzoabi

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.


Author(s):  
Achrak El Mehdi ◽  
Chkouri Mohamed Yassin ◽  
El Kadiri Kamal Eddine

2022 ◽  
Vol 31 (1) ◽  
pp. 1-49
Author(s):  
Anders Sundelin ◽  
Javier Gonzalez-huerta ◽  
Krzysztof Wnuk ◽  
Tony Gorschek

Context: The concept of software craftsmanship has early roots in computing, and in 2009, the Manifesto for Software Craftsmanship was formulated as a reaction to how the Agile methods were practiced and taught. But software craftsmanship has seldom been studied from a software engineering perspective. Objective: The objective of this article is to systematize an anatomy of software craftsmanship through literature studies and a longitudinal case study. Method: We performed a snowballing literature review based on an initial set of nine papers, resulting in 18 papers and 11 books. We also performed a case study following seven years of software development of a product for the financial market, eliciting qualitative, and quantitative results. We used thematic coding to synthesize the results into categories. Results: The resulting anatomy is centered around four themes, containing 17 principles and 47 hierarchical practices connected to the principles. We present the identified practices based on the experiences gathered from the case study, triangulating with the literature results. Conclusion: We provide our systematically derived anatomy of software craftsmanship with the goal of inspiring more research into the principles and practices of software craftsmanship and how these relate to other principles within software engineering in general.


Author(s):  
Zaidoun Alzoabi

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.


10.28945/3357 ◽  
2009 ◽  
Author(s):  
Sita Ramakrishnan

Software Engineering capstone projects have been running successfully since 2002 for the final year software engineering (SE) students of the Bachelor of Software Engineering (BSE) Program at Monash University, accredited by Engineers Australia and Australian Computer Society. Agile methods are being increasingly adopted in the industry. In this paper, we describe the objectives of SE capstone projects and report on how our innovative projects for supporting the software engineering projects in undergraduate programs at Monash University have evolved and have been scaled up to support agile SE capstone projects. We detail the evolution from our early innovative software engineering projects in the mid 1990s that have served as catalysts for more innovation in the early 2000, and for scaling up agile SE projects with increasing central technical infrastructure support from the School. More recently, we have adapted our approach with a combination of open-source and commercial tools under academic licence for developing and deploying these projects effectively with agile distributed teams. The paper concludes with a discussion on lessons learnt from our innovative projects in the mid 1990s and from the evolution in scaling up to agile practices for the SE capstone projects from 2002-2008.


Author(s):  
Shah Imran Alam ◽  
Syed Shahabuddin Ashraf ◽  
Faria Iqbal

Software engineering is comparatively a new addition in the vocabulary of traditional engineering discipline. Being a late joiner, software engineering obtained many of its process foundation from traditional engineering domains. But the ever-changing business needs and the growing complexity that are required to be addressed in a software application, have kept software engineers on their toes to continuously improve the development process to meet and to manage the challenges in it. Agile project management has been the most significant development in IT industry to manage software development process that could deliver quality software product at an extremely high speed compared to any of the predecessor methods. The key abstraction of all the flavors of agile methods is adaptability towards change. This adaptability is achieved by the use of quality practices and practitioners in a closely integrated working environment that also involves the customers in the development process more than ever before. IT industry has acknowledged the significant success of the agile process and has been a buzz-word for a decade in the IT industry. The paper is built upon a comparative study of the application of Agile project management in both IT and non-IT industries. It further discusses the adaptability of agile methods and its potential to benefit the Non-IT industry in managing the quality of deliverables while maintaining high delivery speed. The discussion extends its boundaries to cover the reason for less acceptance of Agile process in non-IT industry and put forth an argument against the suitability of some of the success-factors in the case of non-IT industries, while they enabled a high acceptance of the Agile process in IT-industry.


2002 ◽  
Vol 12 (3) ◽  
pp. 187-195 ◽  
Author(s):  
Barry Boehm ◽  
Dan Port ◽  
A. Winsor Brown

Sign in / Sign up

Export Citation Format

Share Document