One strategy for achieving rapid development is to determine the area in which most of the time is spent on a typical project and then try to reduce that time. You can shrink some areas more readily than others, and attempting to reduce some areas can inadvertently lengthen the schedule.
You can view time on a software project from many angles, and the different views produce different insights into where the time goes. The next subsection presents the classic (phase-by-phase) view, and the subsections after that present other views.
Most projects start out in an ill-defined, pre-requirements phase that ...