Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 529 papers for “Extreme programming practices”

Extreme research: applying extreme programming practices to research

Toleman, Mark · University of Southern Queensland ePrints (University of Southern Queensland) · 2007

[Introduction]: A few years ago, my colleagues and I embarked on a journey that had multiple rationales and multiple outcomes. We had all been software developers at some point in our professional lives and we noticed a growing interest in the software developer community about so-called Agile methods, and eXtreme Programming (XP) in particular. None of us had explicitly applied these methods in the projects in which we had been a part, but we did have some other colleagues who had and still were. As academics, these Agile methods interested us because our developer colleagues were reporting significant benefits of using them. Many of the practices seemed to reflect the way these developers preferred to work and since traditional software development methods had a relatively low adoption rate, perhaps these new methods provided a more relevant approach. We also saw a research opportunity, a gap, with many practitioner reports but little academic research focussing on Agile methods. Another rationale was to build research capacity by mentoring young researchers in designing, conducting and reporting research.

Cited by 0Open access

Adopting eXtreme programming practices for teaching object oriented programming

Keefe, Karen Dianne. · Monash University · 2022

This thesis was scanned from the print manuscript for digital preservation and is copyright the author. Researchers can access this thesis by asking their local university, institution or public library to make a request on their behalf. Monash staff and postgraduate students can use the link in the References field.

Cited by 0Open access

Adopting eXtreme programming practices for teaching object oriented programming

Keefe, Karen Dianne. · Figshare · 2022

This thesis was scanned from the print manuscript for digital preservation and is copyright the author. Researchers can access this thesis by asking their local university, institution or public library to make a request on their behalf. Monash staff and postgraduate students can use the link in the References field.

Cited by 0Open access

Adopting eXtreme programming practices for teaching object oriented programming

Keefe, Karen Dianne. (12387523) · INDIGO (University of Illinois at Chicago) · 2022

This thesis was scanned from the print manuscript for digital preservation and is copyright the author.\n Researchers can access this thesis by asking their local university, institution or public library to\n make a request on their behalf. Monash staff and postgraduate students can use the link in the References field.

Cited by 0Open access

Best practices in extreme programming course design

Kai Stapel, Daniel Lübke, Eric Knauss · 2008

Teaching (and therefore learning) eXtreme Programming (XP) in a university setting is difficult because of course time limitations and the soft nature of XP that requires first-hand experience in order to see and really learn the methods. For example, iterations are either shorter or fewer than appropriate. In this paper we present the properties to tune when designing an eXtreme Programming course. These are the properties we gathered by conducting three XP labs as part of our software engineering teaching. Within this paper we describe our set-up as well as the important properties. Lecturers and teachers can use this property system and combine it with their own constraints in order to derive a better XP lab for their curriculum.

Cited by 32

ENHANCEMENTS IN SCUM FRAMEWORK USING EXTREME PROGRAMMING PRACTICES

Nabil A. Darwish · International journal of intelligent computing and information sciences/International Journal of Intelligent Computing and Information Sciences · 2014

This paper is concerned with providing an enhanced Scrum framework that combines some practices of eXtreme Programming (XP) approach in Scrum framework to produce quality software on time. XP and Scrum are two agile software development methods. While Scrum is focused on project management, XP is focused on Software development; nevertheless, they both can be used to participate in the development of any software project independently or together. This paper presents the main concepts, features, phases, artifacts, and roles of Scrum as well as a brief introduction to XP and its practices. In this paper, the researcher presents how to combine some XP practices into Scrum activities. The researcher exploits the features and best practices of the two methods to propose an enhanced Scrum framework that includes an elaborated set of guidelines for achieving each Scrum activity. Therefore, the enhanced Scrum framework is more applicable than many previous attempts in this domain. The enhanced Scrum framework has been validated by a group of 17 experts and specialists in software projects.

Cited by 3Open access

E.: Best Practices in eXtreme Programming Course Design

Kai Stapel, Daniel Lübke, Eric Knauss · 2008

Teaching (and therefore learning) eXtreme Programming (XP) in a university setting is difficult because of course time limitations and the soft nature of XP that requires first-hand experience in order to see and really learn the methods. For example, iterations are either shorter or fewer than appropriate. In this paper we present the properties to tune when designing an eXtreme Programming course. These are the properties we gathered by conducting three XP labs as part of our software engineering teaching. Within this paper we describe our set-up as well as the important properties. Lecturers and teachers can use this property system and combine it with their own constraints in order to derive a better XP lab for their curriculum.

Cited by 0

Software Configuration Management Practices for eXtreme Programming Teams

Ulf Asklund, Lars Bendix, Torbjörn Ekman · 2004

Extreme Programming (XP) is becoming popular as a software development method and there is quite a lot of literature describing its philosophy and practices. However, in all of this literature Software Configuration Management (SCM) is almost never mentioned explicitly, leaving XP practitioners with the impression that SCM is not needed and SCM people with the impression that XP is not sound from an SCM perspective. We carried out a more profound analysis of XP and its practices seen from an SCM perspective. We found that in general XP and its practices do not go against common SCM standards, if we take into consideration that the XP context is different from that of more traditional projects. However, some SCM aspects need to be made explicit and a number of SCM-specific sub-practices need to be added to make XP a complete and sound development method seen from an SCM perspective. We report on how we implemented “our findings ” on several dozen XP projects and our experience from doing this through several iterations. 1.

Cited by 13

10/28/2009 Extreme Programming Extreme Programming An Agile Process � Definition � Origins � Core Values � Best Practices

Chad Levesque, Core Values · 2009

What is it? � Extreme Programming, or XP, is a methodology. � A set of principles and practices that guide the rapid development of software. � A type of Agile Development, focused on collaborative, iterative development. � Named because it takes 12 well-known software “best practices ” to their logical extremes. Origins � In the 1990’s, the dot-com boom and the increasing importance of speed-tomarket introduced a strain on the software industry. � Many development teams were facing problems where traditional practices were failing while attempting to adapt to customers ’ increasingly rapid requirements changing.

Cited by 0

Extreme Programming Practices Used to Facilitate Effective Project Management

Clement James Goebel, Menlo Innovations · 2003

Extreme Programming codifies a set of practices that many software developers are willing to adopt in both action and spirit. Many of these practices are grounded in fundamental project management theory. When software development teams embrace the practices of Extreme Programming an opportunity is created for a broad set of project management practices to become meaningful and accessible to the developers, while at the same time making clear, unambiguous information available to the project managers.

Cited by 4

Extreme Programming Practices Used to Facilitate Effective Project Management

Clement James, Goebel Iii, Menlo Innovations · 2008

It is unfortunate that many software development professionals regard project management as formalized paper pushing. It is even more unfortunate when a project manager focuses primarily on the scheduling of meetings, and the creation or maintenance of artifacts instead of fostering high quality communications and coordination between project stakeholders.

Cited by 0

A Grounded Theory of Developer Communication in Extreme Programming Practices

Ben Hur C. Viray · Zenodo (CERN European Organization for Nuclear Research) · 2024

There is evidence that Extreme Programming (XP) software development practices are still actively used by Information Technology (IT) projects under the Agile methodology, one of the famous software development life cycle (SDLC) models. However, more information about the communication between programmers or developers for these XP practices is needed. Thus, this study, employing a constructivist grounded theory (CGT) design which emphasizes the construction of knowledge through the interpretation of data, was conducted to explore developer communication for significant XP practices. For the initial data, the researcher was fortunate to have the participation of eleven out of fifteen IT professionals, each with at least a decade of work experience. Their expertise was invaluable in shaping the direction of the research. Three out of four identified developers also participated in a follow-up questionnaire. Subsequently, semi-structured key informant interviews were conducted, focusing on their top three practices: Planning Game, Test-Driven Development (TDD), and Small Releases, which were selected based on their perceived importance in IT projects. During the interviews, it became evident that the developers play multiple roles, each significantly influencing communication. These fourteen identified roles highlight their work’s diverse and complex nature: Assessor, Collaborator, Coordinator, Designer, Developer, Documenter, Interpreter, Learner, Mentor, Negotiator, Presenter, Researcher, Tester, and Translator. The developers interacted with seven teams categorized into four groups based on their modes of communication: Direct Managers and Change management under Linear-Interactional, Business Team under Interactional, External Developers, Functional Resources, and Technical Team under Interactional-Transactional, and Transactional-Interactional for Internal Developers. With all the combined practices, roles, and interactions, this study has proposed an XP Developer Communication (XPDC) model. This framework can serve as a guide for understanding and improving developer communication in XP projects. For instance, it can help identify the key roles and their communication needs or guide the selection of appropriate communication modes for different teams. Although not all XP practices are covered, the components are enough to cover all the essential developer communication practices in XP.

Cited by 0Open access

A Grounded Theory of Developer Communication in Extreme Programming Practices

Ben Hur C. Viray · Zenodo (CERN European Organization for Nuclear Research) · 2024

There is evidence that Extreme Programming (XP) software development practices are still actively used by Information Technology (IT) projects under the Agile methodology, one of the famous software development life cycle (SDLC) models. However, more information about the communication between programmers or developers for these XP practices is needed. Thus, this study, employing a constructivist grounded theory (CGT) design which emphasizes the construction of knowledge through the interpretation of data, was conducted to explore developer communication for significant XP practices. For the initial data, the researcher was fortunate to have the participation of eleven out of fifteen IT professionals, each with at least a decade of work experience. Their expertise was invaluable in shaping the direction of the research. Three out of four identified developers also participated in a follow-up questionnaire. Subsequently, semi-structured key informant interviews were conducted, focusing on their top three practices: Planning Game, Test-Driven Development (TDD), and Small Releases, which were selected based on their perceived importance in IT projects. During the interviews, it became evident that the developers play multiple roles, each significantly influencing communication. These fourteen identified roles highlight their work’s diverse and complex nature: Assessor, Collaborator, Coordinator, Designer, Developer, Documenter, Interpreter, Learner, Mentor, Negotiator, Presenter, Researcher, Tester, and Translator. The developers interacted with seven teams categorized into four groups based on their modes of communication: Direct Managers and Change management under Linear-Interactional, Business Team under Interactional, External Developers, Functional Resources, and Technical Team under Interactional-Transactional, and Transactional-Interactional for Internal Developers. With all the combined practices, roles, and interactions, this study has proposed an XP Developer Communication (XPDC) model. This framework can serve as a guide for understanding and improving developer communication in XP projects. For instance, it can help identify the key roles and their communication needs or guide the selection of appropriate communication modes for different teams. Although not all XP practices are covered, the components are enough to cover all the essential developer communication practices in XP.

Cited by 0Open access

Analyzing The Use Of Large Language Models In eXtreme Programming Agile Practices

Largura, Andrea · AMS Degree Thesis (University of Bologna) · 2024

In this dissertation we investigate the utilization of Large Language Models (LLMs) to enhance the effectiveness of Extreme Programming (XP) practices in agile software development. The study delves into various XP practices through a mixed-methods approach combining quantitative and qualitative analysis. The overarching aim is to discern how LLMs can augment
\n human developers’ capabilities within agile practices, examining aspects such
\n as efficiency, collaboration dynamics, code quality, and overall productivity.
\n Our study reveals that the practices that tend to work better with LLMs include those that involve repetitive tasks and require extensive code generation
\n or manipulation, such as Test-Driven Development (TDD) and collaborative
\n programming scenarios. Despite the need for human validation, LLMs can
\n significantly enhance productivity in these contexts. Conversely, practices relying heavily on human judgment, such as user story and use case evaluation, may not benefit as much from LLM integration. We conclude with recommendations for future research such as improving LLMs prompts, and
\n addressing security issues.

Cited by 0Open access

Optimal coordination of crystallization batch processes using rules and practices of extreme programming

Wolfgang Böck, Harald König, Lothar Litz · 2004

This contribution describes the development and implementation of a complex control system for a sugar production plant. Using practices of extreme programming control algorithms have been generated to realize an optimal coordination of twenty batch crystallizers. Thus the equilibrium of mass and energy flows as well as the improvement of sugar quality parameters could be achieved. The developed batch control is working on the level of process coordination, acting directly on the level of process control. All algorithms are implemented in Matlab/Simulink and handle about 300 binary and continuous I/O-signals in real time connection. Therefore a client server structure is established between Matlab and the process control system.

Cited by 1