INTRODUCTION TO SOFTWARE ENGINEERING
AGILE SOFTWARE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
When the Development Team feels that the work is too hard
|
|
|
When the Sprint Goal becomes obsolete
|
|
|
When the sales department has an important new opportunity
|
|
|
When it becomes clear that not everything will be finished by the end of the Sprint
|
Detailed explanation-1: -A Sprint would be cancelled if theSprint Goal becomes obsolete. This might occur if the company changes direction or if marketor technology conditions change.
Detailed explanation-2: -Another poor reason to cancel a Sprint is when a Sprint Goal is already achieved early, and there is still time remaining. The Sprint Backlog isn’t fixed, and the Scrum Team can still figure out what else is valuable to them or stakeholders. Canceling a Sprint meddles with the heartbeat.
Detailed explanation-3: -The Scrum Master should cancel the Sprint Planning, if the Sprint Goal is not composed beforehand. FALSE. The Sprint Goal is composed by the whole Scrum Team during the Sprint Planning.
Detailed explanation-4: -When the Product Owner or Scrum Master cannot handle the impediments faced by the team, the Sprint is more likely to fail. Also, when the Product Owner makes the Sprint rigid with no considerations for changes, the Sprint may fail as Developers spend more time planning than working.