Proceedings of the second Nordic conference on Human-computer interaction
Evolving legacy system features into fine-grained components
Proceedings of the 24th International Conference on Software Engineering
Internet Software Engineering: A Different Class of Processes
Annals of Software Engineering
Field Experiences with eXtreme Programming: Developing an Emergency Response System
Journal of Management Information Systems
Agile systems development and stakeholder satisfaction: a South African empirical study
Proceedings of the 2008 annual research conference of the South African Institute of Computer Scientists and Information Technologists on IT research in developing countries: riding the wave of technology
Information and Software Technology
Modeling dynamics in agile software development
ACM Transactions on Management Information Systems (TMIS)
| Hi-index | 0.01 |
To those who are unfamiliar with the method, eXtreme Programming might conjure up visions of programmers madly hacking away without concern for analysis, architecture, design, or consequences. Indeed, people have frequently made such accusations. Yet such claims are not only baseless, they are diametrically opposed to what XP is all about. XP is the brainchild of K. Beck (2000). It is a software development method that views people, rather than paper, as a project's most potent element. Its primary motive is to start a dialog between the people involved in a project (customers and programmers). It facilitates this by identifying the parties in the conversation and arming them with the clear knowledge of what they are responsible for communicating to others