Question

Draw a comparison between the traditional system development methodologies and the agile methodology on the basis of following factors:

1. Project Size

2. People Factor

3. Risk Factors

Answer 1

Comparison of Traditional System development methodologies and Agile Methodology:

Traditional system development methodologies have been around for long years and then comes Waterfall model which has been widely used for both large and smaller system developments and it has been successful. Even though the model is success it has lot of drawbacks like no flexibility while changing the requirements, to follow high processes irrespective of size of project etc.,

Agile methods deal with unstable and volatile requirements by using a number of techniques, focusing on collaboration between developers and customers and support early product delivery.

Factors	Methodology	Factor Discriminator	Remarks
Project Size	Agile Methodology	One of the limitations of agile methods Elements of project size are project budget, duration and project team organization compiling more requirements, requiring more people and more coordination	Concluding that when time is limited, using an agile methodology would be better
	Traditional System Developments	support this by providing plans, documentation and processes for better communication and coordination across large groups preferred option for large teams involve a lot of “time waste” outputs such as documentation, design documents, writing analysis etc
People Factor	Agile Methodology	Half of the agile methodology deals with human factors, Individuals and interactions and Customer collaboration Having skill and experienced people in a team is a key factor Encouraging domain experts to be part of the team gives developers rapid feedback on the implications to the user of their design choices Customer adaptability is another great factor, the customer gets the power to check the progress and change the direction of the software development during each iteration	Agile methodology a more attractive process than traditional system development
	Traditional System Developments	The larger the team affects the communication in a project and effectiveness per person Plan-oriented; adequate skills access to external knowledge
Risk Factor	Agile Methodology	It is used in applications that can be built quickly and do not require extensive quality assurance Unknown risks creates major impact	Agile methods allow for better handling the changes, such as constant feedback from customer and short iterative development.
	Traditional System Developments	Critical, reliable, and safe systems are more suited to a traditional system development Well understood risks creates minor impact