Proceedings of the 2008 international workshop on Scrutinizing agile practices or shoot-out at the agile corral
Journal of Systems and Software
The impact of agile principles on market-driven software product development
Journal of Software Maintenance and Evolution: Research and Practice
Empirical Software Engineering
Information and Software Technology
The right process for each context: objective evidence needed
Proceedings of the 2011 International Conference on Software and Systems Process
Adopting agile practices in teams with no direct programming responsibility - a case study
PROFES'11 Proceedings of the 12th international conference on Product-focused software process improvement
Deploying agile practices in organizations: a case study
EuroSPI'05 Proceedings of the 12th European conference on Software Process Improvement
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
A practical approach for deploying agile methods
XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering
Systematic piloting of agile methods in the large: two cases in embedded systems development
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
Successful extreme programming: Fidelity to the methodology or good teamworking?
Information and Software Technology
Methodology Mashups: An Exploration of Processes Used to Maintain Software
Journal of Management Information Systems
When agile meets the enterprise
Information and Software Technology
Extended iterative maintenance life cycle using eXtreme programming
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
The purpose of this paper is to present results of introducing an agile process based on extreme programming, XP, in an evolutionary and maintenance software development environment. The agile process was introduced to a large software development organization. The process was applied by a team during eight months. The conclusions indicate that it in this case is more difficult to introduce XP, in its original appearance, to the case environment than to less complex environments. The complexity of the organization made it necessary to redesign many of the practices in order for them to fit the needs of the software development team.