written 6.8 years ago by | modified 2.8 years ago by |
Subject: Software Engineering
Topic: Agile Software Development
Difficulty: High
written 6.8 years ago by | modified 2.8 years ago by |
Subject: Software Engineering
Topic: Agile Software Development
Difficulty: High
written 6.7 years ago by |
Example: Google is working on project to come up with a competing product for MS Word, that provides all the features provided by MS Word and any other features requested by the marketing team. The final product needs to be ready in 10 months of time. Let us see how this project is executed in traditional and Agile methodologies. In traditional Waterfall model –
At a high level, the project teams would spend 15% of their time on gathering requirements and analysis (1.5 months)
20% of their time on design (2 months)
40% on coding (4 months) and unit testing
20% on System and Integration testing (2 months).
At the end of this cycle, the project may also have 2 weeks of User Acceptance testing by marketing teams.
In this approach, the customer does not get to see the end product until the end of the project, when it becomes too late to make significant changes.