Adding planned design to xp might help novices' productivity (or might not): two controlled experiments

Authors:
René Noël;Gonzalo Valdes;Marcello Visconti;Hernán Astudillo
Affiliations:
Universidad Técnica Federico Santa María, Valparaíso, Chile;Universidad Técnica Federico Santa María, Valparaíso, Chile;Universidad Técnica Federico Santa María, Valparaíso, Chile;Universidad Técnica Federico Santa María, Valparaíso, Chile
Venue:
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Year:
2008

Citing 5
Cited 0

Extreme programming explained: embrace change

Extreme programming explained: embrace change
Case study: extreme programming in a university environment

ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Introducing XP into Greenfield Projects: Lessons Learned

IEEE Software
Using Extreme Programming in a capstone project

ACE '04 Proceedings of the Sixth Australasian Conference on Computing Education - Volume 30
Software Engineering: A Practitioner's Approach

Software Engineering: A Practitioner's Approach

Quantified Score

Hi-index	0.00

Visualization

Abstract

Extreme Programming (XP) suggests using Evolutionary design, always implementing the simplest solution that satisfies the current iteration's requirements, instead of Planned (or Traditional) up-front design. Some developers have questioned the usefulness of Evolutionary approach's enabling practices (e.g., refactoring, test-driven development) arguing for the naturalness of, and need for, Planned design. Two controlled experiments were conducted to compare both approaches regarding product quality and programmer productivity. Results from both studies show that (1) there is no significant difference in the product quality, independently of experience, but (2) novices are more productive using the Planned approach.