Shortening the iteration cycle and development phase is not a problem in itself, but when combined with the long lead times required for harness development, problems can arise. Harness lead times are typically around 23-26 weeks from design release to product delivery. The difference in lead times depends on the number and schedule of changes the project performs during the development cycle. In order to meet the deadline for the next development phase, the harness must be frozen (at which point the data/design has been released and must be updated through a formal change management process), resulting in little to no time between the two development phases to review or Implement lessons learned. When the next freeze comes, vehicle testing often hasn’t even begun. Once the next build phase begins, this can lead to a lot of rework, or a large number of change requests in a short period of time to implement changes into the harness design as quickly as possible before the next freeze. Both alternatives have the potential to degrade the harness and cause unnecessary delays during functional verification.