The spiral methodology has no governors to control oscillations. More often than not, the length or number of cycles grow unbounded. There are no constraints on the requirement team to ``get things right the first time''. This leads to the sloppy thinking from the requirement team giving the implementation team many tasks that eventually get thrown out. The architecture team is never given a complete picture of the product and hence will not be able to complete an efficient global architecture. There are no firm deadlines. Cycles continue with no clear termination condition. The implementation team may be chasing a continuously changing architecture and dynamic product requirements.