Where most application developers shun requirement changes, we embrace change. We look at requirement changes as a vital part of the development process.
Requirements are gathered and a functional specification is then created. The specification creates some buzz and requirements may change based on the functional specification.
A model or mock up is created; the stake holders review the model. The model is modified and the process begins all over again. The model is what everyone looks at and understands.
We start development with an idea that we roll out in stages. In this way we can show it to the stake holders, so they can modify the requirements again.
It is this continuous modification before project release that insures the application is what the users need. In the long run, this makes for a more successful project and reduces the overall time to completion.