on Fri, 09/01/2017 - 00:35
When using open source systems, you can use thousands of features simply by turning them on. You don't have to create the code for the functions you need, just activate them; saving time and money. It's pretty cool stuff. But, the benefit in using open source systems can also be a big challenge when it comes to coordination different aspects of a project. Not everything exists in harmony- even when it is easy to turn on or off- and project planning/development methodologies can mean the difference between reaching your goal and just not.
Typically when you're walking through the phases of production you will analyze needs, collect requirements, form a design then develop and implement. If you walk through these phases one at a time while documenting your steps then you may not have a difficult time ensuring that your requirements get implemented during the development phase.
As with anything, there are going to be methods of production ranging from "careless" (according to some) to "excessively orderly" (according to others.) Some people believe that a non-linear approach to site production yields solutions incapable of supporting your big picture and may even create conflicts between site features. This camp recommends that you spend time detailing your goal, gameplan and collecting all the requirements you want in the end before DOing anything.
Others believe that if you know the goal of your site and a commonly used module recipe already exists for that purpose that you should dive right in. Play it by ear and decide what you want as you're going. This method is as extreme as the first method mentioned although neither is unheard of. As with any pair of extremes, there is a happy medium to be had and you will probably use pieces from more than one method to define how your site production will occur.
Several common development methodologies are:
1. Waterfall Methodology 2. Agile Methodologies 3. RAD Methodology 4. Spiral Methodology 5. Phased Methodology