- Tags:: [[Software Development]] [[Agile]] [[Software Testing]] - Last Updated: [[2020-12-29]] - Date Created: [[2020-09-07]] - De-emphasis on documentation - Agile methodologies tend to downplay the need for documentation, handling it one of two ways: - Documentation is not done. - Documentation is done, but by a separate team. - It doesn't cater for projects where a large amount of up-front planning must be done. - "`Certain organizations still require up-front planning due to the sheer scale of their deliveries (no one is jumping into Sprint 1 to start building a new data warehouse without some planning…) `" - It assumes that each sprint starts from scratch to a certain extent, when sometimes projects begin with existing resources. - "`Here is a peer-reviewed paper from NASA arguing for The Business Case for Spiral Development in Heavy-Lift Launch Vehicle Systems The Spiral Development process is now being widely used for large Government program acquisitions and lends itself to the project described here. The main advantage of this concept is that it builds on existing capabilities and assets, as opposed to starting up a “new sheet” vehicle program from scratch. Spiral Development designs recombine existing assets in new configurations to function in extrapolated operating conditions. `" - Agile is primarily concerned with describing how people should work within the development team; the [[Agile Manifesto]] does not describe how Agile can be implemented at an enterprise level. - [[Agile for enterprises]]