eXtreme Programming

2011 ◽  
pp. 108-133
Author(s):  
Fabrizio Fioravanti
Keyword(s):  
The Other ◽  
Extreme Programming ◽  
Software Project ◽  
Design Development ◽  
Project Development ◽  
Success Story ◽  
Software Projects ◽  
Management Processes ◽  
Main Component ◽  
Development And Management

One of the emerging techniques that is becoming increasingly popular for managing software project is eXtreme Programming (XP) (Beck, 1999, 2000; Williams, 2000). XP surely changes the way in which we develop and manage software, as all the other methodologies related to the Agile Manifesto do (Agile Alliance, 2001; Boehm, 2002; Cockburn, 2001; Highsmith, 2001; Rakitin, 2001). XP has been the methodology that I have adopted in recent years to develop and manage software projects — before modifying it in order to create my own methodology, ADPD (Agile and Defined Project Development), which is described in Chapter XI. In order to understand ADPD, it is necessary to acquire all the possible knowledge about XP, since ADPD is XP 80% and recognizes quite all the values of this revolutionary technique for developing and managing software projects. The most interesting feature of XP consists in the fact that it is human oriented (Brooks, 1995). XP considers the human factor as the main component for steering a project toward a success story. On the other hand, it is important to notice that XP is guided by programming rules, even if its more interesting aspects deal with the values that are the real guides for the design, development, and management processes.

Influential Agile Software Parameters

2011 ◽  
pp. 1938-1943
Author(s):  
Subhas C. Misra ◽  
Vinod Kumar ◽  
Uma Kumar
Keyword(s):  
Project Management ◽  
Software Process ◽  
Systems Development ◽  
The Other ◽  
Software Systems ◽  
Software Projects ◽  
Optimal Cost ◽  
Management Processes ◽  
Agile Software ◽  
Refining Processes

Successful software systems development is a delicate balance among several distinct factors (Jalote, 2002) such as enabling people to grow professionally; documenting processes representing the gained experiences and knowledge of the organization members; using know how to apply the suitable processes to similar circumstances; and refining processes based on achieved experience. Software projects have two main dimensions: engineering and project management. The engineering dimension concerns the construction of a system, and focuses mainly on issues such as how to build a system. The project management dimension is in charge with properly planning and controlling the engineering activities to meet project goals for optimal cost, schedule, and quality. For a project, the engineering processes specify how to perform activities such as requirement specification, design, testing, and so on. The project management processes, on the other hand, specify how to set milestones, organize personnel, manage risks, monitor progress, and so on (Jalote, 2002). A software process may be defined as “a set of activities, methods, practices, and transformations that people use to develop and maintain software, and the associated products and artifacts.”1 This is pictorially depicted in Figure 1 (Donaldson & Siegel, 2000).

eXtreme Programming, Agile Methodologies, Software Project Management, Customer Role, Rigorous Testing

2022 ◽  
pp. 163-182
Author(s):  
Kamalendu Pal
Keyword(s):  
Project Management ◽  
Software Development ◽  
Extreme Programming ◽  
Acceptance Testing ◽  
Software Project ◽  
Software Project Management ◽  
Software Projects ◽  
Agile Methodologies ◽  
Rigorous Testing ◽  
Software Development Methodologies

Agile software development methodologies are attracting attention from academics and practitioners for planning and managing software projects. The eXtreme Programming (XP) challenges conformist wisdom regarding software system development processes and practices as agile methodologies. To work efficiently in the current software development practice, characterized by requirements fuzziness, XP moves away from document-centric operations into people-centric management. In the XP-based software project, the customers play an essential role, having multiple responsibilities such as driving the project, gathering requirements (‘user stories'), and exercising quality control (or acceptance testing). Besides, the customers must liaise with external project stakeholders (e.g., funding authorities, end-users) while maintaining the development team's trust and the wider business. The success of such software project management practices relies on the quality result of each stage of development obtained through rigorous testing. This chapter describes three characteristics of XP project management: customer role, software testing feedback, and learning.

scholarly journals Scrumban: An Agile Integration of Scrum and Kanban in Software Engineering

2020 ◽  
Vol 9 (4) ◽  
pp. 1626-1634
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Engineering Management ◽  
Organizational Capabilities ◽  
Software Project ◽  
Project Development ◽  
Development Organizations ◽  
Internal States ◽  
Development Processes ◽  
Development And Management

Software Engineering (SE) technologies are emerging day by day and seeking ABPR (Agile Business Process Reengineering) for Software Engineering Management (SEM) frameworks in software development organizations. BPR can enable organizational capabilities to initiate and implement critical change in execution. Under the roof of agile and on the base of empiricism, the Scrum has been proven itself as an ABPR approach for software engineering management in the software development organizations, across the world, by improving productivity, self-organization and collaboration for standard software development processes. Scrum has been leading software project development practices using its own characteristics: Artifacts, Pillars, Values, Events and Roles. But still software project development organizations are facing some issues with their software project development and management processes, like no documentation policy which results into inaccurate estimation, internal states of each work item flowing through the Scrum Board, Sprint tracker and prediction towards goal achievement which can be considered as challenges for Scrum due its limitations as well as Scrum does not allow, any alteration in its rules. Such issues have raised a question against implementation of Scrum and have opened the door for the next level of research to answer the question, how to overcome the limitations of Scrum. Kanban can provide the solution to some of these issues but it can’t provide complete SEM solutions to software Development Organizations. The aim of this research study is empirical analysis about how the formation of hybrid framework Scrumban as an integration of Scrum with Kanban, can resolve challenges of Scrum; using literature reviews, case study reviews, and research surveys; and this research has proposed a conceptual customized Scrumban framework, by keeping Kanban in the center of customization under the bound of Scrum rules. This research also concludes limitations of Scrumban, like project documentation, planning, large scaled project, distributed environment, team capabilities etc.; as each method has its own limitations.

scholarly journals A Generic Agent Framework to Support the Various Software Project Management Processes

10.28945/3157 ◽  
2007 ◽  
Author(s):  
Rita Nienaber ◽  
Andries Barnard
Keyword(s):  
Project Management ◽  
High Rate ◽  
Software Project ◽  
Software Project Management ◽  
Software Projects ◽  
Management Processes ◽  
Generic Agent ◽  
Project Management Processes ◽  
Support Software ◽  
Rate Of Failure

Despite various research efforts originating from both academia and industry, software projects have a high rate of failure, more specific, software projects often do not comply with the traditional standard measurements of success, namely time, cost and requirements specification. Thus, there is a need for new methods and measures to support the software project management process. Globalisation and advances in computing technologies has changed the software project management environment. Currently software projects are developed and deployed in distributed, pervasive and collaborative environments and traditional project management methods cannot, and do not, address the added complexities inherent to this environment. In this paper the utilisation of stationary and mobile software agents is investigated as a potential tool to assist with the improvement of software project management processes. In particular we propose and discuss a software agent framework to support software project management. Although still in its initial phases, this research shows promise of significant results in enabling software developers to meet market expectations, and produce projects on time, within budget and to users’ satisfaction.

scholarly journals The Effects of Agile Methodologies on Software Project Management in Pakistani Software Companies

2021 ◽  
Vol 12 (3) ◽  
pp. 1717-1727
Author(s):  
Javed Iqbal Et.al
Keyword(s):  
Project Management ◽  
Software Development ◽  
Extreme Programming ◽  
Software Project ◽  
Software Project Management ◽  
Software Projects ◽  
Software Companies ◽  
Agile Methodologies ◽  
Management Factors ◽  
Main Determinants

Agile methodologies are always tends to increase the quality of software and also handling the complex software projects. However, the software companies in Pakistan have recently felt the disparity of producing successful software. In this context, an extensive survey has been conducted in 52 prominent software development companies of Pakistan to identify this remedy and the motivation behind this production discrepancy. It is revealed from the survey that there is a lack of empirical evidence in the relationship of agile methodologies with the effective and progressive management of software project management factors including, schedule, scope, risk, budget, quality and resources. Therefore, the proposed study delivers an extensive statistical comparison to determine the effectiveness of agile methodologies in terms of their effects on the project management factors. The results suggest that in general all agile methodologies play a significant role towards the successful software development in the software company. However, Extreme Programming, Scrum, Kanban and Agile modeling are the main determinants of production disparity among software companies. Furthermore, it is determined that the quality factor has a positive correlation with the rest of the factors. It is also found that the budget factor has significantly correlated with other five factors, while rest of the factors has insignificant correlation. We have also compared agile methodologies in terms of project management factors, which specify that each agile methodology has its own importance and effect with respect to managing different factors of project management.

scholarly journals Design of an environmental management information system for the Universidad Distrital

2022 ◽  
Vol 25 (1) ◽  
pp. 529
Author(s):  
Edwin Arturo Quintero Torres ◽  
William Andrés León Beltrán ◽  
Juan Manuel Sánchez Céspedes
Keyword(s):  
Environmental Management ◽  
Software Tool ◽  
Management Control ◽  
Extreme Programming ◽  
Customer Requirements ◽  
Design Development ◽  
Agile Methodology ◽  
Management Processes ◽  
Management Policies ◽  
Efficient Software

This article presents the design, development and implementation of a software tool, serving as an alternative to the problems involving management, control and reporting of processes within the institutional plan for environmental management (known as plan institucional de gestión ambiental (PIGA) by its Spanish acronym) for the Universidad Distrital Francisco José de Caldas. The software is focused on carrying out such processes to the automation setting, based on the extreme programming (XP) Agile methodology that mainly centers on the continuous development of the customer requirements to offer a more assertive tool, in line with the plan institucional de gestión ambiental in Spanish (PIGA) processes. The result is a complete satisfaction of users and a highly usable, adaptable and efficient software, inherently optimizing and automating the environmental management processes of the PIGA program. This work delivers an applet that meets the design and implementation requirements of environmental management policies. The proposed tool manages to reduce process-related times by 97%, therefore, allowing to aim efforts in other missional functions and increase the overall value offer of the organization.

scholarly journals Meningkatkan Akurasi Perkiraan Waktu Proyek Perangkat Lunak Dalam COCOMO II Dengan Mengubah Nilai Parameter

2019 ◽  
Vol 4 (1) ◽  
Author(s):  
Rahmi Rizkiana Putri ◽  
Weny Mistarika Rahmawati
Keyword(s):  
Cost Driver ◽  
Software Project ◽  
Effective Management ◽  
Project Development ◽  
Software Projects ◽  
Entire Process ◽  
Time Estimates ◽  
Time Changes ◽  
Parameter Values ◽  
Cocomo Ii

Good management of software projects can be obtained through accurate time estimates. When estimating less accurate time it will affect the lack of effective management of the software project and the entire process during project development. Barry Boehm, an inventor of COCOMO, has developed the COCOMO 1 cost driver that has an effect on the accuracy of the estimated time results. But if you only use the COCOMO II cost driver, it is still far from the accuracy of the desired results. Therefore it is necessary to change the values of parameters C and D for estimated time. Changes in parameter values are done by decreasing the initial gradation by 0,1 so that the approximate results become more optimal and close to the original values. Based on the implementation of the proposed method, the results show that the error decreases to% when compared to using only the COCOMO I and COCOMO II cost drivers without changing parameter values. So that the accuracy of the estimated project time can increase.

scholarly journals Monolithic Ontological Methodology (MOM): An Effective Software Project Management Approach

2021 ◽  
Author(s):  
Kamal Uddin Sarker ◽  
◽  
Aziz Deraman ◽  
Raza Hasan ◽  
Ali Abbas ◽  
...  
Keyword(s):  
Project Management ◽  
Performance Metrics ◽  
Stakeholder Involvement ◽  
Extreme Programming ◽  
Management Approach ◽  
Software Project ◽  
Software Projects ◽  
Analytic Hierarchy ◽  
Standard Organization ◽  
Standard Documentation

Due to rapid changes in software applications, especially incorporating the demands of self-regulating technologies becomes a major challenge in software projects. This research focuses on technological, managerial, and procedural challenges, which are believed to the most significant factors contributing to projects failure. To address these issues, this study proposes Monolithic Ontological Methodology (MOM) which addresses the weakness in the existing benchmark methodologies including PRINCE2, Extreme Programming, and Scrum in terms of project management, quality control, and stakeholder involvement. The MOM consists of seven phases and each phase has the required number of iterations until it is approved by management. The updated information is recorded and shared with the respective teams. The standard documentation with control language is structured by Descriptive Logic (DL) that reduces ambiguity and technical debate. Furthermore, the illustration of the MOM includes figures, logical expressions, and descriptions. To demonstrate the effectiveness of the proposed methodology, an Analytic Hierarchy Process (AHP) was performed. The findings indicate the validity of MOM concerning considered performance metrics. Although the applicability of the proposed methodology involves relatively more documentation and formalities. The adaptive nature of MOM makes it suitable for the standard organization and brings sustainability to the organization by implementing distributed project management.

Sign in / Sign up

Export Citation Format

Share Document