Requirements churn—or changes to a product’s requirements—is inevitable, but there are ways to keep it from becoming excessive. Some churn is natural in the beginning of a project, as the developers refine their understanding of the product and technologies being used to develop it. In most cases, requirements stabilize after they become part of a baseline and the relevant stakeholders have signed off.

If the amount of churn is still high after this point, it can drive up costs, impact quality, or result in sacrificing key features or functionality in order to release the product on time.