2000 · 57 citations · 1 references
ComputingComputer ScienceFeature EngineeringRequirements EngineeringSoftware EngineeringAgile DevelopmentSoftware ConstructionSoftware DesignSoftware Development Life Cycle ManagementSystems Development Life CycleCo-located CollaborationExtreme ProgrammingSoftware Development Life CycleSoftware Development LifecycleUser Requirements Analysis
Daily build originated in the PC industry to impose order on growing software projects while keeping the focus on end‑user requirements and code quality. Ericsson Radio Systems adopted daily build to enhance end‑user focus and code quality within its already robust development process, and the article reports on their experiences with daily build and feature‑oriented development. The authors relate their experience to extreme programming, suggesting that their ideas can broaden extreme programming’s applicability beyond small, co‑located teams.
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.
1