Why agile is less efficient than Waterfall?
I am also practicing a agile environment but I always thinking that water fall model is a more efficient in software development sometimes people are saying that agile is a cheaper than waterfall model but it is not true it is depend on the application or nature of project, team size,timeline,budget.
The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation and Maintenance.
If in the beginning of the project failures are detected, it takes less effort (and therefore time and money) for this error. In the waterfall model phases to be properly sealed first before proceeding to the next stage. It is believed that the phases are correct before proceeding to the next phase. In the waterfall model lay the emphasis on documentation. In the newer software development methodologies makes it less documentation. This means that when new people in the project and people leave it is difficult to transfer knowledge. This disadvantage is not the traditional waterfall model. Milestones can be used to monitor the progress of the project to estimate. Better forecast estimation.
There is some disadvantages on agile methods
1) More than one people can handle a team.
2) Only senior programmers are capable of taking the kind of decisions required during the development process. Hence it has no place for newbie programmers, unless combined with experienced resources.
3) Difficult forecast.
4) There is lack of emphasis on necessary designing and documentation.
5) The project can easily get taken off track if the customer representative is not clear what final outcome that they want.
6) If the team members are not committed, the project will either never complete or fail.
7. It is good for small, fast moving projects as it works well only with small team.
8. If any of the team members leave during a development it can have a huge inverse effect on the project development.
9.less time to test.
The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation and Maintenance.
If in the beginning of the project failures are detected, it takes less effort (and therefore time and money) for this error. In the waterfall model phases to be properly sealed first before proceeding to the next stage. It is believed that the phases are correct before proceeding to the next phase. In the waterfall model lay the emphasis on documentation. In the newer software development methodologies makes it less documentation. This means that when new people in the project and people leave it is difficult to transfer knowledge. This disadvantage is not the traditional waterfall model. Milestones can be used to monitor the progress of the project to estimate. Better forecast estimation.
There is some disadvantages on agile methods
1) More than one people can handle a team.
2) Only senior programmers are capable of taking the kind of decisions required during the development process. Hence it has no place for newbie programmers, unless combined with experienced resources.
3) Difficult forecast.
4) There is lack of emphasis on necessary designing and documentation.
5) The project can easily get taken off track if the customer representative is not clear what final outcome that they want.
6) If the team members are not committed, the project will either never complete or fail.
7. It is good for small, fast moving projects as it works well only with small team.
8. If any of the team members leave during a development it can have a huge inverse effect on the project development.
9.less time to test.
Comments
Post a Comment