Development processes are evolved over years, waterfall approach no longer in practice, we are evolved into so called iterative methodologies where change in requirement are accepted, but still, there are delays, development failures, dissatisfaction of customers.
All these continues, because of scheduling and estimating the development and delivery as sequence of phases, all these phases are continues process, never going to be in the state of completed, a constant change will be there as a iteration. This can be solved only by scheduling, estimating and delivering applications with the set of feature it is going to offer, something like, in the first phase we are going to deliver this set of features, in the next phase, we are going to deliver this set, etc, Evolution delivery is the process of delivering software in small, incremental stages. An initial prototype, subset of the software is build and tested. New features are added and existing features refined with successive versions of the system. The prototype evolves into the finished product. You can see this approach in the whole Microsoft product range, they start with the functional prototype, then they release the product just to be in that domain, then they start adding features one by one and dominate the market in few versions. This what happened in Microsoft Office, Money and of course IE.
Comments