Phased Methodology

The objective of a phased approach to development is to break your site into individual components or features that can stand on their own. You start with a needs analysis, identifying the purpose of your site. For instance, assume your site will be a combination of an e-commerce site, library site, community site, and a product brochure site. You can proceed one of two ways.

1. Collect requirements and create a design for the entire system (all parts) and then develop each part one phase at a time

2. Collect requirements, create a design, then develop and implement each part of the site

Once you have your phases decided, you can use whatever development methodology you feel fits for your project. You could use RAD for phase 1 and Scrum for phase 2 and then create your own strategy for phase 3.


The phased approach enables you to make incremental investments in your site, to launch the site one phase at a time. This is advantageous if you have a vision for something grand but don’t have the funds to do it all in one effort.


A drawback to the phased approach is the risk of building the fi rst component in such a way that it prevents the subsequent components from being implemented appropriately or without restructuring a feature from a previous phase. This method requires you to spend some time during each phase thinking about the next phase and how your decisions today affect what you need for tomorrow.