Incomplete requirements - Pitched

It’s my suspicion that the typical person who enjoys writing code doesn't like agile and would prefer a waterfall / BUS approach. (They also tend to not like users or customers, which is where most problems start!) The reality of modern software development, especially for smaller SMEs building their own products, is that the comprehensive specification document is like rocking horse shit! Instead they receive “what could be cobbled together in the time allowed”. However, there are things you can do help yourself. Is your design and spec generation process defined? (And by defined I mean written down not “in John's head”). You'll probably end up with several versions, one for each type of problem, but once it’s written down, you can track whether a feature went through the process or not. No doubt the ones that just had to be rushed through and didn't follow the process will cause your dev team the most headaches, but I bet you'll also find they have the most bugs, or took much longer to develop than estimated or receive the worst user feedback. You’ll soon find enough evidence that everyone in the business will want everything to run through the full dev design process.