9-11 minutes<\/p>\n
There are a number of different approaches<\/a> in the software development industry \u2013 some are new takes on old methods and others have adapted a relatively new approach. The two most commonly used methods in this field are the Agile such as, Scrum<\/a> , Kanban and Lean and etc., and traditional Waterfall models such as structured methods or newer RUP.<\/p>\n Most software companies that follow these two models will argue that their chosen method is superior in respects, so before we answer the question, \u201cWhich one is more successful? We should look at their main differences.<\/p>\n Waterfall is a linear approach to software development process. Each of these represents a distinct phase of software development, and each phase generally finishes before the next one can begin. There is also typically a milestone between each development phase.<\/p>\n Thus the waterfall model maintains that one should move to a phase only when its preceding phase is reviewed and verified as shown in the Figure below:<\/p>\n Waterfall approach<\/p>\n For example:<\/p>\n Agile is derived using Lean thinking that applies \u201cLean\u201d concepts in the information technology environment. The key focus of the Lean approach is to:<\/p>\n Agile Approaches<\/p>\n Agile approach is the proven project management methodology that encourages the following key concepts:<\/p>\n Agile development<\/a> stages include traditional planning, analyzing requirements, design, coding, testing, and deployment, but they form a cycle rather than a line. This means the processes are flexible, repeatable, can happen in any order and in parallel. This allows gathering the user feedback, continuous testing against different environments and changing the scope of the project on the run.<\/p>\n The Waterfall Method\u2019s greatest strengths are its fixed costs and predictability. You know the price, and when it is going to be delivered. Its most significant weakness is its inflexibility. The Agile Method<\/a> is extremely flexible and could evolve into a significantly different product than was originally envisioned.<\/p>\nWaterfall Approaches<\/h3>\n
\n
\n
Agile Approaches<\/h3>\n
\n
\n
Agile Development \u2013 Iterative Lifecycle<\/h3>\n
The Foundation of Agile Approaches<\/h3>\n
\n
Agile vs Waterfall \u2013 Scope, Time and Cost Triangle<\/h3>\n