Extreme programming explained: embrace change
Extreme programming explained: embrace change
Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People
Improving validation activities in a global software development
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Integrating hundred's of products through one architecture: the industrial IT architecture
Proceedings of the 24th International Conference on Software Engineering
Can you Trust a Single Data Source Exploratory Software Engineering Case Study?
Empirical Software Engineering
Surviving Global Software Development
IEEE Software
Improving Validation Activities in a Global Software Development
IWSM '00 Proceedings of the 10th International Workshop on New Approaches in Software Measurement
Tricks and traps of initiating a product line concept in existing products
Proceedings of the 25th International Conference on Software Engineering
Automating regression testing for evolving GUI software: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice - 2003 International Conference on Software Maintenance: The Architectural Evolution of Systems
Studying the Fault-Detection Effectiveness of GUI Test Cases for Rapidly Evolving Software
IEEE Transactions on Software Engineering
Distributed Information System Development: Review of Some Management Issues
OTM '09 Proceedings of the Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: ADI, CAMS, EI2N, ISDE, IWSSA, MONET, OnToContent, ODIS, ORM, OTM Academy, SWWS, SEMELS, Beyond SAWSDL, and COMBEK 2009
| Hi-index | 0.00 |
Daily build is a software development paradigm that originated in the PC industry to get control of the development process, while still allowing the focus on end user requirements and code. The PC industry used daily build to avoid chaos in increasingly larger applications in an environment without a strong development process. Ericsson Radio Systems has chosen to implement daily build to increase the focus on end user requirements and code, but from a different starting point with a traditionally strong development process. In this article we discuss our experiences with daily build and feature oriented development in this context. We also relate our experience to the concept of extreme programming, arguing that our ideas can help extend the applicability of extreme programming beyond small co-located projects.