An iterative approach to Web development

June 2009

When developing applications, one of the major challenges involves managing and planning for the impact of changes on the product development cycle. This is especially true when the development cycle extends over a few months.

The iterative approach to development proposes a series of safeguards that allow for easier management and quicker integration of changes. This approach considers change as an inevitable part of development projects.

Definition

Iterative development consists of delivering parts of a system or application at regular intervals, called iterations. An iteration is made up of a series of activities that include conducting needs analysis, developing parts of the system, then deploying and testing them for QA. In the end, one or more functionalities are ready for integration into the final product.

Classic sequential approach ("waterfall") compared to the iterative approach

Imagine an online application development project that offers 20 different functionalities (20 scenarios).

In the waterfall approach:

• A complete analysis is performed to determine the details of all scenarios
• The architect puts together a detailed architecture for each component of the application
• The functional analysis and architecture document are sent to the developers, who implement all 20 scenarios
• QA testing is performed for each of the 20 scenarios
• Product is handed over to client for acceptance testing
• Changes requested by client are implemented
• Final product is finally delivered

Before the product is final, there are almost always changes that need to be implemented. This often results in additional delays.

In the iterative approach, the steps remain the same but they occur within an iteration whose duration is predetermined. There are a number of iterations, and the above-mentioned steps are repeated within each one.

For example, we could decide that scenarios 10 and 15 will be developed as part of iteration one. For iteration two, there may be some corrections to scenarios 10 and 15, as well as a few more scenarios taken from the original list, and so on.

Advantages of using iterative development

The iterative development approach offers the following advantages:

• It is more adaptable to changes, and considers changes an integral part of the application development cycle, rather than a nuisance
• It allows for early detection of risks associated with a given project
• QA can be performed at the end of each iteration
• Project managers are in a better position to assess the impact of changes on the delivery dates

Overall, the iterative approach allows for adjustments earlier in the development process, and not once everything is finished (and all hours worked). You have the opportunity to visualize the results of each iteration, witness the progress of the project, and express any concerns or preferences as the project evolves.

With the sequential approach, it is difficult to measure exactly how well the project is progressing within a wide timeframe. When a project manager asks the age-old question, "Are we on time?" developers will have two possible answers. "Yes" if the delivery date is far in the future, or "no" if the project is due in just a few days. There is little leeway, and it is sometimes too late to react or extend deadlines.

With the iterative approach, the project manager controls progress through each iteration, which lasts only a few weeks. This project manager can assess the situation and have a better margin of manoeuvrability because problems will become apparent at the start of the project.

Web Solutions from Bell

Bell provides expertise in Web development, usability testing, digital marketing, and much more.

We customize the iterative process to each project for the best results. Our team of dedicated project managers and developers work to meet your requirements, budget and timelines.

Have a project in mind? Contact us today to discuss your requirements.