If you have been involved in very many BPM projects you have inevitably seen some which progressed through the entire development lifecycle with no major warning signs only to fail when put into production. They fail because the delivered system does not solve the problem which the business needs solved. They typically go through a complete lifecycle with verification at each stage. The Business writes its requirements. Business Analysts turn these into a functional requirements document, approved by the business. The development team creates then implements designs and finally QA tests the system and verifies that it satisfies the documented requirements. Yet in spite of all of this, the resulting system is not usable for its intended purpose.
