When to Use and Not to Use Agile Method \" Please respond to the following: Desc
ID: 3703476 • Letter: W
Question
When to Use and Not to Use Agile Method" Please respond to the following:
Describe a development scenario where an Agile method would not be an appropriate method to use for developing a software system. Cite an example that addresses a specific programming language such as Java, C++, or others.
Describe a situation where an Agile method would be an appropriate method to use for developing a software system. Your response must address a specific programming language such as Java, C++, or others.
Explanation / Answer
Agile method would not be an appropriate method to use for developing a software system.
A: Project plan & requirements are clear & unlikely to change:
If team is developing software for a client who wants – a) Speed, b) Clear picture of timeline & budgets c) wants to give detailed documented requirements at the beginning & wants to get involved only during end or testing phase, then taking waterfall approach is better than Agile because Agile projects can not be estimated for budgets & timeline accurately. Agile Projects are people based not plan based.
Scenario :- If a member drops in the middle, Agile project will be impacted while waterfall project won’t be impacted because it has robust documented plan which any new member can take over easily.
In Agile methodology the documentation is less.
Sometimes in Agile methodology the requirement is not very clear hence it’s difficult to predict the expected result.
In few of the projects at the starting of the software development life cycle it’s difficult to estimate the actual effort required.
Functional languages are not good for Agile. They need better understanding initially.
Agile method would be an appropriate method to use for developing a software system.
The customers are satisfied because after every Sprint working feature of the software is delivered to them.
Customers can have a look of the working feature which fulfilled their expectations.
If the customers has any feedback or any change in the feature then it can be accommodated in the current release of the product.
In Agile methodology the daily interactions are required between the business people and the developers.
In this methodology attention is paid to the good design of the product.
Changes in the requirements are accepted even in the later stages of the development.
Java,C++,C# languages are good for following agile methodology because these are adaptable to all situations.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.