Essay On Waterfall Model

2239 Words5 Pages

Agile Waterfall Hybrid Model
A Collaborative Approach
Version 0.1
10-March-2014

REVISION HISTORY
Version Effective Date (DD/MM/YYYY) Brief Description of Change Affected Section(s) Prepared By Reviewed By Approved By
0.1 27-Feb-14 Initial Draft Harshpal Singh

TABLE OF CONTENTS
1 Overview 6
2 Waterfall Model 7
2.1 Advantages of Waterfall Model 7
2.2 Disadvantages of Waterfall Model 7
3 Agile Model 8
3.1 Advantages of Agile Model 8
3.2 Disadvantages of Agile Model 8
4 Collaborative (Hybrid) Model 9
4.1 Advantages of Collaborative Model 10
5 Overview of ACCA Account 11
5.1 What went wrong in Online IR project? And Lessons learnt 11
5.2 Additional best practices in a Hybrid model 12
6 Conclusion 15

LIST OF IMAGES
Figure 1: Waterfall Model 7
Figure 2: Agile Model………………………………………………………………………………………………..8
Figure 3: Collaborative (Hybrid) Model………………………………………………………………………..…..9
Figure 4: Model used by ACCA for Exam Entry project……………………………………………………14

1 Overview
The Waterfall Model has been the ideal choice for software development. In this model, an idea become a usable software in a sequential process that cascade through the stages of Initiation, Analysis, Implementation, Testing and Maintenance. But it has some disadvantages. Agile software development evolved as a solution to the disadvantages of Waterfall model. Instead of a sequential design process, the Agile methodology follows an incremental approach.
When clients/firms who were used to following Waterfall model switched to Agile, the transition brought with it many issues.The reason being inadaptability to a different approach to software development. The end product turned out to be a disaster. A new methodology has thus evolved, combibining the best of both ...

... middle of paper ...

... team is going to adopt. This requires proper planning. Factors like budget, time, resource utilization, complexity of requirements, etc. should be considered in adopting a software model.

Hybrid model is still in a nascent stage. As more and more companies will adopt it, we will learn more about this concept.

The Agile manifesto asks us to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

Whereas, the hybrid model does not adhere to it 100 percent. It believes all aspects are important. It is upto the clients/project managers to decide which aspect to value more and which aspect to value less.
References
http://www.wikipedia.org/ http://www.mountaingoatsoftware.com/ http://www.accaglobal.com/gb/en.html

Open Document