Waterfall AND Agile? Is it good for an IT Organization to be following both Agile and Waterfall Methodologies? There are Organizations that follow Waterfall methology for certain types of projects and Agile for certain types. Is it good to have both methodologies followed in the same organization? > Sukhbinder B.: Yes, definitely! Waterfall methodology is very popular in public sector organisations. I feel there is a lack of knowledge and experience of Agile methodology. Personally I believe the mixture of Agile and Waterfall methodology is the best combination as they both complement each other. When designing websites, interactive Information DVDs or other solutions I have made use of Agile methodology informally i.e. planning, designing, implementing and evaluating each stage in small increments. In my opinion the Waterfall methodology is quite dangerous when replacing large IT systems costing millions of pounds as there is no going back after the requirements have been signed off. Another drawback in my experience is that at the time of designing and testing sometimes the requirements need to change to accommodate better outcome or output which is not allowed with Waterfall methodology. On the other hand, software procurement of IT systems costing millions of pounds under Agile methodology might suffer if organisations are going through constant reviews and loosing staff especially staff working the Agile project. Another drawback of the Agile methodology is that the systems might cost a lot more than originally thought because of the time it takes to complete. If we were to combine the 2 methodologies then we could overcome the drawbacks and enhance the benefits. However, for the solutions which need constant evaluation and evolution, Agile methodology is a must and solutions which are needs to be replaced or procured once in 10 years then Waterfall methodology will work.
Posted on: Wed, 04 Sep 2013 08:14:24 +0000
Trending Topics
Recently Viewed Topics
© 2015