The case for collaborative programming
Communications of the ACM
Effective Java programming language guide
Effective Java programming language guide
Agile Software Development with Scrum
Agile Software Development with Scrum
Test Driven Development: By Example
Test Driven Development: By Example
Strengthening the Case for Pair Programming
IEEE Software
Test-Driven Development as a Defect-Reduction Practice
ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
Are Reviews an Alternative to Pair Programming?
Empirical Software Engineering
A multiple case study on the impact of pair programming on product quality
Proceedings of the 27th international conference on Software engineering
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
Two controlled experiments concerning the comparison of pair programming to peer review
Journal of Systems and Software
Agile Retrospectives: Making Good Teams Great
Agile Retrospectives: Making Good Teams Great
Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise
IEEE Transactions on Software Engineering
Impact of pair programming on thoroughness and fault detection effectiveness of unit test suites
Software Process: Improvement and Practice
Proceedings of the 2005 conference on Software Engineering: Evolution and Emerging Technologies
Empirical evidence principle and joint engagement practice to introduce XP
XP'07 Proceedings of the 8th international conference on Agile processes in software engineering and extreme programming
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Pair programming vs. side-by-side programming
EuroSPI'05 Proceedings of the 12th European conference on Software Process Improvement
On the effects of pair programming on thoroughness and fault-finding effectiveness of unit tests
PROFES'07 Proceedings of the 8th international conference on Product-Focused Software Process Improvement
Hi-index | 0.00 |
Applying changes to software engineering processes in organisations usually raises many problems of varying nature. Basing on a real-world 2-year project and a simultaneous process change initiative in Poland the authors studied those problems, their context, and the outcome. The reflection was a need for a set of principles and practices to help introduce eXtreme Programming (XP). In the paper the authors extend their preliminary set, consisting of the Empirical Evidence principle, exemplified using DICE®, and the practice of the Joint Engagement of management and the developers. This preliminary collection is being supplemented with the Capable Leader, as well as the Skilled and Motivated Team practices based on the DICE® framework as well.