Introducing 

Prezi AI.

Your new presentation assistant.

Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.

Loading…
Transcript

4. Planning the Next Iteration/Phase

3. Development and Test

Customer evaluates the project and identifies issues in the project that will be dealt with in the next spiral.

If everything is good, project is released

-develop the planned project

-test the developed project

-development may be done using different approaches. Eg. Waterfall

Advantages

2. Identify and Resolve Risks

Risk mitigation is the focus.

Project is broken up in to smaller parts in order to determine risks in the development process.

Generally this includes two prototypes and an operational prototype.

-Operational prototype

-Evolutionary prototype

-Throw away prototype

1. One of the most flexible models in place; Development phases can be determined by the project manager

2. Project monitoring is easy and effective

3. Risk management is one of the in-built features of the model

4. Changes can be introduced later in the life cycle as well.

5. Project estimates (schedule, cost etc.) become more realistic as the project moves forward

6. Suitable for high risk projects, where business needs may be unstable.

7. Highly customized product can be developed using this.

Spiral Strategy Model

1. Determining Objectives

The client meets with the developer and the developer determines:

- software objectives

-design alternatives

-constraints such as cost, technology, and schedule

Disadvantages

By: Kevin, Arjun & Neil

Spiral Methodology

Spiral Model

  • First Described by Barry Bohem in 1986

  • Adopts elements of other process models (ex. incremental, waterfall and evolutionary prototyping)

  • Choices are based on a project's risks and then generate a appropriate process model

  • Cost involved is usually high

  • Complicated approach

  • Rules and protocols should be followed properly to effectively implement the model

  • Not suitable for low risk projects.

  • Meeting budgetary and scheduling requirements is tough

  • Documentation required in intermediate stages

Thank You

Learn more about creating dynamic, engaging presentations with Prezi