Waterfall workflow example
In a Waterfall approach to building a customer relationship management (CRM) system, the project moves through separate, sequential phases with little overlap. The workflow starts with a Requirements Phase, where business analysts might spend weeks or months creating a comprehensive 100-page document detailing every feature the system should have. Only when this document is approved does the project move to the Design Phase, where architects and designers create detailed technical plans and user interface designs. Next comes the Implementation Phase, where developers build the entire system according to the specifications. This is followed by the Testing Phase, where quality assurance tests the completed code. After testing and bug fixes, the project enters the Deployment Phase, where the entire system is released at once. Finally, the Maintenance Phase begins, where post-launch problems are fixed. The important characteristic of this workflow is that feedback from users or changes to requirements typically don't happen until very late in the process, often after months of development.
Pro Tip: Even when using Waterfall for regulatory or contractual reasons, try to include more frequent review points to reduce the risk of major misalignments.