This article does an excellent job of simplifying the development cycle. It does leave one critical step out, though.
Nearly every designer, whether computer software or other products, skip an essential step between the implementation phase and the next iteration, thus leaving the poor users of the new product hanging.
The costly developers and experts move the next iteration. The users are left with a separate warranty group who may be unfamiliar with the product. Possibly, they have no direct support at all.
The developers and experts should not be allowed to go on vacation and should not be assigned a new project for a short time after the implementation. They need to be available to fix the bugs that crop up in the first week of use.
The last step in all of my 100+ projects was Post-Implementation Adjustments. Time was included for that step.
Some managers tried to call that “warranty,” but that’s BS.
