The traditional waterfall life peri...

The traditional waterfall life period has been the mainstay for software developer for many years. For software effects that do not change true much once they are specified, the waterfall mould is still viable. However, for software produces that have their feature places redefined during development because of user feedback and other factors, the traditional waterfall protoplast is no longer appropriate.

Hewlett-Packard, like other organizations developing software consequences is always looking for ways to improve its software unravelling processes. One software development order that has become quite popular at HP is called Evolutionary increase or EVO (see reference 1 and the article in succession page 25). EVO uses small, incremental work releases, frequent delivery to users, and dynamic plans and processe Although EVO is relatively simple in conception its implementation at HP has included the pair significant challenges and notable benefits. This paper begins with a brief discussion about the EVO course and its benefits, then describes software devises at three HP divisions that have used EVO and finally discusses critical succes factors and elucidation lessons about EVO.

The EVO Method

Fig. 1 point out tos the difference between the traditional waterfall life round of years and the EVO life revolution of time The EVO development model divides the unfolding cycle into smaller, incremental waterfall patterns in which users are able to come by access to the product at the extremity of each cycle. The users provide feedback in succession the product for the planning stage of the nearest cycle and the development team accords often by changing the crops plans, or process. These incremental round of yearss are typically two to four weeks in duration and continue until the fruit is shipped.

At Hewlett-Packard, we have plant that it is possible to relax a certain number of of our original ideas regarding EVO In particular, it isn't absolutely necessary to deliver the performance to external customers with customer-ready documentation, training, and support to benefit from EVO

Benefits of EVO

Successful use of EVO can benefit not alone business results but marketing and internal operations as well. From a business perspective, the biggest benefit of EVOis a significant reduction in risk for software shoot forwards This risk might be associated with any of the many ways a software exhibit can go awry, including missing scheduled deadlines, unusable effects wrong feature sets, or poor quality. by the agency of breaking the project into smaller, more manageable pieces and by means of increasing the visibility of the management team in the devise these risks can be addressed and managed.

Because a certain design issues are cheaper to reduce through experimentation than through analysis, EVO can bring costs by providing a structur disciplined avenue for experimentation. Finally, the inevitable change in expectations when users begin using the software scheme is addressed by EVO's early and ongoing involvement of the user in the progress to maturity process. This can result in a harvest that better fits user distresss and market requirements.

EVO allows the marketing department access to early deliveries, facilitating exhibition of documentation and demonstrations. Although this access must be given judiciously, in near markets it is absolutely necessary to start the sales circle of time well before product release. The ability of developer to be agreeable to to market changes is increased in EVO because the software is continuously evolving and the unfolding team is thus better positioned to change a feature risk or release it earlier.

Short, common EVO cycles have some distinct advantages for internal processe and tribe considerations. First, continuous process improvement becomes a more realistic possibility with one-to-four-week periods Second, the opportunity to present to view their work to customers and hear customer answers tends to increase the motivation of software developer and consequently encourages a more customer-focused orientation. In traditional software throws that customer-response payoff may no other than come every few years and may be in such a manner filtered by marketing and management that it is meaningless. Fig. 2 illustrates the difference between the traditional life period and EVO in terms of in what way much user feedback can be look fored during product development.

Finally, the cooperation and flexibility required by means of EVO of each developer originates in greater teamwork. Since scheduling and appurtenance analysis are more rigorous, les dead time is exhausted waiting on other people to unbroken their work.

While the benefits can be substantial, implementation of evolutionary increase can hold significant challenges. It requires a fundamental shift in the way individual thinks about managing projects and definitely requires more management effort than traditional software unravelling methods. The next section examines to what degree EVO was applied in three different HP divisions and what we learned from the experience.

Evolutionary exhibition in Practice

Some form of EVO has been used in at least eight Hewlett-Packard divisions in from one side of to the other ten major projects. Much of this has been done drawing forward expertise from HP's Corporate Engineering software initiative, which is a central service arrange of consultants in software engineering and management (see the article upon page 42). The software initiative dispose is currently leveraging existing experience and promoting the use of EVO at HP