Suitability of Agile Model for projects
I have been following agile in my projects recently and I have increasingly been experiencing the need to decide on the suitability of using the agile model for product development/project execution. Most of the times we use agile in projects because it is customer demanded; we do it without analyzing the suitability and feasibility of using agile for the project.
While it is imperative in this competitive world of the IT industry to comply with customer demands, it is also equally important to educate (if required) and negotiate with the customer on the suitability of the methodology/model for the project. Typically, a high-bred model combining waterfall, iterative and agile seems to be more apt for outsourced IT projects with diverse teams both onshore and offshore.
Estimating an Agile project:
The estimation for a agile project can be done in two parts:
- the first part to cover conceptualization, feasibility, prototyping and high-level architecture/design, which would follow the traditional waterfall approach.
- The second part would cover prioritization of requirements, low-level design, coding, testing and implementation, which would follow an agile approach taking into consideration additional overheads for iteration and collaboration.
In this approach, the …
