Any working process greatly benefits from a solid basis of configuration management. The aim is complete traceability, at any given time, of the entire development process -- who changed what, when, and for what reason.
Let us start "at the beginning". A good configuration management needs to trace the following information on its requirements: which requirements belong to the project and where to find them? Are they valid or outdated, and when and why were the requirements changed or complemented?
The same applies to information on any other artefact of a software project: design concepts belonging to the requirements, implementation concepts, test concepts evolving in the course of development, sources, libraries, build files, testing results, change requests, problem reports, etc., including any production tools and the development environments.
Mastering the configurations ensures a firm grip on software development, regardless of whether the processes are rather strict or rather agile.
