The stated, accepted philosophy for systems development is that the development process is a well understood approach that can be planned, estimated, and successfully completed. This has proven incorrect in practice. SCRUM assumes that the systems development process is an unpredictable, complicated process that can only be roughly described as an overall progression. SCRUM defines the systems development process as a loose set of activities that combines known, workable tools and techniques with the best that a development team can devise to build systems. Since these activities are loose, controls to manage the process and inherent risk are used. SCRUM is an enhancement of the commonly used iterative/incremental object-oriented development cycle.
CITATION STYLE
Casanave, C. (1997). Business-Object Architectures and Standards. In Business Object Design and Implementation (pp. 7–28). Springer London. https://doi.org/10.1007/978-1-4471-0947-1_2
Mendeley helps you to discover research relevant for your work.