Adding planned design to XP might help novices' productivity (or might not): Two controlled experiments. In pages 285-287, 2008.
doi  abstract   bibtex   
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. Copyright 2008 ACM.
@inproceedings{10.1145/1414004.1414053,
    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. Copyright 2008 ACM.",
    year = "2008",
    title = "Adding planned design to XP might help novices' productivity (or might not): Two controlled experiments",
    pages = "285-287",
    doi = "10.1145/1414004.1414053",
    journal = "ESEM'08: Proceedings of the 2008 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement"
}

Downloads: 0