SOFTWARE ENGINEERING

Detailed explanation-1: -Often the consequences of not changing are worse than the pain and cost of changing. This gives rise to the 2nd Agile principle, welcoming changing requirements. To maximize profit, we need to welcome at least some changes even late in development.

Detailed explanation-2: -Welcome Changing Requirements at the Right Time By balancing the reality of change with the need for stability for the Development Team, Scrum makes it possible to “welcome changing requirements, even late in development” when it will be most advantageous to do so.

Detailed explanation-3: -Any changes the client comes up with can be discussed immediately. So a change in the requirements, the effect of the change on the overall scope, timeframe, any extra effort required and overall project schedule can be discussed in these meetings at a higher level and agreed upon quickly.

Detailed explanation-4: -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.