Traditional Vs Agile Methodologies

2077 Words9 Pages

Critically evaluate the differences between the traditional heavyweight methods and agile methodologies, using a suitable example.
Abstract
A software development methodology refers to the framework that is used to structure, plan, and control the process of developing a software product. Due to the growing complexity in software products, different methodologies have emerged since the past years each having their own strengths and weaknesses. Software methodologies fall under two categories that are heavyweight and lightweight. Heavyweight methodologies also known as traditional methods deliver software through a sequence of well defined requirements, design processes and documentation. On the other side, lightweight methodologies commonly …show more content…

Waterfall Waterfall approach is a linear approach that emphasizes on a sequential progression where each stage defines a series of activities and deliverables that must be completed before starting the next phase ensuring deadline control. The main stages identified are requirements capture, analysis, design, construction, testing, implementation, and maintenance
Product Requirements-Requirements capture is one of the most determinant stages in waterfall model as change or misunderstanding can be very costly to correct. For the University web-based information system, product manager creates requirements documents that include the following requirements. The requirements elicitation and prioritization will help determine what should be tackle first and allow proper planning. Examples include:
• User should be able to view lecturers records
• User should be able to view student …show more content…

Developers and customers agree upon list of well defined requirements right from the start and no further customer involvement is considered until delivery. Full scope of work being identified right from the start allows proper planning, documentation and straightforward design. Milestones can be properly set allowing concise follow up on progression. On the other side, for agile, customers provides brief user stories that are just enough for implementing the primitive features. However, there is the opportunity for customers to see frequent working increments to better identify further requirements or improvement to existing ones as they often do not know what they want themselves. Furthermore, each iteration adds some business value to the final product. The customer implications can be a determining factor in the product success and increase quality as a whole. If the time to market is a main concern, agile can quickly produce a working version of the

Open Document