Change requests are used to track and control all changes to the product and supporting systems (such as the configuration system). All change requests are initiated as the result of a defect found in a baseline. For example, if a meeting with the user uncovers new requirements, a defect is created documenting that the current requirements baseline is out of date. A change request must be created to propose bringing the requirements baseline up-to-date. All change requests are extensively analyzed for impact on the user, product, and teams. All change requests are reviewed by the change control board. The change control board has sole authority for accepting or rejecting change requests. If a change request is accepted, it is scheduled for a future iteration to be implemented.