Extreme programming explained: embrace change
Extreme programming explained: embrace change
All I really need to know about pair programming I learned in kindergarten
Communications of the ACM
Extreme programming applied: playing to win
Extreme programming applied: playing to win
Pair Programming Illuminated
The collaborative software process(sm)
The collaborative software process(sm)
Agile Software Testing in a Large-Scale Project
IEEE Software
Current State of Agile User-Centered Design: A Survey
USAB '09 Proceedings of the 5th Symposium of the Workgroup Human-Computer Interaction and Usability Engineering of the Austrian Computer Society on HCI and Usability for e-Inclusion
Hi-index | 0.00 |
Many of the twelve carefully defined practices of Extreme Programming are tightly coupled. The various practices have checks and balances on each other and are, in many ways, dependant on each other. Therefore, neglecting essential practices can have sub-optimal or negative consequences to team results. The practices that are actually utilized in team development can often be attributed to the perceptions of the value and difficulty of the practices by the developers on the team. Through two surveys answered by 27 developers, we have assessed the utilization of and the sentiments towards the XP practices. In general, these developers we surveyed valued and utilized most of the practices.