The Impact of Agile Methods on Managing IT Professionals

2011 ◽  
pp. 233-253
Author(s):  
Mark Toleman ◽  
Fiona Darroch ◽  
Mustafa Ally
Keyword(s):  
Software Development ◽  
Empirical Research ◽  
System Development ◽  
Detailed Examination ◽  
Extreme Programming ◽  
Agile Methods ◽  
Organizational Impact ◽  
Development Environment ◽  
Firm Basis ◽  
The Impact

This chapter examines the potential for agile methods to provide mechanisms to deal with the software development environment that has evolved in response to the inadequacies of traditional, heavyweight development approaches. A framework is proposed which identifies three major areas of organizational impact that require management attention when undertaking system development in the new environment. This is followed by a detailed examination of the constructs within those three main areas, and assesses the potential for agile methods to address those issues. The current literature and empirical research into agile methods (and eXtreme Programming in particular) underpins the proposals for dealing with contemporary software development challenges. The authors hope that understanding the environment from the perspective of the framework will assist managers in their perception of the challenges of contemporary software development, and provide them with a firm basis on which to consider the adoption of agile methods.

scholarly journals AGILE SOFTWARE DEVELOPMENT

2021 ◽  
Vol 5 (12) ◽  
Author(s):  
Gopalkrishna Waja ◽  
Jill Shah ◽  
Pankti Nanavati
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Extreme Programming ◽  
Software Project ◽  
Research Papers ◽  
Agile Methodology ◽  
Development Methodology ◽  
Software Development Methodology ◽  
Agile Software ◽  
The Impact

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.

THE ORGANIZATIONAL IMPACT OF INTEGRATING MULTIPLE TOOLS

1991 ◽  
Vol 01 (02) ◽  
pp. 165-188 ◽  
Author(s):  
MIKE P. PAPAZOGLOU ◽  
LOUIS MARINOS ◽  
NIKOLAOS G. BOURBAKIS
Keyword(s):  
Software Development ◽  
Data Sharing ◽  
Data Modeling ◽  
Organizational Impact ◽  
Tool Integration ◽  
Development Environment ◽  
Software Development Environment ◽  
Object Management ◽  
Management Issues ◽  
Software Development Environments

This paper elaborates on the data modeling and data sharing issues that arise when developing and interconnecting modern software development environments. It primarily focuses on the investigation of adjoined object management issues for tool integration, software development environment extensibility, and interconnectivity.

Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation

2017 ◽  
Vol 02 (02) ◽  
pp. 1750007
Author(s):  
Taiga Mitsuyuki ◽  
Kazuo Hiekata ◽  
Takuya Goto ◽  
Bryan Moser
Keyword(s):  
Software Development ◽  
Process Simulation ◽  
System Development ◽  
Development Project ◽  
Development Projects ◽  
Software Project ◽  
Conditional Response ◽  
Agile Process ◽  
Requirement Changes ◽  
The Impact

For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.

scholarly journals The Role of Customers in Extreme Programming Projects

2021 ◽  
Author(s):  
◽  
Angela Michelle Martin
Keyword(s):  
Software Development ◽  
Well Being ◽  
Development Project ◽  
Extreme Programming ◽  
Agile Methods ◽  
Acceptance Testing ◽  
Software Development Project ◽  
Big Picture ◽  
Definition Of ◽  
Key Steps

<p>eXtreme programming (XP) is one of a new breed of methods, collectively known as the agile methods, that are challenging conventional wisdom regarding systems development processes and practices. Practitioners specifically designed the agile methods to meet the business problems and challenges we face building software today. As such, these methods are receiving significant attention in practitioner literature. In order to operate effectively in the world of vague and changing requirements, XP moves the emphasis away from document-centric processes into practices that enable people. The Customer is the primary organisational facing role in eXtreme Programming (XP). The Customer's explicit responsibilities are to drive the project, providing project requirements (user stories) and quality control (acceptance testing). Unfortunately the customer must also shoulder a number of implicit responsibilities including liaison with external project stakeholders, especially project funders, clients, and end users, while maintaining the trust of both the development team and the wider business. This thesis presents a grounded theory of XP software development requirements elicitation, communication, and acceptance, which was guided by three major research questions. What is the experience of being an XP Customer? We found that teams agree that the on-site customer practice is a drastic improvement to the traditional document-centric approaches. Our results indicate, however, that the customers are consistently under pressure and commit long hours to the project in order to fulfil the customer role. So while this approach to requirements is achieving excellent results, it also appears to be unsustainable and thus constitutes a great risk to XP projects. Who is the XP Customer? The initial definition of XP resulted in many people interpreting the onsite customer to be a single person. This research has highlighted that a customer team always exists, and goes further to outline the ten different roles that were covered on the team, which range from the recognised "Acceptance Tester" role to the less recognised roles of "Political Advisor" and "Super-Secretary". What are the practices that support an XP Customer to perform their role effectively on a software development project? An additional eight customer-focused practices have been uncovered to supplement the existing XP practices. These customer-focused practices together enable customers to sustainably drive XP projects to successful completion. The practices range from those that specifically focus on interaction (both with the programmer team and the larger organisation) e.g. "Programmer On-site" and "Roadshows" to those that specifically look to the well-being and effectiveness of the customer (e.g. "Pair Customering") to those that highlight the key steps or activities that need to occur along the way (e.g. "Big Picture Up-Front" and "Recalibration").</p>

scholarly journals The Impact of Factors of Success on the In-House Software Development for Preserving Tacit Knowledge: Survey

2016 ◽  
Vol 2 (3) ◽  
Author(s):  
Mohammed W. Shbair, Wael F. AlSarraj, Khalid M. Kahloot
Keyword(s):  
Software Development ◽  
Knowledge Sharing ◽  
Tacit Knowledge ◽  
Positive Impact ◽  
Third Party ◽  
Development Environment ◽  
Development Organization ◽  
Tacit Knowledge Sharing ◽  
The Impact ◽  
Factors Of Success

Factors of success are aimed to provide knowledge-intensive organisations to better manage their knowledge value. There are multiple ways to capture organization’s knowledge and make it available to all their members while it is not easy to capture/share the tacit knowledge among the stakeholders. The purpose of this study was to investigate the impact of factors of success on the in-house software development for preserving tacit knowledge. We conducted a survey to study the impact of these five factors on the tacit knowledge sharing between the developers within the in-house software development environment. This paper is firstly exploring the definition of the knowledge and introducing the types of knowledge those are explicit and tacit knowledge. We discuss the in-house software development concept in which the non-IT organizations may need to develop their own software internally with no need to have a third party software development organization. For tacit knowledge sharing, we considered four factors reviewed in other researches and we added to them the pair programming as a practice. Case study is local bank in Palestine. Based on the results we have, it is confirmed the hypothesis of a positive impact of factors of success on the process of knowledge sharing.

scholarly journals - Development of Heavy Equipment Rental System Using eXtreme Programming Method

2019 ◽  
Vol 6 (1) ◽  
pp. 24-31
Author(s):  
Johanes Fernandes Andry
Keyword(s):  
Software Development ◽  
System Design ◽  
System Analysis ◽  
System Development ◽  
Extreme Programming ◽  
Application Development ◽  
Team Members ◽  
Time Of Application ◽  
Heavy Equipment ◽  
The Right

Many system development consultants nowadays using the XP framework (eXtreme Programming) in software development, This is based on the needs of the era where software can be completed quickly and when user software development is involved. The XP framework does not need too many team members, so it emphasizes effectiveness of work. In software development must begin with good planning to avoid patchwork (software crisis) in software development. The stage in research on the development of rental heavy equipment applications with an XP framework start from planning, designing, coding, testing and releasing software. Studies that do in this research include: literature studies, interviews, observations, document examinations. Next is do the analysis on the application made, and make documentation for system development. That was done as a system analysis and system design in the research. The selection of the right framework at the time of application development is very important, so that the application can be completed on time. The XP framework focuses more on making programs, the system design is enough with the CRC (Class Responsibility Collaborator). In the framework of XP, it always involves users during application development. Each module made by programmers that always tested by the system test section, so the applications that are made can be completed on time, suitable with user needs, and have high quality.

Agile Embedded System Development versus European Space Standards

2017 ◽  
Vol 8 (1) ◽  
pp. 1-23
Author(s):  
Ville Rantala ◽  
Kaisa Könnölä ◽  
Samuli Suomi ◽  
Minna Isomäki ◽  
Teijo Lehtonen
Keyword(s):  
Software Development ◽  
Embedded System ◽  
System Development ◽  
Agile Methods ◽  
Agile Development ◽  
Space Systems ◽  
European Cooperation ◽  
Space Projects ◽  
Mission Critical ◽  
Development Methods

Agile development methods are widely utilized in software development. There is a growing interest and effort to introduce them to other areas of technology, such as development of space systems. Space systems are typically safety- and mission-critical and therefore their development is strongly regulated and standardized. European Cooperation for Space Standardization (ECSS) has created a collection of standards which are extensively followed mainly in European space projects. In this paper, a review and discussion are presented to find out the conflicts between the agile development and the ECSS standards. The presented analysis and discussion show that the ECSS standards do not fully prevent the utilization of agile methods. However, there are aspects to be taken into account in the development methods, contracts and tailoring of standards.

Agile Team Measurement to Review the Performance in Global Software Development

2022 ◽  
pp. 2015-2025
Author(s):  
Chamundeswari Arumugam ◽  
Srinivasan Vaidyanathan
Keyword(s):  
Software Development ◽  
Performance Indicators ◽  
Gold Standard ◽  
Extreme Programming ◽  
Global Software Development ◽  
Development Environment ◽  
Worst Case ◽  
Team Members ◽  
Project Environment ◽  
Programming Software

This chapter is aimed at studying the key performance indicators of team members working in an agile project environment and in an extreme programming software development. Practitioners from six different XP projects were selected to respond to the survey measuring the performance indicators, namely, escaped defects, team member's velocity, deliverables, and extra efforts. The chapter presents a comparative view of Scrum and XP, the two renowned agile methods with their processes, methodologies, development cycles, and artifacts, while assessing the base performance indicators in XP setup. These indicators are key to any agile project in a global software development environment. The observed performance indicators were compared against the gold standard industry benchmarks along with best, average, and worst-case scenarios. Practitioners from six agile XP projects were asked to participate in the survey. Observed results best serve the practitioners to take necessary course corrections to stay in the best-case scenarios of their respective projects.

Sign in / Sign up

Export Citation Format

Share Document