INTRODUCTION TO SOFTWARE ENGINEERING
AGILE SOFTWARE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
Agile:Which of the following is NOT a benefit of welcoming changing requirements?
|
|
It gives the team a way to explain a missed deadline
|
|
|
The team builds more valuable software when customers aren’t pressured not to change their minds
|
|
|
There’s more time and less pressure so the team can make better decisions
|
|
|
Less code is written before changes happen, which minimizes unnecessary rework
|
Explanation:
Detailed explanation-1: -In which of the following situations, would you NOT recommend using an agile process? A. For a project where requirements are well known but the technology and solution are unknown (i.e., changes expected in the solution).
Detailed explanation-2: -Visibility of project details. Increased team efficiency. Ability to adapt to changes. Ability to scale.
Detailed explanation-3: -Customer input happens throughout the development process. Product backlog sets development priorities. Daily meetings promote communications. Task boards make developer tasks and details visible. User stories and sprints orchestrate change.
There is 1 question to complete.