A product manager at a new company needs to ensure the development team produces high-quality code on time. The manager has decided to implement an agile development approach instead of waterfall. Which of the following are reasons to choose an agile development approach? (Choose two.)
An agile development approach is suitable for environments where the scope of work is expected to evolve during the lifetime of project development and where there is a preference for code to be iteratively tested throughout the development process. Agile methods are particularly advantageous in projects with changing requirements and promote continuous integration and testing, thereby enhancing the ability to adapt to new information and ensuring quality through regular intervals of testing.
FROM THE CASP STUDENT GUIDE.. C & D ARE CORRECT.. READ PEOPLE: Agile Model The more recent Agile model uses iterative processes to release well-tested code in smaller blocks or units. In this model, development and provisioning tasks are conceived as continuous. This method focuses on adaptive measures in various phases—such as requirements—so that development teams can more easily collaborate and respond to changes. The agile method breaks up tasks incrementally, so that there is no long-term planning, but only short iterations that developers can more easily alter to fit their evolving needs. At the end of each iteration, developers present their progress to clients and other stakeholders to receive feedback and input that they can use in proceeding iterations. The agile method is particularly useful in complex, unstable systems whose requirements and design are not easy to predict. The agile modelʼs focus on rapid development often undermines security. Developers release rapidly which can introduce new, untested functionality and vulnerabilities.
This method focuses on adaptive measures in various phases—such as requirements—so that development teams can more easily collaborate and respond to changes. The agile method breaks up tasks incrementally, so that there is no long-term planning, but only short iterations
Agreed. Thanks for the explanation.
he reasons to choose an agile development approach over a waterfall approach include: C. The scope of work is expected to evolve during the lifetime of project development: Agile methodologies are well-suited for projects where requirements may change or evolve over time. Agile allows for flexibility in accommodating changing requirements during development. D. The product manager prefers to have code iteratively tested throughout development: Agile promotes iterative development with frequent testing, which can lead to early detection and correction of issues. This approach can result in higher code quality and reduced testing effort at the end of the development cycle.
C. The scope of work is expected to evolve during the lifetime of project development: Agile methodologies accommodate changes in requirements and allow for flexibility as the project progresses, enabling teams to adapt to evolving needs more effectively than the rigid structure of waterfall. D. The product manager prefers to have code iteratively tested throughout development: Agile emphasizes continuous testing and integration, allowing for early detection and resolution of issues, which ultimately leads to higher-quality code and reduces the risk of significant defects in the final product.
I agree with previous comments.