Incorporating Traditional Project Management Methodologies

We use cookies to give you the best experience possible. By continuing we’ll assume you’re on board with our cookie policy

Spiral methodology; it is the evolutionary step from the waterfall where the various steps are staged for multiple deliveries or handoffs. The ultimate evolution from the water fall is the spiral, taking advantage of the fact that development projects work best when they are both incremental and iterative, where the team is able to start small and benefit from enlightened trial and error along the way. The spiral methodology reflects the relationship of tasks with rapid prototyping, increased parallelism, and concurrency in design and build activities.

The spiral method should still be planned methodically, with tasks and deliverables identified for each step in the spiral. The above two models represent the traditional approaches to software development life cycle (SDLC) methodologies. At the time of their conception, they were complex processes and served best for the development then. With the continued metamorphosis and dynamism of the problems and processes requiring software, there is now a realization that processes remain forever dynamic.

What works today might not necessarily work tomorrow. In this age of consumerism and where the consumer is king, a realization that no two consumers are the same is key. Thus the general consensus is SDLC has to be dynamic. Designed in such a way as to allow for self correction and improvement without having to redisign the whole process. To allow for different solutions for similar situations taking into account the unique characteristics of each situation.

Iterative Model; it does not attempt to start with a full specification of requirements. Instead, development begins by specifying and implementing just part of the software, which can then be reviewed in order to identify further requirements. This process is then repeated, producing a new version of the software for each cycle of the model. Consider an iterative lifecycle model, which consists of repeating the following, four phases in sequence: – A Requirements phase, in which the requirements for the software are gathered and analyzed.

Iteration should eventually result in a requirements phase that produces a complete and final specification of requirements. – A Design phase, in which a software solution to meet the requirements is designed. This may be a new design, or an extension of an earlier design. – An Implementation and Test phase, when the software is coded, integrated and tested. – A Review phase, in which the software is evaluated, the current requirements are reviewed, and changes and additions to requirements proposed.

Get help with your homework

Haven't found the Essay You Want? Get your custom essay sample For Only $13.90/page

Sarah from CollectifbdpHi there, would you like to get such a paper? How about receiving a customized one?

Check it out