It’s important to follow a standardized approach to Web development.
The symptoms like projects going over-time and facing particular issues indicate that things are going wrong.
Adopt, Adapt or Build Your Own
There are three paths to choose from:
Evaluation Criteria :
Decide on the criteria by which you would evaluate like:
Complexity: Must be easy to understand yet should offer sufficient depth for guiding developers for custom web development
Size: A 10-page summary is better compared to 100 page document
Cost: The less money it required, the better it is
Risk: The methodology must not go wrong
Pragmatic: The solution must work, should not be based on theory
Rational Unified Process
It has problems like:
Process Monitor: It was more compact than RUP.
In-House Methodologies: In-house methodologies borrowed from another organization, also don’t work in custom wed development.
Traditional Methodologies: They involved longer time frames and failed to consider “soft” aspects of software development.
Agile Methodologies: Feature Driven Development (FDD) in agile methodology was well suited to Web development but requires some fine tuning.
An Overview of FDD
Why Apply FDD to Web Development?
The plus points of FDD were:
How to Manage the Transition?
Manage the transition by:
FDD for Small Teams
There are two main aspects of FDD for small projects:
FDD Overview for Web Development
The following is a high-level overview of FDD followed in Web Development (India):
FDD is good for Web development but does not have the complete answer.