Ed's computing and Business Process

A new project (lets call it project "slurpy") has been kicked off to our fix terribly broken business processes involving starting new projects. We currently have to go through a discovery phase, then a design, then a build then an implementation. Each phase is a discrete project. This is great if you are rolling out a new cellular phone network, but a little onerous if you want add a photo to the internal address book.

Despite this enormous administrative overhead, projects often get through "design" without a single requirement written down.

9 out of 10 failed projects fail because of poor requirements. I hope the first paragraph of recommendations from project Slurpy is "DEFINE YOUR REQUIREMENTS!"